- 1.8
- 1.9
- 1.10
- 1.11
- 1.12
![[Image: 10e79fbde2f08a43b97b4e3d26031caea6141b9e...banner.png]](https://proxy.spigotmc.org/10e79fbde2f08a43b97b4e3d26031caea6141b9e?url=https%3A%2F%2Fhelpch.at%2Fbanner.png)
![[Image: 09e95546f7cf9400cf2f83b4d01614fb161e18a1...QIN3Xc.png]](https://proxy.spigotmc.org/09e95546f7cf9400cf2f83b4d01614fb161e18a1?url=http%3A%2F%2Fi.imgur.com%2FOQIN3Xc.png)
This video was made for EZRanksLite but it is still supported for EZRanksPro
The best and most customizable /rankup plugin!
This plugin relies on Vault, and a Vault compatible economy and permissions plugin to function properly.
Compatible and tested with PermissionsEx, GroupManager, bPermissions, zPermissions
SQLPerms is also supported![[Image: clear.png]](https://www.spigotmc.org/styles/default/xenforo/clear.png)
Compatible and tested with PermissionsEx, GroupManager, bPermissions, zPermissions
SQLPerms is also supported
Spoiler:More information
Player Commands:
Spoiler
layer commands
Spoiler
layer commandsAdmin Commands:
Admin commands require a player to have a certain permission to be used! Console supported!
Spoiler:Admin commands
Admin commands require a player to have a certain permission to be used! Console supported!
Spoiler:Admin commands
The first time EZRanksPro is started on your server, 4 configuration files will be created. Each file allows you to customize every aspect of your rankup plugin. In addition to these 4 files, there is also a "debug" option in the config which when enabled will create a debug.log file. There is also an option to log all rankups, if this config option is enabled, a rankup.log file will also be created.
Spoiler:config.yml
Spoiler:rankups.yml
Spoiler:messages.yml
Spoiler:multipliers.yml
To give a player or group access to a rankup, they need access to the permission node associated with it! Without it EZRanksPro does not know what rankup they have access to. If you create a rankup for rank A to B, you will need to give the A rank the permission node: ezranks.rank.A. This will tell EZRanksPro that players in A should have the rankup associated with A. Players can have access to multiple ezranks.rank,<rank> permission nodes, the highest order rankup will always be applied for the player.
For a player to be considered the last rank, they NEED to have the permission node: ezranks.lastrank
This tells EZRanksPro that the player is at the last rank and has no more rankups available.
Inside of your rankups.yml you will see a section with each rankup named rankup_actions.
In this section you may list many actions that the plugin will perform when a player ranks up. The format for actions are:
- '<action> <arguments>'
You must include required arguments
<required>, (optional)
You may delay any rankup action by ending the action String with <delay=(time in seconds)>
example:
- '[consolecommand] eco give %player% 100 <delay=10>'
Spoiler:Rankup action list
Placeholders can be used in your rankup actions and messages:
Spoiler:placeholder list
EZRanksPro uses MetricsLite to collect anonymous statistics such as the amount of servers using the plugin etc. You can disable metrics in your /plugins/pluginmetrics/ folder
If you have any suggestions or feedback please post in the discussion thread!
If you enjoy the plugin, please leave a rating and comment
This hidden content has been reported as still working 0 times this month.
1 times in total