|
|
BlockSuite-Core has its own internal permission system that is separate from Spigot permissions. |
|
|
\ No newline at end of file |
|
|
BlockSuite has its own internal permission system that is separate from Bukkit/Spigot permissions.
|
|
|
|
|
|
...Why?
|
|
|
|
|
|
Well, BlockSuite-Core and BlockSuite-WebUI share permissions and would be really inconvenient attempting for the WebUI to try and pull the permissions that a user has in Bukkit/Spigot. The best solution is to create an internal permission system that both share and can be configured in the Web, Console or in-game. It is the same across the board and no need for redundant configurations.
|
|
|
|
|
|
# Structure
|
|
|
It is pretty simple. Each user will be part of a group, and that group will have a set of permissions they can execute.
|
|
|
|
|
|
Currently, players can only be part of one group at a time and cannot have individually set permissions. If you wish one particular user to have their own permissions, then you must create a group for _that_ user.
|
|
|
|
|
|
# Groups
|
|
|
By default, the group 'members' is created and applied to all new players that join. The group 'members', of course, has limited permissions.
|
|
|
|
|
|
There is currently no limit on how many groups you can have, but you are limited to group names of 32 characters. |
|
|
\ No newline at end of file |