Hytale Server Commands

I'm going to be unusually brief in this reference guide, and I want to explain why up front: Hytale is in Early Access, and the command set is still changing between builds.

A lot of the "complete Hytale commands" reference guides you'll find online are essentially speculative — they list things like /home, /warp, /sethome, /tp ~ ~10 ~, /setspawn, /pos1, /pos2, /copy, /paste, /fillblocks, /prefab, and dozens more that are borrowed wholesale from Minecraft's Essentials and WorldEdit plugins and have not, to my knowledge, been confirmed to exist in Hytale. I don't want to be one of those guides. I'd rather point you at a small number of commands I've actually seen work, plus /help, than pad this out with a speculative list that's going to mislead somebody.

Running commands

You can run commands either:

• In-game, as an operator, by typing them in chat with a leading /.
• In the server console — via Web Console on your LOW.MS panel, or the server terminal if you're self-hosting. In the console the leading / is usually optional, but including it never hurts and makes it unambiguous.

The single most useful command

/help

Lists the commands your server actually supports. On a new Hytale build this is the authoritative source — much better than trusting a blog post like this one. If you want help on a specific command, most of them accept --help:

/<command> --help

Check this before copying any command syntax from a guide on the internet, including mine.

Server authentication

Every Hytale dedicated server has to complete device authentication on first launch before players can connect. In the server console:

/auth login device

The console prints a URL and a device code; you open the URL in a browser and sign in with your Hytale account. When it prints "Authentication successful!" the server is ready to accept connections.

On LOW.MS this is done for you automatically at provisioning, so you'll never need to run it on a hosted server. If you're self-hosting and hitting auth errors, the dedicated session token troubleshooting guide walks through the flow in more detail.

Stopping the server

/stop

The safe way to shut the server down from the console — it finishes saving the world and any pending state before exiting. On LOW.MS you can also click the stop button at the top of the panel, which does the same thing plus handles the process wrapping.

Restarting is easier to do from the panel (Restart button at the top) than from a console command, especially in Early Access where the reliability of a /restart command varies between builds.

Moderation: kick, ban, whitelist

Every game server in the world has kick, ban, unban, and whitelist commands of some kind, and Hytale is no exception — but the exact syntax varies by build and I'm going to stop short of pasting specific command strings that might be wrong on your server.

The approach I'd recommend instead: start a server, run /help in the console, and see what shows up. You're looking for commands with words like kick, ban, unban, and whitelist in them. Use --help on each one to see the exact syntax for your build.

For whitelist setup, particularly the config-file approach (which is more reliable across builds than command-line fiddling), see the whitelist and password guide.

Server password

There isn't a runtime command to set or change the server password — it lives in config.json. Stop the server, edit the relevant field in config.json (via Configuration Files on LOW.MS, or directly if self-hosting), save, and start the server again. Clear the field to remove the password requirement.

Permissions

permissions.json is a separate file that controls which players or groups have which rights. Some builds have runtime commands for permission management; the syntax has been changing, and I don't want to paste specific strings. The reliable, build-independent approach (edit the file directly with the server stopped) is covered in the permissions and ranks guide.

Teleport, world, and building commands

Hytale's server has a built-in command set, but a lot of what's been written online about it — /tp, /sethome, /home, /warp, /setspawn, /pos1//pos2, /copy//paste, /fillblocks, /prefab — is either borrowed wholesale from Minecraft Essentials and WorldEdit (and not confirmed to exist in Hytale), or was documented on a build that's different from the one you're running.

Rather than pass that along, my advice is:

1. Run /help in the console and see what's actually there on your build.
2. Run <command> --help on anything that looks interesting to see the real syntax.
3. If you need building tools at the scale of Minecraft's WorldEdit, those will be mods rather than base-game commands. The mods installation guide covers how to add them.

I'll expand this section of the guide as the Hytale command set stabilises out of Early Access and gets properly documented. Until then, /help is your best friend.

Why this guide is short

Because being wrong is worse than being brief. A lot of the commands I could have confidently listed six months ago would be wrong today, and a lot of what's in other guides right now is going to be wrong six months from now. I'd rather point you at /help on your actual server than paste in a dozen Minecraft-borrowed commands and hope for the best.

When the command set is stable and Hypixel has published formal documentation, I'll flesh this out properly. In the meantime, the four commands on this page — /help, /auth login device, /stop, and whatever you discover via /help — will carry you through most of the day-to-day running of a Hytale server.