ScrollingMenuSign supports all superperms-supporting plugins, including PermissionsBukkit, GroupManager, bPermissions and PermissionsEx.
The default permissions configuration (this applies if you're not using a permissions plugin, or haven't given any scrollingmenusign.X permission nodes to the player) allows basic menu usage for all players, and full plugin admin rights (creation/deletion etc. of menu & views) for op-level players.
The Easy Way
The easiest approach is to grant players one of the following parent permission nodes, each of which grant a set of low-level permissions:
|Usable view types
|Scrolling and executing menu entries, permission elevated commands cannot be used
|As above and permission elevated commands can be used (if no permission nodes are granted, this is the default level of access)
|As above, plus
/sms show, and
/sms getcfg can be used
|Allows creation of menus and views (see below for list of restrictions)
|Complete control of the plugin (if no permission nodes are granted, op-level players have this level of access)
If you want to prevent all menu usage, the easiest way is to give the negated scrollingmenusign.user permission node.
The scrollingmenusign.limited_admin permission node gives control of most plugin functionality, with the exception of:
- May not modify menus or views owned by someone else
- May not change the plugin configuration with
/sms setcfg ...
- May not add menu items with commands that use costs or permission elevation (see Command Parser)
- May not create redstone control signs
Map views, Inventory views and Spout views are restricted from guest and basic users by default since they can be used anywhere, potentially giving users a lot of power. Sign views and Redstone views views are fixed at specific locations in the world.
The Harder Way
If you want more fine-grained control over who gets what nodes or your permissions plugin doesn't handle superperms parent nodes properly, you will need to grant (or remove) low-level nodes individually.
Regular players have the following nodes by default:
Regular players do not have the following nodes by default. You may wish to grant one or more of:
- scrollingmenusign.use.map (if you want to allow players to use map views)
- scrollingmenusign.use.spout (if you want to allow players to use spout views)
- scrollingmenusign.use.inventory (if you want to allow players to use inventory views)
Admin-level players should get all of the nodes listed below.
The following lower level permission nodes correspond directly to
/sms <command>. The Default setting for each node applies if you're not using a permissions plugin, and/or you haven't given any specific
scrollingmenusign permission nodes to a player (including the parent nodes listed in The Easy Way section above).
|allow views to be scrolled
|allow menu commands to be executed
|allow permission-elevated commands to be executed
|for doing anything related to sign views
|for doing anything related to multisign views
|for doing anything related to map views
|for doing anything related to inventory views
|for doing anything related to spout views
|for doing anything related to redstone views
|allow users to create map views from sign views by hitting a sign view with a blank map
|allow users to create sign views from map views by hitting a blank sign with a map view
|for adding menu items with permission-elevated commands
|for adding menu items with costed commands
|ignore view and menu access control settings
|allows modification and destruction of menus & views belonging to other players
|allows creation of redstone output switches
|allows creation of redstone control signs