How to add an admin on a Hytale server
Grant Hytale admin access from the server Console after authentication. Having the player join first gives you a current identity to target. Prefer a limited permission group over blanket op, and confirm current /op syntax with /help on the running build.
Grant Hytale admin access from the Console after the server is
authenticated. Having the player
join first gives you a current identity in Console to target. Update 5 replaced
gamemode-tied rights with groups, inheritance, and namespaced nodes, so you can
give someone a role instead of full /op. Confirm the grant command on
your build with /help — Early Access syntax moves.
The first owner almost always grants from Console. In-game chat only works after that account already has the matching permission.
First owner path
Authenticate the server
The Server Manual says a dedicated server can accept player connections
only after authentication. Finish
server authentication first
(/auth login device on berrybyte, or the same command on a self-hosted
console).
Join with the account you want to grant
Start the server, then join with that account so its current name or identifier appears in Console. This avoids guessing which identity the command expects. See Join your Hytale server if you still need the address.
Open Console and read /help
On berrybyte, open the server's Console tab. Self-hosted operators
use the dedicated-server console. Run /help and look up the current
/op (or permission-group) family for this patch. Update 6 notes say
console /help prints a formatted list and per-command usage; Update 5
already added in-game tab-complete and a suggestion UI.
Grant from Console, not from chat
If /help lists /op add and /op remove, those are the Console
commands this build uses to grant or revoke operator access. Use the
identifier /help prints (do not assume username vs UUID). Prefer a
limited group when /help shows a way to assign one — Update 5
explicitly tells you not to /op friends just to share a role.
Do not copy /op add argument lists from hosting blogs. Official Update 5
notes name /op as the old full-access path and do not publish a stable
signature. If /help on this server does not list /op add / /op remove,
use the family it does list.
Update 5 groups and permissions.json
Update 5 stopped tying permissions to gamemode. You assign a group (a
role) with the nodes that job needs. Groups can inherit, nodes are
namespaced, and /help shows the permission a command requires.
permissions.json is the official on-disk file for that configuration. The
Hytale Server Manual
puts it next to config.json, whitelist.json, and bans.json. The same
manual is explicit about persistence:
- The server reads these files on startup.
- It writes them when permission commands run.
- Manual edits while the server is running are likely overwritten.
Let the running server write permissions.json via Console commands when
you can. Stop the server first if you must edit the file by hand, then
start it so it reloads your change.
Do not invent built-in group names, UUID layouts, or permission node strings.
Update 6 patch notes name some nodes (for example hytale.server.join for
whitelist), but the reliable lookup is still /help on the build you are
running. Give the smallest group that covers the work.
Console vs in-game
| Where | Who can run privileged commands | Typical first-owner use |
|---|---|---|
| Console (berrybyte Console tab, or dedicated-server stdin) | The server itself. Use this before anyone has in-game rights. | Auth, first grant, /help, whitelist, /stop |
| In-game chat | Only accounts that already have the matching permission node or group | Day-to-day admin commands after the first grant |
In-game tab-complete (Update 5) helps once you have rights. It does not bypass a missing permission.
When a grant fails
| Symptom | Likely cause | What to try |
|---|---|---|
| Command unknown or no usage text | This patch uses a different family or spelling | Run /help and use only what it lists |
| Player not found / no effect | They have not joined, or the identifier does not match this session | Have them join, copy the name or id from Console join lines, retry |
| Works in Console, refused in chat | The client lacks that permission | Grant from Console first; then test in-game |
| Rights gone after a restart | permissions.json was edited while the server was online, or never written | Grant again from Console, or stop, edit, then start |
| Nobody can join to be granted | Server is still unauthenticated | Finish authentication |
A working grant is enough to run the operations command reference. Pair it with a whitelist if the world should stay private. More Hytale guides live on the Hytale hub.
If a grant still fails after the table above, open a
support ticket with the server
linked and the exact /help / Console lines attached.
Frequently asked questions
How do I op a player on a Hytale server?
Authenticate the server, have the player join so Console shows the current identity, then grant access from the server Console. Update 5 still refers to /op as the old full-access shortcut. Run /help on your build for the current /op syntax instead of copying host blogs.
Why did my Hytale admin command fail?
The usual causes are a player who has never joined, a name or identifier that does not match this session, a command your patch does not ship, or an in-game client that lacks the matching permission. Retry from Console after the player is online, and confirm the exact family with /help.
What is permissions.json on a Hytale server?
It is the official permission configuration file next to config.json. The server reads it on startup and writes it when permission commands run. Stop the server before any manual edit, or your change can be overwritten. Prefer granting a limited group over editing the file by hand.
Do I need to restart after granting Hytale admin access?
A successful Console grant is written by the running server, so you normally do not restart just to apply it. Restart if you edited permissions.json on disk while the server was stopped. If you edited that file while it was online, the next save can wipe the edit.
Should I give every trusted player full op on Hytale?
No. Update 5 moved permissions off gamemode and onto groups so you can give someone only the commands they need. Blanket op is the blunt tool. Use the smallest group that covers the job, and confirm nodes with /help rather than guessing them.