Hytale Server Commands and Admin Permissions: The Ultimate Guide

Hytale Server Commands and Admin Permissions: The Ultimate Guide

A Hytale dedicated server is managed from its console and from in-game chat. Hytale server commands let you kick and ban players, give items, change time and weather, and manage permissions without restarting. This guide lists the commands the server actually ships, read from the server files of build 0.7.3, and shows how operator status and permissions.json really work.

Establishing Initial Administrator Access (OP)

A fresh server has no operators. Run the command in the server console, where the leading slash is optional (the console strips it). If you host with Supercraft, the console is in your control panel.

op add PlayerNameOrUUID

The argument is a UUID or the username of a player who is online. The server replies "{name} is now an operator!", and a player who is online is told they have been made an operator. For a player who is offline, use their UUID. op remove takes the same argument and reverses it.

An operator is simply a member of the built-in hytale:Admin group. There is no deop command: use op remove.

/op self exists, but on a multiplayer server it only works when the server was started with the --allow-op flag. Without the flag it tells you to add yourself to permissions.json while the server is off, or to launch with the flag.

Essential Gameplay Commands

These are the day-to-day commands. Several need more than the default permissions: for example /time needs the hytale:WorldEditor group, so only operators and editors can use it.

• /gamemode <adventure|creative> [player], alias /gm. Hytale has two game modes, Adventure and Creative; there is no Survival mode.
• /give <item> gives an item to yourself, and /give <player> <item> gives it to an online player. Options are named: --quantity <n>, --durability, --quality and --metadata, for example /give <item> --quantity 10. /give armor hands out armor by search text such as Iron.
• /tp <x> <y> <z>, /tp <player> <x> <y> <z>, /tp <targetPlayer> and /tp <player> <targetPlayer>; /teleport is an alias. Coordinates accept relative values. /tp all, /tp home, /tp top, /tp back, /tp forward and /tp world <name> are sub-commands.
• /time shows the world time, /time <hour 0-24> or /time set <hour> sets it, and /time dawn, /time midday, /time dusk and /time midnight jump to a period (aliases: day and morning for dawn, noon for midday, night for dusk). /time pause freezes the clock and /time dilation <value> (above 0.01, up to 4, Admin group only) speeds it up or slows it down.
• /weather set <weather> forces a weather, /weather get shows the forced weather and /weather reset (alias clear) goes back to the normal cycle.
• /kill <player> kills and respawns a player.
• /say <message> (alias /broadcast) announces to everyone, /who lists who is online, /maxplayers [amount] sets the player limit, /backup runs a backup of the universe and /stop (alias /shutdown) stops the server.

Essential Moderation Commands

• /kick <player> disconnects a player. They can rejoin immediately. The command takes no reason.
• /ban <player> [reason] bans the player's account by UUID, with an optional reason that is stored with the ban (otherwise "No reason."). /unban <player> lifts it. Bans are saved in bans.json.
• /whitelist add|remove <player>, /whitelist enable (alias on), /whitelist disable (alias off), /whitelist status, /whitelist list and /whitelist clear manage the whitelist, which is saved in whitelist.json.
• /voice mute <player> and /voice unmute <player> silence a player's voice chat, and /voice muted lists who is muted. These need the Admin group.

/pardon does not exist, so use /unban. There is also no IP ban, no timed ban and no text-chat mute command in this build. Bans are by account.

Advanced Permissions: The permissions.json File

Permissions are node based. permissions.json sits in the server's working directory, next to config.json, and the server reloads it with /perm reload. Users are keyed by account UUID, not by username.

Built-in groups

The server ships a ladder of groups, each inheriting from the one before it: hytale:None, hytale:Adventurer (the default for every player), hytale:Builder, hytale:WorldEditor, hytale:ServerEditor and hytale:Admin, which holds the wildcard *. Older group names still work: op maps to hytale:Admin, creative to hytale:WorldEditor, and default, adventure and adventurer to hytale:Adventurer.

Example

{
  "users": {
    "11111111-2222-3333-4444-555555555555": {
      "groups": ["moderator"]
    },
    "66666666-7777-8888-9999-000000000000": {
      "permissions": ["hytale.system.command.time"]
    }
  },
  "groups": {
    "moderator": {
      "parent": "hytale:Adventurer",
      "permissions": [
        "hytale.system.command.kick",
        "hytale.system.command.ban",
        "hytale.system.command.unban",
        "hytale.system.command.tp"
      ]
    }
  }
}

A user entry can carry groups and permissions; a group entry can carry parent and permissions. Commands that declare no node of their own, such as kick, ban, unban, whitelist and stop, use hytale.system.command.<name>, and a sub-command adds its own name. Others declare a node: /op add needs hytale.command.op.add, /gamemode needs hytale.command.gamemode.self or .other and /give needs hytale.command.give.self or .other. Plugins use their own base permission. /perm list --all prints every node your build has registered, which is the reliable list. Players need the node hytale.server.join to join when RequireJoinPermission is on in config.json.

You rarely need to edit the file by hand. /perm group add|remove <group> <permissions>, /perm user add|remove <uuid> <permissions>, /perm user group add|remove <uuid> <group>, /perm list [--all] and /perm test do the same from the console, and /setgroup <group> [player] sets a player's group (your own when you leave the player out).

Remote console

This build has no RCON. The server console is the standard input of the server process, and a hosting panel's console tab sends commands to it. To run commands at start, launch the server with --boot-command and a comma-separated list; they run in order.

Conclusion

Keep the Admin group small, give moderators only the command nodes they need, and use /op add instead of editing files while the server runs. Set up your moderator group before you open the server to the public.

If you're looking for a hosting platform that makes managing consoles, FTP, and configurations effortless, choose Supercraft Server Hosting. With a custom-built panel tailored for Hytale, managing your community has never been easier.