Using Promotion Tracks

Promotion tracks are an easy way of promoting and demoting users on your server. Rather than having to remember what groups a user is in, or the right command to use, promotion tracks can allow you to easily set a users rank with only one command - /promote username trackname. This also allows you to allow admins to promote users without giving them the master bPermissions.admin permission.

Types of Tracks

bPermissions supports 3 different methods for promoting a user along a promotion track. The method used by the server is configured in the bPermissions config.yml . For this, we'll assume a default promotion track which promotes along 3 groups: default, trusted, moderator and admin

• track-type: multi will add the next group in a track to a user. For instance, if a user is currently in the default group, running /promote on them will add the trusted group to the user, meaning that user will be in the default and trusted group. Note that if a user is currently set to the trusted group, and you run /promote on that user, the promotion won't work correctly as the track type also expects the user to be in the default group.
• track-type: single sets the users group to the next group in a track. For instance, if a user is currently in the default group, running /promote on them will set their group to trusted, meaning they will only be in the trusted group.
• track-type: replace will add the next group in a track to a user, and remove the previous group in that track from the user. For instance, if a user is currently in the default group and a donator group, running /promote on them will remove the default group, add the trusted group, meaning they will be in the trusted group and the donator group.
• track-type: lump adds all the groups in a track to a user. For instance, if a user is currently in the default group, running /promote on them will give them the gorups default, trusted, moderator and admin.

Example tracks.yml

default:
- default
- trusted
- moderator
- admin
donor:
- donator
- donator+

Permissions

Unlike other bPermissions commands, you don't need bPermissions.admin to be allowed to use tracks. This means you can give some members of your server limited promotion ability without giving them full access to bPermissions. To allow a user or group to use a permissions track, give them the permission tracks.trackname, where trackname is the name of the track in the config.yml. The permission tracks.* allows them to use any track