Every Hytale server needs a permissions system. Without one, every player has the same access, and that's a problem the moment you want moderators, builders, or VIP ranks. HyPerms is a permissions plugin built for Hytale that handles groups, per-player permissions, inheritance, and chat formatting out of the box.

This tutorial covers everything you need to get HyPerms running: creating groups, assigning players, setting up chat prefixes, and a few tips to keep things organised as your server grows.

Quick Command Reference

What You Want to Do	Command
Create a group	/hyp group create <group>
Add a permission to a group	/hyp group add <group> <perm>
Set a group as default	/hyp group default set <group>
Add a player to a group	/hyp user addgroup <player> <group>
Set a group prefix	/hyp group prefix <group> <text>
Set chat format	/hyp chat format <text>
Reload config	/hyp reload

Before You Start

You'll need hyperms.all or OP access to run HyPerms commands. If you're the server owner, you likely already have this. If you're setting up permissions for a staff member to manage, grant them hyperms.all once you've got your groups configured.

Install HyPerms like any other Hytale plugin, drop it into your mods folder, and restart the server. Once it's loaded, all commands use the /hyp prefix.

Creating Your Group Structure

Most servers follow a similar pattern: a default group for new players, a few staff ranks, and maybe a donator or VIP tier. Here's a sensible starting setup:

/hyp group create member
/hyp group create helper
/hyp group create moderator
/hyp group create admin

Then set member as the default group. This is the group every new player gets assigned to automatically:

/hyp group default set member

You can check which group is currently the default at any time with /hyp group default.

Setting Up Inheritance

Inheritance lets a group automatically receive all the permissions of another group. This saves you from duplicating permissions across every rank. The idea is simple: moderators should have everything helpers have, plus their own extra permissions.

Set it up like a chain:

/hyp group inherit helper member
/hyp group inherit moderator helper
/hyp group inherit admin moderator

With this in place, any permission you give to member automatically applies to helper, moderator, and admin too. Any permission you give to helper flows up to moderator and admin, and so on. You only need to add the permissions specific to each rank.

Adding Permissions to Groups

With your structure ready, start assigning permissions. The exact permission nodes depend on whatever other plugins you're running, but here's an example to give you the idea:

/hyp group add member essentials.home
/hyp group add member essentials.spawn
/hyp group add member essentials.msg

/hyp group add helper essentials.mute
/hyp group add helper essentials.kick

/hyp group add moderator essentials.ban
/hyp group add moderator essentials.tp

/hyp group add admin hyperms.all

Because of inheritance, helpers already have essentials.home, essentials.spawn, and essentials.msg from the member group. You're only adding the extra nodes they need.

To remove a permission, swap add for remove:

/hyp group remove helper essentials.mute

You can check what a group has at any point with /hyp group info <group>.

Managing Individual Players

To put a player into a group:

/hyp user addgroup Simon moderator

One thing to note: adding a player to a group automatically removes them from the default group. So if Simon was in member, he's now only in moderator.

You can also give individual players specific permissions without changing their group. This is handy for one-off cases where someone needs access to a single command:

/hyp user add Simon someplugin.specialcommand

To check what permissions and groups a player currently has:

/hyp user info Simon

Chat Formatting

HyPerms includes built-in chat formatting, so you don't need a separate plugin for rank prefixes in chat. There are two parts to this: setting prefixes for your groups, and configuring the chat format string.

First, give each group a prefix:

/hyp group prefix member &#aaaaaa;Member
/hyp group prefix helper 7FF55;Helper
/hyp group prefix moderator &#FFAA00;Mod
/hyp group prefix admin &#FF5555;Admin

The &#RRGGBB syntax lets you use hex colours. You can also use legacy colour codes like &a for green or &c for red if you prefer. For bold or italic text, use &l and &o.

Then set up the chat format. This controls how every message appears in chat. Use these placeholders:

Placeholder	Output
%prefix%	The player's group prefix
%suffix%	The player's group suffix
%player%	The player's name
%message%	The chat message content

There's one quirk to know about: you need to use | (pipe) instead of spaces in the format command. Here's an example that produces a clean rank tag followed by the player name and message:

/hyp chat format &#FF0000;[%prefix%]|%player%|&7»|&f%message%

This would display something like: [Mod] Simon » Hello everyone!

Check your current format at any time with /hyp chat.

A Note on HyPerms Pro

HyPerms has a Pro tier that adds a browser-based admin panel (Web GUI) and remote management. If you manage a larger server or prefer not to do everything through in-game commands, it's worth looking into. You can purchase a licence through the HyPerms Discord, activate it with /hyp license <key>, and the web panel runs at http://your-ip:8080.

For most small to mid-sized servers, the free version covers everything you need.

Get Your Server Listed

With your permissions configured and rank prefixes showing in chat, your server is ready to make a good first impression. A clean rank structure signals to new players that your server is well run, and that matters when people are browsing Hytale servers looking for somewhere to play.

If you haven't already, list your server with us to get it in front of players searching for the best Hytale servers. It's free, takes a couple of minutes, and helps your server show up on our Hytale server list alongside other top Hytale servers.

Tips for Keeping Things Tidy

Permissions setups tend to get messy over time. A few habits that help:

• Use inheritance properly. If you find yourself adding the same permission to multiple groups, it probably belongs in a lower group that the others inherit from.
• Avoid per-player permissions where possible. They're useful in a pinch, but if multiple people need the same access, make a group for it.
• Use /hyp group info regularly. Before adding permissions, check what the group already has through inheritance. Duplicate entries won't break anything, but they make troubleshooting harder.
• Reload after config changes. If you've edited config files directly, run /hyp reload to apply changes without restarting the server.
• Document your setup. Keep a simple list of your groups, what each one is for, and any non-obvious permission nodes. Future you will appreciate it.

Troubleshooting Common Issues

Player doesn't have the right permissions after being added to a group: Check that the group actually has the permission with /hyp group info <group>. Also verify the player is in the correct group using /hyp user info <player>. If everything looks right, try /hyp reload.

Chat format not showing prefixes: Make sure you've set a prefix for the group with /hyp group prefix, and that your chat format string includes %prefix%. Remember to use | instead of spaces in the format command.

Inheritance doesn't seem to work: Double check the direction. /hyp group inherit moderator helper means moderator inherits from helper, not the other way around. The first group is the one receiving the extra permissions.