Installation
Requirements
| Java | 21 or newer |
| Server | Paper, both 1.20.x and 1.21.x |
| Required | SnLib.jar (SnLib 1.25.0 or newer) |
| Optional | Vault plus an economy plugin, PlaceholderAPI |
| Database | SQLite (default, no setup) or MySQL |
| License | Yes - SnRankUp is part of the licensed bundle |
The jar is compiled for Java 21. A 1.20.x server still running Java 17 refuses to load it, so move the server to Java 21 first.
Steps
- Download
SnRankUp-<version>.jarfrom the releases page (tags prefixedsnrankup-). - Put it in
plugins/, together withSnLib.jar. - Start the server. SnRankUp creates
plugins/.Sn-License/license.ymland then disables itself, because that file still holds a placeholder. - Paste your bundle key on the first non-comment line of
plugins/.Sn-License/license.yml. - Restart the server. SnRankUp validates the key at startup.
- Edit
plugins/SnRankUp/rankup.ymlto build your ladder, then run/rankup reload.
One key unlocks the whole bundle. plugins/.Sn-License/license.yml is shared by every Sn bundle
plugin on the server, so if you already run one of them the file exists and SnRankUp reads the key
that is already there. Nothing to paste twice.
The key is checked once, at startup. SnRankUp refuses to enable without a valid one, so the server
log is the place to look if the plugin is missing from /plugins.
Updating SnLib always needs a full restart, never a /reload.
First boot
plugins/
.Sn-License/
license.yml your bundle key - shared by every Sn bundle plugin on this server
SnRankUp/
config.yml language, command aliases, database, menu mode, leaderboard, currencies
rankup.yml the ladder: one entry per rank, with its price, rewards and menu item
guis/ the layout of both menus, one file each
rankup-menu.yml the single-button menu, used when menu.mode is single
rankup-list.yml the paginated ladder, used when menu.mode is paginated
lang/
messages_en.yml every line the plugin sends to players and admins
data.db SQLite database, when database.type is sqliteNothing has to be created by hand. Every file above is written on the first boot that passes the
licence check, and the shipped rankup.yml is a working four rank ladder you can rename, extend or
replace.
Dependencies
| Plugin | Required |
|---|---|
| SnLib | Yes |
| Vault | No |
| PlaceholderAPI | No |
Vault and PlaceholderAPI are only needed by the currency types that name them. A ladder priced in
hours alone needs neither.
Updating
Replace the jar and restart. New keys are merged into your config.yml, rankup.yml,
lang/messages_en.yml and guis/*.yml on boot, and your values, comments and additions are
preserved. Example entries you deleted stay deleted.
There is no config-version key and nothing to migrate by hand. Set update-configs: false to
freeze every managed file, and SnLib then only warns about missing keys.