config.yml explained


There are three options for this configuration. "multi", "single", and "lump".
This affects the behavior of the "promote" command. When set to "multi", "/promote" adds the next group in a track to the player. When set to "single", "/promote" sets the player's group to the next group in a track. When set to "lump", "/promote" adds all groups in a track to a player.


A boolean option. Setting to "true" will make bPermissions save to file every single time you alter a permission, group, player or meta data. Setting to "false" will make it so in order for command changes to be saved (after no matter how many commands), you must do "/permissions save"


  • To post a comment, please or register a new account.
Posts Quoted:
Clear All Quotes