Repository navigation
Ranks and Permissions
GenRaid Setup ships with a full 12 rank ladder split into two tracks: a player track for donors, and a staff track for moderation and administration. Everything below is preconfigured in LuckPerms already. This page explains what each rank includes so you can adjust it to fit your own server.
Player track: Member, VIP, VIP+, MVP
Staff track: Trial Moderator, Moderator, Senior Moderator, Administrator, Senior Administrator, Developer, Head Developer, Manager, Owner
Staff ranks inherit every permission from the player rank below them, so a Moderator also has everything a Member, VIP, VIP+, and MVP has, plus their own moderation permissions. This means you never need to give a staff member two separate ranks.
The Developer rank is the one exception. It branches off separately from MVP and does not inherit any staff moderation permissions. This is intentional, see the Developer section below for why.
Every rank uses the same bracket color, a neutral dark gray, so the bracket itself is not a color statement. The rank name inside the brackets is what changes color, and follows normal conventions players already recognize from other games and servers.
| Rank | Name Color | Style |
|---|---|---|
| Member | #AAAAAA |
Plain |
| VIP | #55FF55 |
Plain |
| VIP+ | #00E5CC |
Bold |
| MVP | Gradient #FFD700 to #FFA500
|
Bold |
| Trial Moderator | #5DADE2 |
Plain |
| Moderator | #2E86C1 |
Bold |
| Senior Moderator | Gradient #2E86C1 to #1B4F72
|
Bold |
| Administrator | #E74C3C |
Bold |
| Senior Administrator | Gradient #E74C3C to #922B21
|
Bold, Italic |
| Developer | Gradient #9B59B6 to #6C3483
|
Bold |
| Head Developer | Gradient #9B59B6 to #6C3483
|
Bold |
| Manager | Gradient #F39C12 to #E74C3C
|
Bold, Italic |
| Owner | Gradient #FFD700 to #FF4500 to #FFD700
|
Bold, Italic |
Developer and Head Developer intentionally break away from the blue to red climb the rest of staff follows. Developers get flagged for different reasons than moderators do, code issues instead of player behavior, so giving them a distinct color makes it instantly clear in chat which kind of staff member someone is looking at.
Owner is the only rank using a three stop gradient. Nothing else on the server should visually compete with it.
Weights control both permission priority in LuckPerms and sorting order in the tab list.
| Rank | Weight |
|---|---|
| Member | 0 |
| VIP | 10 |
| VIP+ | 20 |
| MVP | 30 |
| Trial Moderator | 40 |
| Moderator | 50 |
| Senior Moderator | 60 |
| Administrator | 70 |
| Senior Administrator | 80 |
| Head Developer | 90 |
| Manager | 95 |
| Owner | 100 |
TAB is configured to sort the tab list using this exact order, Owner at the top, Member at the bottom. If you ever add a new rank, you will need to add it to TAB's sorting configuration manually. Setting a LuckPerms weight alone does not automatically change tab list order, TAB has to be told the order separately.
Click a rank below to see its full permission list.
Member
essentials.spawn
essentials.help
essentials.list
essentials.msg
essentials.reply
essentials.afk
axtrade.use
sellwands.use
VIP
essentials.spawn
essentials.help
essentials.list
essentials.msg
essentials.reply
essentials.afk
axtrade.use
sellwands.use
essentials.color
essentials.sethome.multiple.vip
essentials.hat
VIP+
essentials.spawn
essentials.help
essentials.list
essentials.msg
essentials.reply
essentials.afk
axtrade.use
sellwands.use
essentials.color
essentials.sethome.multiple.vipplus
essentials.hat
essentials.nick
MVP
essentials.spawn
essentials.help
essentials.list
essentials.msg
essentials.reply
essentials.afk
axtrade.use
sellwands.use
essentials.color
essentials.sethome.multiple.mvp
essentials.hat
essentials.nick
Trial Moderator
Everything from MVP, plus:
libertybans.warn
libertybans.warn.dur.perm
libertybans.mute
libertybans.mute.dur.7d
essentials.invsee
Trial Moderators can warn and temp mute for up to 7 days. They cannot kick, ban, or issue a permanent mute. This is intentional, see Staff Punishment System for the full reasoning.
Moderator
Everything from Trial Moderator, plus:
libertybans.kick
libertybans.mute.dur.perm
essentials.vanish
Senior Moderator
Everything from Moderator, plus:
libertybans.ban
libertybans.ban.dur.30d
essentials.gamemode.spectator
essentials.gamemode.survival
essentials.tp
essentials.tphere
Senior Moderators can ban for up to 30 days. They cannot issue a permanent ban. This limit is enforced by LibertyBans itself, not just a rule staff are expected to remember.
Administrator
Everything from Senior Moderator, plus:
essentials.gamemode.creative
libertybans.ban.dur.perm
essentials.tpall
essentials.item
essentials.give
essentials.eco
worldguard.region.info
lagg.clear
lagg.check
Senior Administrator
Everything from Administrator, plus:
worldguard.region.bypass
worldguard.region.*
worldedit.*
essentials.fly
essentials.god
essentials.vanish.see
lagg.admin
luckperms.user.permission.set.*
This is the first rank with WorldGuard bypass. Read World Protection and Regions before handing this rank out, since bypass permissions affect how you test your own server too.
Developer
Developer branches off MVP directly and does not include any staff moderation permissions.
essentials.spawn
essentials.help
essentials.list
essentials.msg
essentials.reply
essentials.afk
axtrade.use
sellwands.use
essentials.color
essentials.sethome.multiple.mvp
essentials.hat
essentials.nick
spark.profiler
spark.tickmonitor
bukkit.command.reload
minecraft.command.execute
genraid.debug
This rank is meant for someone handling code and server performance, not player behavior. They cannot kick, mute, ban, change gamemode, or bypass WorldGuard.
Head Developer
Head Developer inherits from both Senior Administrator and Developer. It is not a single step up a ladder, it combines both tracks.
Everything from Senior Administrator, everything from Developer, plus:
fancynpcs.admin
ajleaderboards.admin
deluxemenus.admin
essentials.setspawn
Manager
*
Full server access.
Owner
*
Full server access. Functionally identical to Manager. The real difference between the two is meant to be organizational, Owner is the account holder, Manager is the most trusted staff member below them, not a technical permission difference. If you want a real technical gap between the two, you will need to restrict LuckPerms itself so Manager cannot edit the Owner group.
Manager and Owner both carry the LuckPerms wildcard *, which grants every permission on the server, including ones you did not think about. This is normal and expected for top level ranks, but it has one important side effect you should know about before you start testing your own server.
Wildcard ranks silently bypass systems that are supposed to be restricted, such as WorldGuard region protection and ajLeaderboards' update blocking. If you test your server while logged in as Owner or Manager, you may see things working, or breaking, in ways that will not match what a normal player experiences. Always test protection and player facing features using an account on a lower rank. See Troubleshooting and FAQ for real examples of this causing confusion.
GenRaid Setup
Getting Started
Plugins
Core Systems
- Ranks and Permissions
- World Protection and Regions
- Leaderboards and Podium NPCs
- Spawn Signage
- Staff Punishment System
Help