What Rankup version do I need for Minecraft version 1.18/1.17/1.16/1.15/1.14/1.13/1.12/1.11/1.10/1.9/1.8/1.7?
The latest Rankup version supports all Minecraft Spigot server versions. Only Minecraft Versions 1.13+ support all Rankup features.
An example of features that don't function in versions 1.12 or older includes any
requirements:that check the Vanilla statistics menu since these are not available in 1.12 or lower due to major changes.
Rankup remained compatible with 1.15, 1.16, 1.17, and 1.18 on release and is expected to maintain compatibility when Spigot and other dependencies become available/stable.
Always keep plugins like Rankup up-to-date.
Try to update to the latest version of Minecraft to maintain compatibility for all of Rankup's features.
When migrating, first you should make a copy of all the files in your
/plugins/rankupdirectory to use on the new host.
Then use the migration information included with your permission plugin to maintain players' rankups on the new host.
Rankup does not manage prefixes! Consult your permission group and/or chat plugins.
If you followed this wiki's recommendation to use LuckPerms, you can learn about Prefixes and Suffixes on the LuckPerms wiki!
LuckPerms can also support multiple prefixes via Prefix Stacking
Rankup doesn't save them!
Instead, your permission plugin stores a player's group information and provides it to Vault.
Rankup uses what's provided to Vault to place a player on the ladder if possible. (example: a player's primary-group in LuckPerms)
No, Rankup automatically changes a player's groups when
Learn about when and how to use
Rankup only applies/removes the groups specified in a rankup step written in your rankups.yml when
permission-rankup: true, you change those groups manually.
See the Permission Rankup page for more information.
This is a known issue if using GroupManager. GroupManager does not support Vault correctly, as it has not been updated since 1.7.
If you are on any permission manager not supported by Vault, like GroupManager or PermissionsEx, there are steps to migrate to LuckPerms, the permissions plugin used in this wiki's example configurations.
Otherwise, make sure the group you want to rankup to actually exists in your Vault-Compatible group management plugin.
Verify the group is named identically to the rankup step's
next:in your rankups.yml.
/prestige, also verify prestiges have been enabled in config.yml.
Try updating Rankup3! A new placeholder engine was added in version 3.12.
If your files use Old Placeholders, upgrade to their new Pebble Placeholder variants.
Though the Old Placeholders remain supported, they offer fewer customization options.
We recommend using a 'find all and replace with' operation on each Old Placeholder for the new Pebble Placeholders.
You can find examples comparing the Pebble Placeholders and Old Placeholders at the bottom of the Config Placeholders page.
Players also need the permission
rankup.auto. Though enabled by default, you may have negated it.
ranksgui:is available in Rankup 3.10 or newer,
/prestigescurrently has no dedicated gui.
Files like the
prestiges.yml, and selected locale are reloaded as described in the Commands Reference.
However, the reload command executes the reload function which only reads all the prior listed files and
config.yml. The only contents of
config.ymlwhich should get repopulated during a reload at runtime are
permission-rankup:, but it's recommended to fully restart if changing any
You should always read the console after a command fails and while starting your server.
This message is only used to indicate a problem. It provides no information intentionally.
Rankup will NEVER send detailed errors to chat.
Share only the errors from console in discord when troubleshooting after receiving this message in chat.
/rankup3 reloadfrom, or while watching, your server console.
This way you can see any error as it gets generated.
Read through the error's readable text.
The plugin will often describe parsing errors in the console by providing line and column numbers to the problem in your file.
You can also validate your yaml syntax with a validation service like CodeBeautify.
Sorry, but we could not find any rankups for the group(s) you are in. Use /ranks to list the rankups.?
The sender of
/rankupdoes not belong to a permission group listed in your
rankups.ymlto utilize the correct group name or permission node or change the player's permission groups in your permission manager to match their actual progress on the rankup ladder.
Multiple root rankup nodes detected (a root rankup nodes is a rankup that does not have anything that ranks up to it). This may lead to inconsistent behaviour.
You can only have one rankup ladder!
Each rank at the bottom/beginning of a ladder is called a "root" node. The root node indicates the start of a rankup ladder.
For each error listing a conflicting root node, you have
1 + error countroot nodes.
Fit unwanted root node back into the primary rankup ladder or remove the extraneous node and all rankup steps along its ladder of
next:nodes if they exist.
[Server] INFO Caused by: java.lang.ArrayIndexOutOfBoundsException: Index (number) out of bounds for length (number)
If you see this line in your error, your GUI has been misconfigured.
Check that all fields of your
gui:are accurate and will create a valid GUI.
If you see this line in your error, one of your messages has been misconfigured.
The error in console is now entirely readable text describing solutions to this error.
Use math operators in a pebble template to change the output of the placeholder.
Use a source code editor like Kate/Atom/Visual Studio Code/etc. when editing the files to "syntax highlight" or color the functional code.
You should edit the plugin's files in an editor with YAML syntax highlighting whenever possible.
You must remove, replace, or integrate any functional code from the examples otherwise you may encounter unexpected results/errors.
Code following a "#" is known as a
comment. Comments are non-functional code which the plugin will ignore and are used to embed notes in the files.
You can safely ignore or remove the comments and refer to the rankups.yml file in this repository if you prefer.
Make sure to preserve the syntax of your own functional code when deleting large sections of the files.
tl;dr use either |- and newlines or double quotes and \n
message: |- firstline secondline
will appear in chat as
will appear in chat as
Of these two, the first is recommended by Okx.
The other newline behavior options detailed in https://yaml-multiline.info/ are not recommended for beginners and are not included in default configurations.
Discord can highlight your code when submitted as a file with the
.ymlextension or in a code block like the following:
```yaml code: rank: 'foo' next: 'bar' requirement:  ```
Refrain from sharing large chunks of code using the above method.
.ymlfile or pastebin link to your files is always preferred!
Don't post images of files!
When you rejoin, make sure to read the #readme channel and pinned messages in the support channels before asking or replying.
You can send Okx a spigot message to request an unban. Access is not guaranteed for those who violate the server's or Discord's rules.