Config or perm World Blacklist / Whitelist with override
LadyCailinBot opened this issue ยท 2 comments
WORLDEDIT-2848 - Reported by Zed.Spencer-Milnes
My suggestion is that if you have 14 worlds and you want to allow your Donators to have WE access to maybe 3 of them and then staff to have access to 7 of them, but if you are owner you want access over all worlds. To achieve this currently, you will have to have separate permission files for each different world, this is really hard to maintain if you get a new plugin, or want to change something and you have loads of worlds.
I see two solutions to this problem, one better than the other:
== Solution 1 == :
In the config file there is a 'world whitelist' with an enable/disable switch and a 'world blacklist' with an enable/disable switch. This means if you wanted all worlds disabled but one, you can use the whitelist or if vice versa, you can use the blacklist. If the permission worldedit.world.override has been given then that player can use WE anywhere
== Solution 2 better in my opininon == :
Have a permission based system so if the Donator Rank has the perms:
- worldedit.world.creative
- worldedit.world.flat
- worldedit.world.donator
the donator rank will only be able to use WE in these worlds.
In vice versa you could have this set:
- worledit.world-deny.survival
if you want all others enabled but this one.
I would suggest that the use of these permissions is toggled in the config file so new server owners won't have to mess with setting extra perms, the options for worldperms could be 'off', 'blacklist' or 'whitelist'
you can then add more and more worlds as the ranks go up. The owner could also have the permission:
- worldedit.allworlds
This would allow them to WE in all worlds.
I believe Option 2 is better than Option 1 as although it is slightly more complicated, it is much more flexible.
I hope you will consider my suggestion
Comment by wizjany
most permissions plugins already support per world permissions
Comment by sk89q
I think he means that his/her permissions plugin supports it, but its a pain to do.
But IMO it is a limitation with the permissions plugin. It should support specifying, for example, which permission files to use for which world, and allow for things like merging permission files or inheriting them.