Examples
Here you find some examples of how to use RSP.
Some are a little older and rely on the underlying permission plugins groups. However it should be preferred to define all permissions with the transient-groups in theconfiguration of RSP, if possible. That spares unnecessary writing to disk for most of the "have-inside" setups.
Transient Permissions (RSP)
This is recommended for all permissions that do not need to be written to disk or are just to have inside of a region or are just for use during runtime.
Negating Permissions
A bit complex may appear the task to negate existing permisisons. In general the rule of thumb is, that you have to negate permissions of your permissionsplugin using groups of that plugin, and to negate permissions given via RSP with transient-groups also with the use of transient-groups. Even further that means that to reliably negate or un-negate permissions you have to handle that permission completely with either the permission plugin or with RSP. Even further one can't really rely on the permission plugin to reliably negate permissions with dynamically added groups, for the uncertain grouping order. If your plugin supports priorities for groups it is simply solvable. RSP supports priorities for permdefs, so you can reliably negate and un-negate permissions using the transient-groups of RSP. (I might later go for an update that allows to control in which order groups handled by RSP are passed to the permissisos plugin, such that negation might be possible, however that might not go for every plugin.)
Persistent Permissions (Permisisons Plugins)
For permanently adding or removing a group registered with your permissions plugin you can use the group names defined in there. This could be setups of the types like "choose your skill" or "i was here".
Comments