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.
@Katorone
Oh yes, it is a feature on the list, but it is not yet implemented.
I intend to have links for all regions, and owned regions, maybe for "can-build" as well.
@Remi_Scarlet
Looks like you mixed up groups and have-inside, the intended logic is to have-inside .... groups ...., but you are not the first exchanging those, i did it too couple of times.
This should do it:
Not quite sure what I'm doing wrong, but the permissions don't seem to be applying correctly even after looking through your example files for permissionsEx and going through your troubleshoot page like 10 times. It's probably some extremely stupid mistake, but regardless I can't seem to find it.
with the permissionsEx looking like
Is there anything blatantly wrong that I'm missing here?
Thanks
I'm trying to use towny and worldguard together. Towny is setup to block building everywhere outside of towns, even inside worldguard regions. This is why I was hoping your plugin could add the exemption permissions of the towny wilderness rules to all worldguard regions. To do this with some ease, I'd need a wildcard, a permission setting that applies to all worldguard regions. I've looked through the documentation but haven't found this specific setting. Could you tell me if your plugin supports this, or will support this in the future?
Regards, Kat
I think the main reason the user count is on the lower side is mainly people don't understand how powerful it can be.
@sheepwool7
Thank you :) - the number of users is not that high after all, so the pace of comments can be very slow...
@asofold
No, it was just getting a bit nervous because of the lack of comments.
I really like the plugin, and it works very well. I really appreciate your work!
@sheepwool7
Yes, it still is in developement, and in use.
For the dev version (not available currently) i added transient permissions that do not really need a permissions plugin. However i would want to make it so , that RSP really works without a permissions plugin.
Further big point is to allow generic stuff, for instance for region owners or worlds.
Is there anything specific you need or came across?
Is this still in development?
Amazing plugin, thanks!
@Ferkswe
Actually having permisisons for players own regions is a future feature, which will be in one of the next versions.
Currently you have to set the region names explicitly.
Hm. This could be exactly what I need. What I want to do is make it so people only have access to making LWC protections while inside of their own WG region by enabling the permission node when they enter the region. I would do that with this plugin by making two identical permission groups but one with and one without lwc permissions right?
@cataclisto
It is not directly hooked by RSP, you would need Vault to link to it, currently. With Vault it should be possible to use, though i have not tested it myself with GroupManager, yet.
I might add direct support for GroupManager later, though.
Just wondering is this compatible with the permissions plugin, essentials group manager? I see its not mentioned above.
@EvilNilla
Well, RSP uses the permissions plugins (or in this case Vaults) APi to manipulate permission groups, thus permission changes result in file-IO usually. This could explain lag spikes in case your test server is very slow on that, also in case of many players changing permissions in the same moment.
Questions:
On a local test with PermissionsBukkit with Vault i am not experiencing any trouble.
In general it should be "possible" to use Vault + PermissionsBukkit, but concerning performance, other permission plugins should be a more optimal choice, especially concerning changing permissions. One example is using PermissionsEx tied to a fast local database, which would allow for per player permission saving, which should be the most efficient with RSP. But others use it with other plugins too, so this is probably not needed.
We're using the latest 0.12.0 beta.
I'm really excited about the possibility to use this plugin. But I've noticed that when this is loaded on our dev server(Vault + PermissionsBukkit), things creep to a halt when people enter/leave the specified region.
Are there any known bugs with performance on this plugin?
@Adkit
Well, claiming that the users of RSP don't understand it:
As it seems people get along well with RSP once they have understood how it works. You can decide for yourself, if to take the hurdle of configuration, or not do it.
To get what you want, you might ask some programmer at irc/bukkitdev to check/turn PermissionZones (by Evenprime at GitHub) into what you want, though that one uses transient permissions, which do not persist on disk.
Still the alternative is to tell what you want to reach, in order to receive information on how to reach it with RSP.
I don't think you understand how user friendlyness works. I don't care what happens behind the scenes or what needs to be done to make it work, all I wanted was a config file with World: Region: - permissions
I would've even been ok with a tutorial telling me to also put a special permission named "rsp" or something in the groups I want to be affected or whatever but the whole filter and "permdefs" and so on, it's just a mess of things that the common user won't understand unless they already understand it.
The fact that you wrote so much as a reply kind of shows what I mean, you need to make this more basic for the people who are actually using it. With how much you're typing it makes you sound like you have Asperger's. x.x Which is funny because I have Asperger's but type less than you.
@Adkit Is that now a feature request ?
You can create a ticket for it.... so sorry that you did not make it to a working configuration.
The configuration is almost as simple as possible to provide the features RSP has.
You define a set of permission groups and how they are to be applied. Then you define for which regions in which worlds these sets should apply.
The reason for using permission groups is that they do not create too much of havoc if trouble arises, they can simply be removed and few harm is done.
But if i let RSP add single (persistent) permissions, then trying to recover from problems is rather more tedious than with permission groups.
I will later add transient permissions support for permissions that do not get saved, but i will keep the configuration structure - it is not 100% straight forward, but it aims at people not having to define all permissions groups and properties how to add or remove them for each region individually, but do one definition of the desired kind and link all regions to that definition rather than repeating the definition over and over. Also linking several separated permission setups to one region is comparably simple the way RSP does it (imagine many shop regions, some with extended functionality and some with allowing other stuff like flying or whatever, some shops for VIPS some for all, etc.).
This is not a simple plugin, there does not exist a simple plugin for this, and there will hardly ever be a plugin with a much more simple configuration than that of RSP, which can do what RSP does, i am very sure :)
For what you want there might exist something almost as simple as you want , one day, perhaps. But be aware that you need the world name and the region name to assign properties to a region and then... do you want an extra file for it, so you dont need to use a configuration section like "links"? That would be more simple for the region linking, but also would mean more files, which then some others would find less simple. While filling in the permissions or permission groups directly into the region section means to blow up the configuraton section to another level, being not nice to read as opposed to a list of "permdef"-names that are linked to a region as it is now.
The documentation is certainly not perfect, probably not even optimal, but if you don't tell what you tried (probably next time before one hour has passed) then people can't help you on that. Using a local server for testing the basic plugin setup can be helpful to get over the basics without causing problems for your "production servers".
If you should decide to try again, i would be interested in the information about versions and plugins you use concerning: WorldGuard, CraftBukkit, permissions plugin + if using Vault.
Unfortunately i will be away for a couple of days, so you might have to wait till then, unless somebody else joins to help, to reach me it is like 12 hours to go at most...
Ok wow, this has got to be the worst plugin I've ever seen. It's so confusing that you have to spend an hour just figuring out the logistics behind it. All it had to be is two settings: "area" and "permission" so you could add a permission to an area. That's all it needed. Your explanation doesn't help, it's barely even lucid.
Not only that, it completely crashed my server and made it impossible to reboot until I removed it.
+1 love it works great for me :)