
β sRankup Pro "Speed Studios" ποΈ
SRanks is a fully configurable rankup and prestige plugin with a polished, paginated GUI, an in-game editor for rewards and requirements, custom item rewards, Vault economy support, PlaceholderAPI placeholders and LuckPerms-friendly permissions.
Compatibility
Minecraft: Java Edition
Platforms
Links
Tags
Creators
Details
https://speedstudiosprojects.github.io/sranks/
SRanks
One JAR. Every rankup. Spigot/Paper 1.7.10 β 26.x.
SRanks is a fully configurable rankup and prestige plugin with a polished, paginated GUI, an in-game editor for rewards and requirements, custom item rewards, Vault economy support, PlaceholderAPI placeholders and LuckPerms-friendly permissions.
No addons. No database. No separate builds for old and new servers. Just one Java 8 JAR that runs from 1.7.10 to 26.x.
Status: Beta Β· Version: 1.0.1 Β· Server-side only Β· Java 8+
β¨ Why SRanks?
- Ranks and prestiges fully configurable from YAML.
- Six requirement types that can be combined: money, playtime, XP, items, permissions and placeholders.
- Real rewards: money, console commands, custom items, messages, broadcasts, titles and action bars.
- Configurable GUI with borders, fillers, status lore, pagination, sounds and buttons.
- In-game editor (
/sranks editor) for rewards, commands, items from your hand and requirements. - Optional
/rankupcommand with the same subcommands as/sranks. - One Java 8 JAR for Paper/Spigot 1.7.10 through 1.21.x and 26.x.
- Optional integrations: Vault, PlaceholderAPI and LuckPerms.
- Async persistence, autosave, cached top and playtime tracking.
- No hard dependencies: the plugin starts even without Vault or PlaceholderAPI.
π§© Compatibility
SRanks is compiled against the Spigot 1.16.5 API but generates Java 8 bytecode. Everything newer is accessed through reflection and degrades gracefully when it does not exist.
| Environment | Status | What was checked |
|---|---|---|
| Paper 1.7.10 + Java 8 | Tested | Startup, configs, commands, data and dynamic /rankup |
| Paper 1.8.8 + Java 8 | Tested | Legacy GUI, clicks, pagination, editor, rewards and prestiges |
| Paper 1.21.4 + Java 21/26 | Tested | GUI, Adventure, hex colors, PlaceholderAPI, rankup and prestige |
| Paper 26.3 + Java 25/26 | Tested | Loading, commands, /rankup, Adventure and modern materials |
| Spigot 1.7.10 β 1.21.x | Supported | Same API surface used by SRanks |
| Spigot/Paper 26.x | Supported | Tolerant version detection (for example 26.3.build.231-stable) |
Java runtime: Java 8+ for 1.7.10β1.21.x; Java 25+ for 26.x servers.
π Installation
- Download the JAR and place it in your server's
plugins/folder. - Start the server once to generate the configuration files.
- Optionally install Vault + an economy plugin for money requirements/rewards.
- Optionally install PlaceholderAPI for
%placeholders%and LuckPerms for permissions. - Edit
plugins/SRanks/rankups.yml,prestiges.yml,gui.ymlandmessages.yml. - Run
/sranks reload, then/sranks guior/sranks rankup.
Files created
| File | Purpose |
|---|---|
config.yml |
Prefix, autosave, playtime, Vault, rank detection, compatibility, sounds, top and commands |
messages.yml |
All messages, titles, action bars and editor texts |
gui.yml |
Rank and prestige GUIs: title, rows, borders, fill, templates and buttons |
rankups.yml |
Ranks, requirements, rewards and per-rank GUI overrides |
prestiges.yml |
Prestige levels, reset rank, requirements and rewards |
editor.yml |
Overrides generated by the in-game editor (takes precedence over YAML) |
playerdata/<uuid>.yml |
Rank, prestige and playtime per player |
Existing files are never overwritten. Missing message keys are filled from the JAR defaults.
πΉοΈ Commands
Root command: /sranks (alias /sr).
| Command | What it does | Permission |
|---|---|---|
/sranks or /sr |
Opens the main GUI (console shows help) | sranks.use |
/sranks gui |
Opens the rank GUI | sranks.use |
/sranks rankup |
Attempts to rank up | sranks.use |
/sranks ranks |
Rank list or GUI according to commands.ranks-mode |
sranks.use |
/sranks prestiges |
Prestige list or GUI | sranks.use |
/sranks prestige |
Attempts a prestige | sranks.use |
/sranks info [player] |
Current rank, next rank, progress and requirements | sranks.use |
/sranks top |
Top by prestige, rank and playtime | sranks.top |
/sranks reload |
Reloads configs, messages, GUI, ranks and overrides | sranks.admin |
/sranks set <player> <rank> |
Forces a rank (online or offline) | sranks.admin |
/sranks reset <player> |
Resets to the starting rank | sranks.admin |
/sranks editor |
Opens the in-game editor | sranks.admin.editor |
/sranks help |
Shows the help | sranks.use |
Optional /rankup
Designed for players used to Rankup3. It is registered dynamically and only if the name is free; SRanks never replaces another plugin's /rankup.
commands:
rankup-command:
enabled: true
root: rankup # rankup = try to rank up; gui = open the GUI
/rankup with no arguments runs the configured root action. Subcommands: gui, rankup, ranks, prestiges, prestige, info, top, reload, set, reset, editor, help.
π Permissions
| Node | Default | Purpose |
|---|---|---|
sranks.use |
true |
Basic commands, GUI, rankup, prestige and info |
sranks.admin |
op |
Reload, set, reset and editor bypass |
sranks.admin.editor |
op |
In-game editor |
sranks.top |
op |
View the top |
sranks.rankup.<id> |
optional | Automatic node when a rank has no permission and require-rank-permission is enabled |
A rank's explicit permission: is always required, even when require-rank-permission is false. If a rank has no permission and the toggle is enabled, sranks.rankup.<id> is required.
LuckPerms examples
lp user Name permission set sranks.use true
lp user Name permission set sranks.admin.editor true
lp group admin permission set sranks.admin true
lp user Name permission set sranks.rankup.advanced true
βοΈ Configuration
Rank example
ranks:
apprentice:
order: 1
group: apprentice
display-name: "<gradient:#A0A0A0:#FFFFFF><bold>Apprentice</bold></gradient>"
permission: "" # optional; if set, it is always required
requirements:
money: { amount: 1000, take: true }
playtime: { minutes: 30 }
rewards:
money: 250
commands:
- "say {PLAYER} ranked up from {OLD_RANK} to {RANK}."
message: "<green>You are now <bold>{rank}</bold>!</green>"
gui-item:
material: LEATHER_CHESTPLATE
| Rank field | Description |
|---|---|
order |
Numeric order. Lower comes first. If omitted, file order is used |
group |
Vault group to switch to. Defaults to the rank id |
display-name |
Visible name with MiniMessage/legacy formatting |
permission |
Optional permission. If present, it is always required |
requirements |
Combinable requirements |
rewards |
Money, commands, items, message, broadcast |
gui-item |
Optional GUI item override for that rank |
Prestige example
require-max-rank: true
prestiges:
- id: prestige_1
display-name: "<gradient:#FFD700:#FFAA00><bold>β¦ Prestige {level} β¦</bold></gradient>"
reset-rank: apprentice
requirements:
money: { amount: 100000, take: true }
playtime: { hours: 5 }
rewards:
money: 25000
commands:
- "say {PLAYER} reached prestige {PRESTIGE}."
message: "<gold>Prestige {prestige}!</gold>"
Rank detection
| Mode | Behaviour |
|---|---|
data |
Uses the rank saved in playerdata (recommended) |
vault |
Syncs with the player's primary Vault group on join |
permission |
Finds the highest rank whose permission the player has |
π Requirements
All defined requirements are combined. Each one shows its progress and can consume the resource with take: true.
requirements:
money:
amount: 7500
take: true
playtime:
hours: 2
xp:
levels: 5
take: true
items:
take: true
list:
- material: DIAMOND
amount: 8
- material: EMERALD
amount: 4
data: 0
permission: "sranks.extra.vip"
placeholder:
placeholder: "%statistic_hours_played%"
operator: ">="
value: "10"
| Type | Fields | Consumes |
|---|---|---|
money |
amount, take |
Withdraws money through Vault |
playtime |
seconds, minutes, hours, days, time: "2h30m" |
No |
xp |
levels, points, amount + mode, take |
Levels or total XP |
items |
list of material, amount, data, name, take |
Removes the items |
permission |
string or list of nodes | No |
placeholder |
placeholder, operator, value |
No |
- A bare number in
playtimeis interpreted as minutes. - In
xp, a bare number means levels; usepointsfor total XP. - Items accept
"DIAMOND:8"or full maps. - Every requirement accepts
name:to customise its label.
Placeholder operators
| Operator | Meaning |
|---|---|
>=, >, <=, < |
Numeric comparison when the value is numeric |
==, equals |
Text equality (case-insensitive) |
!= |
Inequality |
contains |
The value contains the expected text |
Requirements can also be a list with type::
requirements:
- type: money
amount: 1000
- type: playtime
minutes: 30
- type: items
take: true
list:
- material: DIAMOND
amount: 8
π Rewards
Rewards run when a player ranks up or prestiges. Each block is isolated: if one item or command fails, the rest still runs.
rewards:
money: 1500
commands:
- "say {PLAYER} ranked up from {OLD_RANK} to {RANK}."
- "lp user {PLAYER} parent set {RANK}"
items:
- material: NETHER_STAR
amount: 2
name: "<gold>Reward</gold>"
lore:
- "<gray>A prize for your effort.</gray>"
glow: true
custom-model-data: 100
message: "<green>You are now <bold>{rank}</bold>!</green>"
broadcast: "<gradient:#FFD700:#FF8C00>β¦ {PLAYER} reached {rank}.</gradient>"
Item fields
| Field | Description |
|---|---|
material |
Modern or legacy material; mapped automatically |
amount |
Amount; split into stacks of 64 when needed |
data |
Legacy data value (1.7β1.12) |
name, lore |
Formatted text with placeholders |
custom-model-data |
CustomModelData on 1.14+ |
glow |
Fake glow; hidden when the version supports it |
skull-owner |
Player name for heads |
enchantments |
List of ENCHANT:level |
skull-base64 |
Base64 head texture |
serialized |
Exact serialized item generated by the editor |
Reward placeholders
{PLAYER}, {RANK}, {OLD_RANK}, {rank}, {old_rank}, {RANK_DISPLAY}, {RANK_ID}, {PRESTIGE}, {OLD_PRESTIGE}
π₯οΈ GUI
The root of gui.yml defines the rank GUI; prestige-gui: defines the prestige GUI. Everything is configurable: title, rows, fill, borders, sounds, buttons and the template for each rank.
title: "<bold><gradient:#00BFFF:#1E90FF>β¦ SRanks β¦</gradient></bold>"
rows: 6
fill: true
fill-item:
material: GRAY_STAINED_GLASS_PANE
name: " "
border:
enabled: true
material: BLACK_STAINED_GLASS_PANE
name: " "
sounds:
open: BLOCK_NOTE_BLOCK_PLING
click: UI_BUTTON_CLICK
rankup: ENTITY_PLAYER_LEVELUP
error: ENTITY_VILLAGER_NO
page: ITEM_BOOK_PAGE_TURN
sounds-volume: 0.8
sounds-pitch: 1.2
rank-slots: [10, 11, 12, 13, 14, 15, 16,
19, 20, 21, 22, 23, 24, 25,
28, 29, 30, 31, 32, 33, 34]
items:
next-rank:
# No slot = template replicated across rank-slots
material: DIAMOND
material-by-status:
current: NETHER_STAR
available: EMERALD
locked: COAL
unlocked: IRON_INGOT
future: STONE
name: "<bold><gold>β€ {rank}</gold></bold>"
lore:
- ""
- "{status}"
- ""
- "<bold>Requirements:</bold>"
- "{requirements}"
lore-by-status:
current:
- ""
- "{status}"
- "<gray>This is your current rank.</gray>"
unlocked:
- ""
- "{status}"
- "<gray>You already passed this rank.</gray>"
glow-when: [current, available]
action: rankup
rank-button:
slot: 49
material: EMERALD
name: "<bold><gradient:#00FF7F:#32CD32>β RANK UP</gradient></bold>"
action: rankup
close:
slot: 45
material: BARRIER
name: "<bold><red>β Close</red></bold>"
action: close
prev-page:
slot: 48
material: ARROW
name: "<bold><yellow>β Previous page</yellow></bold>"
action: prev-page
next-page:
slot: 50
material: ARROW
name: "<bold><yellow>Next page βΆ</yellow></bold>"
action: next-page
Template rules
- An item without
slotis the template replicated acrossrank-slots. - An item with
slotis fixed (header, button, close, etc.). - Content slots paginate automatically.
- Page buttons hide on the first/last page.
- A rank's template can be overridden with
gui-iteminrankups.yml.
Visual states
| State | When it is used | Default look |
|---|---|---|
current |
The player's current rank | Green, ββ Current rankβ |
available |
Next rank and requirements met | Gold, ββ You can rank upβ |
locked |
Next rank with pending requirements | Red, ββ Requirements incompleteβ |
unlocked |
Rank already passed | Green, ββ Completedβ |
future |
Rank after the next one | Gray, ββ Lockedβ |
max |
Player is at the max rank | Gold, ββ¦ Max rankβ |
Actions
| Action | Function |
|---|---|
rankup |
Attempts the next rank |
prestige |
Attempts a prestige |
close |
Closes the inventory |
prev-page / next-page |
Changes page |
prestige-gui |
Opens the prestige GUI |
ranks-gui |
Returns to the rank GUI |
none |
No action |
Per-state customisation
Every template item can change material, name, lore and head per state:
items:
next-rank:
material-by-status:
current: NETHER_STAR
available: EMERALD
locked: COAL
unlocked: IRON_INGOT
future: STONE
name-by-status:
current: "<green>Your current rank</green>"
available: "<gold>Next rank</gold>"
lore-by-status:
current:
- "<gray>This is your current rank.</gray>"
skull-base64-by-status:
current: "eyJ0ZXh0dXJlcyI6..."
serialized-by-status:
current:
==: org.bukkit.inventory.ItemStack
type: PLAYER_HEAD
glow-when: [current, available]
π οΈ In-game editor
The editor lets an administrator configure ranks, prestiges, requirements and rewards from inside Minecraft, without editing YAML by hand.
/sranks editor
| Screen | What you can edit |
|---|---|
| Main menu | Ranks, prestiges, reload and close |
| Rank list | Paginated list with id, group, requirements, commands and items |
| Prestige list | Paginated list with level, reset rank, requirements and rewards |
| Rank editor | Name, group, permission, order, requirements, rewards, commands, items, appearance, test and reset |
| Prestige editor | Name, reset rank, requirements, rewards, commands, items, appearance, test and reset |
| Rewards | Money, commands, items, message, broadcast and test |
| Commands | Add, edit and delete reward commands |
| Items | Add from hand, pick from a GUI, Base64 head, amount and delete |
| Appearance | Item for each state: current, next available, locked, unlocked, future and max |
| Item picker | Central slot for normal or custom items with NBT/commands |
| Requirements | Add, edit, delete, pick item and toggle consumption |
Shortcuts
| Action | Result |
|---|---|
| Left-click a command | Opens chat to edit it |
| Right-click a command | Deletes it |
| Left-click an item | Asks for the new amount |
| Right-click an item | Deletes it |
| Left-click a requirement | Edits its value |
| Right-click a requirement | Deletes it |
| Shift + click a requirement | Toggles whether it is consumed (money/items/XP) |
Type cancel in a prompt |
Cancels and returns to the menu |
Prompts have a 120-second timeout and are validated before saving. The editor does not rewrite rankups.yml or prestiges.yml: it stores only changed fields in editor.yml, which is applied after the base YAML. That preserves your comments and the rest of your configuration.
π Placeholders
Internal placeholders
Usable in messages.yml, gui.yml and rewards:
{player}, {rank}, {next_rank}, {old_rank}, {RANK}, {OLD_RANK}, {PRESTIGE}, {progress}, {progress_bar}, {requirements}, {requirement_money}, {requirement_playtime}, {requirement_xp}, {requirement_items}, {requirement_permission}, {requirement_placeholder}, {playtime}, {page}, {pages}, {status}
PlaceholderAPI
SRanks registers a sranks expansion:
| Placeholder | Value |
|---|---|
%sranks_rank% |
Current rank id |
%sranks_rank_display% |
Visible rank name without formatting |
%sranks_rank_index% |
1-based rank position |
%sranks_ranks_total% |
Total number of ranks |
%sranks_next_rank% |
Next rank id |
%sranks_next_rank_display% |
Next rank name |
%sranks_prestige% |
Current prestige |
%sranks_next_prestige% |
Next prestige level |
%sranks_next_prestige_display% |
Next prestige name |
%sranks_playtime% |
Formatted playtime |
%sranks_playtime_seconds% |
Playtime in seconds |
%sranks_progress% |
Progress 0β100 to the next rank |
%sranks_progress_bar% |
Progress bar |
%sranks_can_rankup% |
true/false |
%sranks_status% |
available, locked or max |
%sranks_requirements% |
Requirements as text |
%sranks_requirement_<type>% |
money, playtime, xp, items, permission or placeholder |
π° Vault and LuckPerms
Vault is optional, but it provides money for requirements/rewards and, when the permission provider supports groups, changes the player's group on rankup.
| Feature | Behaviour |
|---|---|
| Money | Requirements and rewards use Vault's registered economy |
| Groups | With vault.sync-group: true, switches the primary group on rankup |
| Detection | rank-detection.mode: vault syncs with the primary group on join |
| Fallback | If the provider has no group support, use reward commands |
If your Vault provider does not change groups, this is 100% reliable:
rewards:
commands:
- "lp user {PLAYER} parent set {RANK}"
SRanks checks hasGroupSupport(). If it is unavailable, the rankup still works; only the group change is skipped.
β‘ Performance
- Static texts and items are cached.
- Player data is written asynchronously.
- The top reads YAML asynchronously and caches the result.
- Playtime is consolidated on a timer, without disk I/O.
- No unnecessary per-tick loops.
β FAQ
I ranked up but did not receive the money. Check that Vault is installed and that an economy provider is registered. Without one, SRanks warns in console and skips only the money part; commands and items are still delivered. With Vault active, make sure the amount is greater than 0.
/rankup does not exist.
It is disabled by default. Add commands.rankup-command.enabled: true to config.yml and run /sranks reload. If another plugin already uses /rankup, SRanks does not replace it; use /sranks.
The editor does not save my changes.
Check that you have sranks.admin.editor or sranks.admin. Changes are saved to editor.yml; if the file is not writable, check permissions. After saving, SRanks reloads the rank manager automatically.
Where are the editor changes?
In plugins/SRanks/editor.yml. It is an override layer so your comments in rankups.yml and prestiges.yml are not destroyed. To return to the base YAML, use "Reset override" in the editor for that rank or prestige.
How do I give permissions with LuckPerms?
Use the nodes in the Permissions section. For example:
lp user Name permission set sranks.use true and
lp user Name permission set sranks.admin.editor true.
The per-rank permission uses the rank's configured node or sranks.rankup.<id>.
Why do new messages not appear?
Existing files are not overwritten. SRanks merges the JAR defaults for keys missing from messages.yml. If a key does not appear, check that the YAML is valid and run /sranks reload.
How do I change the GUI?
Edit gui.yml: title, rows, fill, border, sounds, rank-slots, templates and buttons. Items without a slot are templates; items with a slot are fixed. You can override a rank's template with gui-item.
How do I deliver a custom item as a reward?
Use "Add item from hand" in the editor. It saves the serialized item (name, lore, NBT, custom model data, enchantments). To configure it by hand, use items: with material, amount, name, lore, etc.
Why does PlaceholderAPI not resolve placeholders?
Check that PlaceholderAPI is installed and compat.placeholderapi-in-text is true. On 26.3, some old PlaceholderAPI builds fail because of their own version parser; use a compatible build.
Does the editor create or delete ranks? No. It edits existing ranks/prestiges, requirements, rewards, commands, items and metadata. Adding or removing ranks is still done in YAML.
π¦ Changelog
1.0.1 β Beta
Current public beta build. See the 1.0.0 notes for the feature set.
1.0.0 β Initial public release (2026-10-30)
Added
- Configurable ranks and prestiges with combinable requirements and complete rewards.
- Paginated GUI with a "your current rank" header, page indicator, states, per-state lore and sounds.
- In-game editor for metadata, requirements, rewards, commands and custom items.
- Per-state appearance for ranks/prestiges, item picker and Base64 heads.
- Optional
/rankupcommand with the same subcommands as/sranks. - PlaceholderAPI, Vault, Vault groups and LuckPerms-friendly permissions.
- One Java 8 JAR for 1.7.10β26.x, with format and material degradation.
- Async persistence, autosave, cached top and overrides in
editor.yml.
Fixed
commandsaccepts a string or a list;itemsaccepts a map or a list.- Money is read from
rewards.moneyand from the top level. - A failed item/command no longer cancels the remaining rewards.
- Vault economy is retried if it loads after SRanks.
- Prestige requirements/rewards defined as a list are parsed correctly.
- Editor sizes/slots fixed to avoid out-of-range errors.
Changed
- A rank's explicit permission is always required; the global toggle only enables the automatic node.
- Existing
messages.ymlfiles receive the new editor keys from the defaults. /rankupis disabled by default and registered dynamically when the name is free.
πΈ Screenshots
SRanks Β· 1.0.1 Beta Β· 2026-10-30

