Region specific permissions
Region Specific Permissions (RSP) allows to add and remove permissions dynamically, using WorldGuard regions as reference. Also useful to limit your worlds to a rectangular or circular zone around an arbitrary center! Currently you need WorldGuard for regions.
Maintenance Phase
Due to timing constraints i might not add much to this plugin, but can keep it updated.
I might implement some features of pex to make this a fully featured permissions plugin, t would be somewhat optional and RSP still would be able to use hooking into other plugins. However that is quite a task and i am not sure if i will do it, or if i want to rely on another permissions plugin, since pex might time out.
Quick links: Installation | Configuration | Commands | Troubleshooting | Examples
Internals: Performance | Progress | Changelog | Source Code on GitHub
REQUIREMENTS:
- WorldGuard
Since version 1.1.0 you don't need a permissions plugin anymore to operate RSP.
Compatible permissions plugins:
- PermissionsEx or
- bPermissions or
- Since 0.12.0:
Vault, linking to another permissions plugin - however it is not guaranteed, that your permission plugin supports adding or removing groups during runtime. Furthermore you might have to alter the RSP settings to achieve compatibility via Vault.
Should work without adaption (or despite): PermissionsBukkit (RSP 0.12.0)
This plugin actually adds and removes permission groups, either those defined by the permissions plugin or those given in the RSP configuration in the transient-groups section.
Actually RSP has more to it than "just" permission adaption for regions, it also allows to confine your worlds to circular or rectangular areas with arbitrary center, to limit your maps.
See the Configuration link for more specific information and the Troubleshooting link for examples and hints. Both sections are under review and will be updated more or less soon.
omg it was a big failure by me :D
i edited, saved and reloaded the permissions.yml but somehow it didn't save the group "waffen" after the reload. so i just added the group and it's permissions via ingame-commands and right now it's all working^^
thanks for your help.
nice plugin! ;)
@Ahmet094
Ok, the RSP - part looks ok (except for the filter -perm), it all boils down to the permission setup, if i am not mistaken.
The filter-perm is a permission everybody who is intended to gain groups inside of "testarena" should have - if every player should have it, you might just erase the filter-perm entry. It seems contradictory that "pvpgun.machinegun" is the filter-perm and part of th group to be gained at the same time, but this might not be related to the issue.
PermissionsEx should be fine, also with /upper/lower-case group-names, so it really seems to be a question of the permissions setup now... maybe you should add to Bürger some pernission like test.use and name the filter-perm the same.
(If the filter-perm is pvpgun.machinegun and the testperson has it everywhere to test then it is there everywhere, simply, but i am not sure about the rest of the permission setup...)
Thanks for your response ;)
I tried it 1h now, in many different variations, but none of them worked...
So here are some information:
The group in which the Players are: "Bürger"
The group in permissions.yml called: "Waffen" includes following permissions:
- pvpgun.machinegun
- pvpgun.pistol
- pvpgun.sniperrifle
name of the world: "Farmland"
the region in which the players of the group Bürger should have the permissions of Waffen: "testarea"
So i changed the part u sent me like this:
permdefs:
haveguns:
filter-perm: pvpgun.machinegun
ignore-perm: test.ignore
have-inside:
groups:
- Waffen
links:
Farmland:
testarea:
- haveguns
I'm using PermissionsEX.
The testperson could use the gun everywhere^^
Sorry if i missed something, but this plugin is really difficult to configure :D
@Ahmet094
I can't write more right now, you might have a look at the examples linked in the Troubleshooting section. You need at least to look up the permissions for that plugin, which players should have, then you make a permission group for it (that is all independent of RSP). If that is done you can check if adding a group manually and removing it has the desired effect (you have probably done that). Once you have a group with the necessary permissions, RSP setup will not be that difficult anymore.
Say the group is guns, and the filter permission is use-guns (all players thast shall use it there need it by default).
You add the following to the default configuration, WORLD must be the exact name of the world, REGION that of the region (case-sensitive):
If extra settings are necessary might depend on what permissions plugin youre using (If using Vault ....), the example should work with PEX, bPermissions and PermissionsBukkit+Vsult.
Hey,
sry, but i don't understand how to configure this^^
what i want to do is that my players get the permissions for a plugin [PVPGuns] only in the region of my battlefield.
would be nice, if someone could write 1,2 lines of the config-part to show me how i have to list the specified regions..
thx :)
@asofold
You are the man!! It works! Awesome.
@doekia
Ok, i think i understood the issue, good that i have a second account with different case.
It should be fixed now:
DEV version: RSP 0.12.0-DEV-4
@doekia
Ok it is a bug on Vault+PermissionsBukkit side.
But i will try to provide a fix for it on the RSP side, because it is possible.
@asofold
Well no it does not work. I cannot have my player to change their Premium account to be all lowercase :-(, and I cannot see any option to refer to case within permissionsbukkit. Is that a show stoper?
@doekia
So it works now ?
I must add some entries to the Troubleshooting section about letter case, because it can be an issue with permission plugins topo (bPermissions has a configuration option for that, i think).
@asofold
All my plug and versions:
Bukkit is: 22:19:23 [INFO] This server is running CraftBukkit version git-Bukkit-1.2.5-R1.0-b2149jnks (MC: 1.2.5) (Implementing API version 1.2.5-R1.0)
The problem is not just reported. The group, hence the permissions attached to are active. The broker group:
STOP - STOP - STOP While collecting those data my brain switched to genius mode :-) The pattern regarding those failing compared to those working is the letter case. ZerKha/Exose/ZeoBelle fail miserably doekia/lucascart/brunolehip works great
I guess we have a winner :-) Thanks to my brain, was by accident I noticed!
My post got lost...
I'm sorry to hear that....
Now once again, please state all used versions:
I can not reproduce with many users , but i can do some checks.
Given almost any WorldGuard version the region detection should be 100%.
The problem can be the permission changing, though i currently do not see a reason, why it should work for some and for some not, unless there is issues in CraftBukkit, PermissionsBukkit or Vault.
Actually now that i read it again - check to have the latest versions for at least PermissionsBukkit (1.6) and Vault (1.12.14, maybe 1.12.13 does) (but please also state the otthers) - it looks like that either Vault or PermissionsBukkit reports the group to be there (be that the case or not), so naturally on cache-expiration time RSP will attempt to remove it because it is rechecked and found to be in place, though it should not.
It really looks like the group removing does not work (most likely: Vault version, PermisisonsBukkit version, maybe: CraftBukkit version, unlikely: WorldGuard).
@asofold: I did triple check my config. use-worlds was fine ... I have added the extra sections you have in yours such as generic-links and load-plugins to no avail. Then I tested that with different user and it works for some not for someothers. The success or the failure are consistent. I can't see any pattern for such. Same group set same perms ... some ok some ko.
What I can see on the console is that for those it does not work they are tried to be added to the group on entering AND on leaving AND every 12s should they do something ... click move etc ... I tried removing the user profile, reseting manually the groups while they are out, /rsp reload under most possible scenario ... those buggy are still buggy.... any hint?
@doekia
For me it works fine now with Vault+PermissionsBukkit (0.12.0-DEV-3), just you have to set the use-worlds entry to false. (Configuration shows where it is.)
@doekia
(lol) I had the same problem at first - did you set the config flag ?
For Vault+PermissionsBukkit you must set the flag use-worlds to false in the permissions section of the RSP configuration. That should work with the 0.12.0-DEV-3 version.
If that works, players also should get the groups removed when they are not inside of that regin, for instance at login, once set up correctly. So you don't need to manually remove them for all players, do check that, though ...
@asofold: Sorry but I have to temper our mutual enthusiasm. Player get add to to group while entering the region, but never removed from such ...
@asofold: Man you are a master. For what I need it works. Thx
@doekia
Ok i have a version that seems to work with PermissionsBukkit 1.6 now:
DEV version: RSP 0.12.0-DEV-3
It still has / might have some issues, such as printing messages on the console, those are there due to the implementation of Vault, currently.
In order for it to work you have to set the configuration flag in the permissions section: use-worlds: false
@doekia
PermissionsBukkit does not work with RSP / Vault currently.
I am trying to solve this somehow, maybe i will just add PermissionsBukkit directly, though it is kind of hacky due to sending commands like from the console instead of using API calls.
@asofold: I just checked with the latest 0.12DEV2. I does not work at all for me and the PermissionsBukkit. rsp.yml
worlds/map/region.yml
console output
The region is fine and display the greetings The user is never displayed as been part of the group "broker" The group exists while add manually works as expected.
I'm a bit confused with those permissions plugins. As far as I understand I was thinking that PermissionsBukkit is been just a superbridge on top of native permissions.
Group not been saved would not have been an issue for me. I set the area to be the only one where players can trade ... so if they have to leave/re-enter the area while disconnected (purpose/bug/lag) would not have been an issue.
Hope the best that you can somehow address the issue in near future - good luck