Why Proper Staff Ranks Matter
A well-structured staff hierarchy is the difference between a smoothly-run server and constant chaos. When ranks are set up correctly:
- Staff know exactly what they can and can't do
- Players understand the chain of command
- Issues escalate to the right people
- No one accidentally breaks things they shouldn't touch
Let's build a professional staff structure from scratch.
The Standard Hierarchy
Most successful servers use this proven structure:
Owner
└── Admin
└── Senior Moderator
└── Moderator
└── Helper
└── VIP/Donator
└── Member
└── Default
Each rank inherits permissions from ranks below it. An Admin has everything a Moderator has, plus additional powers.
Creating Your Rank Structure
Step 1: Plan Before You Build
Before running any commands, decide:
- How many staff tiers do you need?
- What can each tier do?
- What's the promotion path?
For this tutorial, we'll use: Helper → Moderator → Admin → Owner
Step 2: Create the Groups
With HyperPerms, create each group:
/hp group create helper
/hp group create moderator
/hp group create admin
/hp group create owner
Step 3: Set Up Inheritance
Each rank should inherit from the one below:
/hp group helper parent add member
/hp group moderator parent add helper
/hp group admin parent add moderator
/hp group owner parent add admin
Now permissions flow upward automatically.
Assigning Permissions by Rank
Helper Permissions
Helpers are your front-line support. They answer questions and report issues but can't take major moderation actions.
/hp group helper permission set hytale.chat.color true
/hp group helper permission set hytale.msg.staff true
/hp group helper permission set hytale.reports.create true
/hp group helper permission set hytale.warn true
/hp group helper permission set hytale.teleport.request true
What Helpers CAN do:
- Use colors in chat
- Message staff channels
- Issue warnings
- Request teleports
- Create player reports
What Helpers CANNOT do:
- Kick, mute, or ban players
- Teleport freely
- Access moderation tools
Moderator Permissions
Moderators handle day-to-day enforcement. They keep the peace and handle rule violations.
/hp group moderator permission set hytale.kick true
/hp group moderator permission set hytale.mute true
/hp group moderator permission set hytale.ban.temporary true
/hp group moderator permission set hytale.teleport.* true
/hp group moderator permission set hytale.see.hidden true
/hp group moderator permission set hytale.vanish true
/hp group moderator permission set hytale.reports.view true
/hp group moderator permission set hytale.invsee true
Added capabilities:
- Kick players
- Mute players
- Issue temporary bans
- Teleport freely
- Go invisible
- View player inventories
- View and handle reports
Admin Permissions
Admins handle serious issues and server management. They're trusted with powerful tools.
/hp group admin permission set hytale.ban true
/hp group admin permission set hytale.unban true
/hp group admin permission set hytale.gamemode true
/hp group admin permission set hytale.time.set true
/hp group admin permission set hytale.weather.set true
/hp group admin permission set hytale.whitelist true
/hp group admin permission set hyperperms.user.* true
/hp group admin permission set hyperperms.group.edit true
Added capabilities:
- Permanent bans
- Unban players
- Change gamemode
- Control time and weather
- Manage whitelist
- Edit user permissions
- Edit group settings
Owner Permissions
Owners have full access. Use sparingly—only server owners should have this rank.
/hp group owner permission set hyperperms.admin true
/hp group owner permission set hytale.* true
Or for absolute full access:
/hp group owner permission set * true
Setting Up Prefixes and Suffixes
Visual rank indicators help players identify staff and build community identity.
Prefix Format
HyperPerms supports Minecraft color codes:
| Code | Color | Code | Format |
|---|---|---|---|
| &0 | Black | &l | Bold |
| &1 | Dark Blue | &m | Strikethrough |
| &2 | Dark Green | &n | Underline |
| &4 | Dark Red | &o | Italic |
| &c | Red | &r | Reset |
| &e | Yellow |
Setting Prefixes
/hp group helper meta set prefix "&7[&aHelper&7] "
/hp group moderator meta set prefix "&7[&9Mod&7] "
/hp group admin meta set prefix "&7[&cAdmin&7] "
/hp group owner meta set prefix "&7[&4Owner&7] "
Result in chat:
- [Helper] PlayerName: message
- [Mod] PlayerName: message
- [Admin] PlayerName: message
- [Owner] PlayerName: message
Adding Suffixes
Suffixes appear after the player name:
/hp group vip meta set suffix " &6★"
/hp group moderator meta set suffix " &7[Staff]"
Live Preview
Not sure how your formatting looks? Use HyperPerms' web editor—it shows a live chat preview as you type.
Creating Promotion Tracks
Tracks define the path from one rank to another. With tracks, you can promote staff with a single command.
Create a Staff Track
/hp track create staff
/hp track staff groups helper moderator admin owner
Promote and Demote
Now promoting is simple:
/hp user PlayerName promote staff
They automatically move from Helper to Moderator, or Moderator to Admin, etc.
Demotion works the same:
/hp user PlayerName demote staff
Common Mistakes to Avoid
Mistake 1: Giving Too Many Permissions Early
New staff members should prove themselves before getting more power. Start helpers with minimal permissions and promote based on performance.
Mistake 2: Wildcard Overuse
Avoid giving staff plugin.* wildcards unless absolutely necessary. Wildcards often include permissions you didn't intend to grant.
Mistake 3: No Clear Escalation Path
Document what each rank handles. Helpers shouldn't try to ban players—they should escalate to moderators.
Mistake 4: Forgetting Permission Inheritance
If you set up inheritance correctly, you don't need to re-add permissions. Helper permissions automatically apply to Moderators, Admins, and Owners.
Sample Staff Guidelines
Give your staff clear rules about their powers:
Helpers:
- Greet new players
- Answer basic questions
- Issue warnings for minor offenses
- Report serious issues to moderators
Moderators:
- Mute spam and harassment
- Kick disruptive players
- Issue temp bans (max 24 hours)
- Escalate ban requests to admins
Admins:
- Permanent bans for serious violations
- Whitelist management
- Permission changes for players
- Handle moderator disputes
Owners:
- Server configuration
- Admin appointments
- Final appeal decisions
- Emergency situations
Testing Your Setup
Before going live, verify everything works:
Test Each Rank
Create test accounts or use HyperPerms' check command:
/hp user check HelperAccount hytale.kick
Result should be "false" since helpers can't kick.
/hp user check ModeratorAccount hytale.kick
Result should be "true" since moderators can kick.
Use the Web Editor
The visual editor shows exactly what permissions each group has, including inherited ones. It's the fastest way to audit your setup.
Final Checklist
Before launching your staff system:
- All groups created with proper inheritance
- Permissions assigned to each rank
- Prefixes and suffixes set
- Promotion track configured
- Staff guidelines documented
- Test accounts verified each rank's permissions
- Staff trained on their responsibilities
A well-organized staff hierarchy sets the foundation for a thriving Hytale community. Take time to set it up right, and management becomes almost effortless.
Read the full documentation for advanced features like context-aware staff permissions and temporary role assignments.