- Add /rankup noconfirm command
- This makes a player attempt to rankup without any confirmation. It can be disabled in the config.yml.
- Requires the permission rankup.noconfirm which is granted by default
- Administrators can use the permission rankup.noconfirm.other to make other players rankup with /rankup noconfirm <player> - this can be helpful in making custom confirmations while retaining Rankup's built-in confirmations.
- Better integration with LuckPerms with the luckperms-context configuration option.
- This forces Rankup to use a specific LuckPerms context when checking for, updating, or changing groups instead of using Vault.
- The mob-kills requirement can use EntityType.valueOf as well as EntityType.fromName now.
To take advantage of these options, copy the following text to the end of your config.yml or delete/move it and allow it to be regenerated by Rankup.
Code (Text):
# if not empty, these are the contexts to use when modifying groups if LuckPerms is enabled
# if empty, this will be based on your LuckPerms config.yml 'use-vault-server' and 'vault-server'
# this option will only work if permission-rankup is disabled
#
# luckperms-context: 'server=global' # to make all rankups global
# luckperms-context: 'server=survival' # to make all rankups specific to survival
# luckperms-context: 'server=survival world=world_nether' # to make all rankups specific to the nether world in survival
luckperms-context: ''
# if players can use /rankup noconfirm to bypass any confirmation
# the permission rankup.noconfirm is used for this command, but it is true by default
# the console can always do /rankup noconfirm <player>
enable-noconfirm: true