Register Welcome to the BukkitWiki! Want to help out? We would love to have you! Signup to get started! Home We are preparing to move all Fandom and Gamepedia logins to a unified login system. If you have an account on Fandom with the same username as on Gamepedia, we have a very simple set of instructions to resolve the conflicting username.
|Published (Last):||18 November 2007|
|PDF File Size:||2.76 Mb|
|ePub File Size:||17.66 Mb|
|Price:||Free* [*Free Regsitration Required]|
This configuration can be as simple or as complicated as you make it. The most traditional system shown below uses group inheritance, starting with new players at the top, and owners on the bottom. On smaller servers you might end up merging the moderator and admin rolls, but most people will have different opinions when it comes to which powers the admin should receive access to, and which powers moderators should receive as well.
Newbie The newbie group contains the very basic permission nodes, and should be safe to give all newly joined players upon login. Player The player group covers all the commands that established players can use. This usually includes commands which involve the economy, basic teleportation, and other basic commands.
Moderator The next two groups can be merged or split even further based on your preference. Typically the lowest moderator rank has access to kick users, and jail a user, while higher ranks gain access to IP ban players, turn invisible, and spawn creative mode items.
Place the GroupManager plugin into your plugins folder. The very first time you run Group Manager, it will generate the config files which you can then edit at will. The standard config is usually something which is very similar to the layout detailed above, but you will need to edit the configuration at least a little before use.
You will at the very least want to add yourself as admin. Each plugin has its own set of permission nodes, directly relating to the commands from that specific plugin.
Essentials maintains a complete list of permissions in its Command Reference. For other plugins you will need to check their related documentation. Permissions Nodes Every plugin which supports a permissions plugin, will have their own permission nodes. Example: essentials. This causes the specified group to have access to every command from every plugin. Note: Conflicting commands will become unstable unless negated by a negative node.
Use at your own risk. Not all plugins properly register their permissions as well. Negative Nodes Group Manager supports negative nodes, allowing you to retract access to commands.
This can be useful with inheritance. Combining a summary node with a negative node can remove access to numerous sub-commands with ease.
This can be useful for easily removing access to all commands, then adding each one back individually. These are values which are unique to the group.
They are typically used in plugins to alter behaviour, based on groups. Chat Plugins Most chat plugins will read the prefix and suffix variable to allow you to give players custom names based on their current group.
A list of what colour codes can be found here. Plugins such as EssentialsProtect do. Migration Normally converting from most permission plugins is a rather simple affair. Move EssentialsGroupManager. Remove the previous permission plugin jar from your plugins directory. Copy the previous groups file. Paste two copies of the permissions configuration file.
Rename one to users. Restart the server. Group Manager Commands There are a large number of commands associated with the Group Manager plugin. These can be used to modify and assign groups to users ingame, or from the server console. Make him default group. This command will only allow the user to move the player between groups they inherit.