Questions? Chat with us.
© Haptic, LLC*30% off applies automatically at checkout for your first month. Ends September 30, 2026.
HytaleGuideOperators, the whitelist, and bans all live in the Admins tab of your server's Overview card. Search the player by Hytale username or UUID, pick a role,…
Operators, the whitelist, and bans all live in the Admins tab of your server's Overview card. Search the player by Hytale username or UUID, pick a role, click Add Player, then Save changes. If your server is running when you save, the change applies within seconds and no restart is needed. Nothing here touches your worlds or player data.
Hytale identifies players by account UUID, not by display name. The search box (Search Hytale username or UUID...) looks the UUID up for you, so usually you just type the name.
If it answers Player not found., ask the player to type /uuid in Hytale's chat and search that instead. Both searches use the same player lookup, so if the UUID comes back not found too, that account cannot be added from the Admins tab yet: there is no add-by-hand option. Try again later.
Open My Servers, open your server, and click the Admins tab on the Overview card.
Type the username or UUID and press Enter.
On the player card, pick Operator next to Role:, then click Add Player.
Click Save changes in the popup at the bottom of the page.
Operators get every server permission (Hytale's OP group) and can run admin commands in game. Owning the server on Haptic does not make your character an operator, so add yourself first.
To take a role away, click the trash icon (Remove player) on that row and save.
Search each friend, pick Whitelist, and click Add Player. Add yourself too.
Flip the whitelist toggle at the top of the tab. A Warning! dialog reminds you that non-listed players cannot join; confirm with Enable Whitelist.
Click Save changes.
The text beside the toggle tells you where you stand: "Whitelist is active: Only listed players can join." or "Whitelist is off: Anyone can join." If you only want a door key rather than a guest list, a server password is the simpler tool.
The enabled flag inside whitelist.json is managed by us and rewritten to false on every start, because Hytale's own reader chokes on it otherwise. The real on/off state is the dashboard toggle, so setting that flag over SFTP changes nothing. The player list in the same file is respected as usual.
Search the player and pick Banned next to Role:. A Reason: field appears; type up to 128 characters, or leave it empty.
Click Add Player, then Save changes.
The reason is saved with the ban and shows as grey text under the player's role in the roster. To change it, remove the row and save, then add the player back with the new text and save again: doing both in one save leaves the running server untouched. To lift a ban, remove the row and save.
A ban applies as soon as you save, as long as the server is running. If the player is somehow still connected, run kick <player> from the Console card.
No, as long as the server is running when you hit Save changes. The save sends the matching console commands to your server (op add, op remove, whitelist add, whitelist remove, ban, unban, whitelist enable, whitelist disable), which is why the pending-restart indicator you see for other settings never appears for these.
Two cases to know:
Saved while the server was offline. The popup notes that if your list files were edited directly, those edits win when the server starts. Start the server, then check the Admins tab and redo anything that did not stick.
A command was refused. If the running server rejects one, a warning appears after the save (it names the command when only one failed). Restart the server to apply those changes from the saved lists.
The same jobs work from the Console card using UUIDs: op add <uuid>, whitelist add <uuid>, ban <uuid>, unban <uuid>, whitelist enable, plus who for who is connected. Console changes go to the list files, and the Admins tab picks them up from those files on the next server start, not right away.
On disk the lists are permissions.json, whitelist.json, and bans.json at the root of your server files. Edits there win when the server starts, and the roster updates to match (apart from the whitelist enabled flag above). If one of those files has a syntax error, the server uses it as-is and roster syncing pauses until you fix it; a note in the Admins tab names the file. See Edit config files if you prefer working that way.
Reach us on Discord or at support@haptic.gg. Include your server name, the player's username and UUID, and a screenshot of the Admins tab.
Play Hytale on Haptic!
One subscription, every game