Hytale server commands are build-sensitive administrative tools. On a current server, begin with /help; it shows the commands, subcommands, and parameters your build exposes. Use /help <family> for a narrower list when that command family supports it. Most management commands require operator or administrator permissions, while the server console may run with full permissions.
Prefer not to run the server on your own PC? Godlike.Host offers hosted Hytale servers with free DDoS protection and up to three free backups a day.
This guide maps the commands documented for the Release 0.7.2 documentation context, including permissions, moderation, player testing, items, teleportation, world state, backups, shutdown, and diagnostics. Hytale remains in active release development, so treat every example as a starting point and verify it locally before using it on a live world.
As an Amazon Associate I earn from qualifying purchases.
How Hytale command syntax works
Use the live server as the authority
Hypixel Studios’ official documentation currently labels its server documentation Release 0.7.2. That label is useful for knowing which documentation generation you are reading, but it does not guarantee that every command behaves identically on every server build. Hytale.game’s searchable index, updated 19 January 2026, lists 159 command results across areas such as Hytale Server, Builder Tools, Command Macro, Universe, Teleport, Permissions, NPC, Inventory, Spawn, and Spawning. That index is best treated as a discovery aid, not a promise that all 159 entries are enabled on your installation.
Run /help in chat or in the server console before copying a command from a guide. If the server supports family help, try /help tp, /help inventory, or another family name to inspect its subcommands and argument order. An “unknown command” result is useful information: it usually means the command is not present, is named differently in your build, or is hidden by your permission level.
#1 Best Overall
- Polished core systems
- Exploration
- Flexible combat
- Robust building
Chat, console, and permissions
In-game commands are entered by pressing Enter and typing a leading slash, such as /help or /kick Alex. HypeServ documents both in-game chat and the server console as execution surfaces and states that the console has full permissions. Console interfaces differ in whether they display or require a slash, so follow the prompt’s convention rather than pasting chat formatting blindly.
Most commands that affect another player, the world, or the server require operator or administrator permissions. If a command works in the console but fails in chat, the syntax may be correct and your in-game permission may be the actual problem.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Read placeholders literally
Angle-bracket text in this guide is a placeholder, not text to type. Replace <player> with a real player name and <number> with digits. Options beginning with two hyphens are named parameters; preserve the two hyphens and the equals sign, as in --quantity=100. When a command offers suggestions or completion in your client, prefer those suggestions because names and IDs can change with content updates.
Become an administrator and manage permissions
Start permission changes from the console when possible, especially if you are locked out of chat administration. The core commands documented for this workflow are:
Rank #2
| Command | Purpose | Scope and risk |
|---|---|---|
/op self |
Grant or remove your own admin permissions, depending on the current state. | Self; reversible, but a mistaken removal can leave you without chat access to repair permissions. |
/op add <player> |
Add a player to the administrator list. | Another player; high privilege and reversible. |
/op remove <player> |
Remove a player’s operator or administrator access. | Another player; reversible if another administrator remains. |
/perm |
Open the permissions-management command family. | Server-wide access control; inspect subcommands with /help perm. |
/sudo |
Run a command as another player, where available. | Impersonates a player’s execution context; use only for controlled moderation or testing. |
Give operator access only to people who need it. Operator status is broader than a single moderation action: it can expose inventory, teleport, world, and server-management capabilities. For a moderator who only needs routine access control, inspect /perm and the permission nodes available on your build instead of automatically using /op add.
Moderation and restricted access
These commands cover immediate player removal, bans, and whitelist administration. Confirm the target name before pressing Enter; similarly named accounts can make an otherwise reversible action disruptive.
Recommended Free Tools
| Command | What it does | Operational note |
|---|---|---|
/kick <player> |
Disconnects a player from the server. | The player can normally reconnect unless another restriction applies. |
/ban <player> |
Bans a player. | Use for a deliberate access decision; document the reason in your moderation records. |
/unban <player> |
Reverses a ban. | Check the exact account name and confirm the player can reconnect. |
/whitelist list |
Shows the current whitelist. | Use before changing access so you know the existing state. |
/whitelist enable |
Enables whitelist-only access. | Players not on the list may be blocked immediately. |
/whitelist disable |
Disables whitelist-only access. | Reopens the server to the normal access rules. |
/whitelist add <player> |
Adds a player to the whitelist. | Verify spelling and capitalization as shown by your server. |
/whitelist remove <player> |
Removes a player from the whitelist. | Removing a player while whitelist mode is enabled can prevent their next connection. |
/plugin |
Opens installed-plugin management where supported. | Inspect /help plugin; plugin subcommands and availability are build-dependent. |
A practical maintenance sequence is to run /whitelist list, add staff accounts with /whitelist add <player>, and then enable the whitelist. Reverse that order when reopening a public server: disable the whitelist only after confirming the intended access list and maintenance work are complete.
Player support, testing, and inventory tools
Several commands are useful for support tickets, moderation investigations, and private test sessions. They can also bypass normal progression, so restrict them to trusted staff and a test world whenever possible.
Rank #3
- 5-Minute Dungeon is the most fun you can have in 5 minutes! You'll need teamwork to defeat each dungeon in only 5 minutes, and then take on the next intense challenge. Defeat all 6 bosses to win!
- Now with 25 more cards and the extra-challenging Dungeon Master: Final Form boss!
- Featuring a free timer app for Android and Apple devices, with six different themed narrators!
- Easy to learn, quick to teach: Match your cards to each symbol in the dungeon deck to win! 5-Minute Dungeon is perfect for teams of 2-5 players aged 8+.
- Includes: 275 Cards, 5 Double-Sided Hero Mats (10 Heroes Total), 3 Double-Sided Boss Mats (6 Bosses Total)
| Command | Documented use | Why to use caution |
|---|---|---|
/heal |
Restores health and stamina. | Can erase the consequences of a survival encounter or affect a live moderation case. |
/fillsignature |
Refills signature energy. | Changes a progression resource rather than merely displaying information. |
/inventory backpack --size=<number> |
Resizes a backpack. | Changing capacity can affect item organization and balance; confirm the accepted size range with /help inventory. |
/inventory clear |
Clears an inventory. | Potentially destructive; obtain confirmation before using it on a player account. |
/inventory see <player> |
Views another player’s inventory. | Accesses player data and should be limited to a stated moderation or support purpose. |
/memories unlockall |
Unlocks all memories. | Alters progression broadly and is better suited to testing. |
/memories clear |
Clears memories. | Potentially irreversible progression loss; verify the exact behavior on a disposable world. |
/kill <player> |
Triggers a player kill. | Can cause item loss or other death consequences depending on the world rules. |
/neardeath |
Exposes the near-death utility documented for the current command set. | Inspect /help neardeath for its current arguments and effect before use. |
/damage <player> --amount=<number> |
Applies a specified amount of damage. | Use a test target and a small amount first; the result may trigger normal damage and death systems. |
If a support request concerns a missing item, prefer inspecting the inventory before changing it. Keep a written record whenever you use a command that changes health, stamina, memories, capacity, or inventory contents.
Give items and build creative test setups
/give grants an item to a player. The examples below are documented item IDs, not a complete catalog:
| Example | Use |
|---|---|
/give Tool_Pickaxe_Cobalt |
Give a cobalt pickaxe. |
/give Tool_Hatchet_Cobalt |
Give a cobalt hatchet. |
/give Bench_Alchemy |
Give an alchemy bench. |
/give Bench_Arcane |
Give an arcane bench. |
/give Bench_Memories |
Give a memories bench. |
/give Ingredient_Bar_Iron --quantity=100 |
Give a stack of 100 iron bars. |
Item IDs are tied to the game’s current content and can change as blocks, tools, or recipes are added. If a sample fails, use command completion or the current item reference rather than trying spelling variations at random. Confirm the recipient and quantity before executing a large grant, particularly on a persistent survival server.
Teleportation, spawn, and world-state commands
Teleport and mode commands are efficient for building, moderation, and recovery, but they can move players into dangerous terrain or bypass intended progression.
Rank #4
- Easy to use interface that is designed for ease of creation
- Interactive education for game server hosting creation
- Provider listings for rental game servers for Hytale that match your criteria
- Simple design to help you navigate the complexity of game server hosting
- Further guides on how to join your server
| Command | Documented role | Check before use |
|---|---|---|
/tp |
Teleport using the command’s player or coordinate forms. | Run /help tp to see the exact argument order supported by your build. |
/tp home |
Teleport to the applicable home location. | Confirm that a home exists and that your build exposes this form. |
/spawn |
Teleport to the server or world spawn. | Useful for recovery, but check whether the destination is safe for the target player. |
/gamemode |
Change a player’s game mode. | Inspect /help gamemode for player and mode arguments. |
/warp set <name> |
Create a named warp. | Choose a unique name and verify the location first. |
/warp go <name> |
Travel to a named warp. | Use only trusted warp names; destinations may change after world edits. |
/warp list |
List available warps. | Review names before deleting or replacing locations through any additional subcommands. |
/noon |
Set or invoke the documented noon-time utility. | Check /help noon because time utilities can vary between releases. |
For coordinate teleports, copy coordinates carefully and test with a staff account. A one-digit error can place a player inside terrain, over a void, or far from the intended build.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Backups, shutdown, and diagnostics
Server-lifecycle commands affect everyone connected. Announce disruptive maintenance in advance, and create a backup before major administrative changes.
| Command | Purpose | Risk and timing |
|---|---|---|
/backup |
Creates a universe backup. | Run before large permission, inventory, world, or plugin changes; allow the operation to finish. |
/stop |
Performs a server shutdown. | Disconnects players and ends the session; use only after announcing maintenance. |
/server dump |
Writes a server-state text dump. | Useful for diagnostics; store the output where staff can retrieve it without exposing sensitive data. |
/server gc |
Forces memory cleanup. | May cause a temporary pause; it is not a substitute for fixing a persistent memory problem. |
/server stats CPU |
Shows CPU statistics. | Capture the result during the slowdown you are investigating. |
/server stats memory |
Shows memory statistics. | Compare repeated samples rather than relying on one instant. |
/server stats GPU |
Shows GPU statistics where available. | Availability depends on the host and build; verify with /help server. |
For a larger community, managed Hytale hosting can simplify console access, scheduled backups, and restart procedures, but confirm that the provider supports the Hytale release you run and exposes the controls your staff need. The commands themselves remain the authoritative way to verify what the live server accepts.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Reliable administrator workflows
First-time setup
- Open the server console or join with an account that already has administrative access.
- Run
/helpand record the command families visible on this build. - Use
/op selfonly if you need to establish your own operator access and understand its current toggle state. - Run
/permand inspect available permission controls before adding other operators. - Add a second trusted administrator with
/op add <player>so one account failure does not lock the team out. - Create a backup with
/backupbefore importing a world, changing access policy, or testing destructive tools.
Private build or event session
- Run
/whitelist listand add approved participants with/whitelist add <player>. - Enable restricted access with
/whitelist enable. - Move builders with the appropriate
/tpform, then use/gamemodeonly for accounts that need it. - Grant test materials with specific
/giveIDs and quantities rather than broad inventory changes. - When the session ends, disable the whitelist only if the server is meant to reopen immediately; otherwise leave it enabled until the next event.
Handling a player incident
- Confirm the account name and gather the relevant chat or server evidence.
- Use
/kick <player>for an immediate, temporary disconnect. - Use
/ban <player>only after the moderation decision is made and recorded. - If the action was mistaken, use
/unban <player>and communicate the correction through your normal staff channel. - Do not use
/sudo,/inventory see,/damage, or/killas casual investigation shortcuts; each changes or exposes a player context.
Planned maintenance
- Announce the maintenance window and ask players to leave dangerous areas.
- Run
/backupand wait for completion. - Capture
/server stats CPU,/server stats memory, or/server stats GPUif the maintenance addresses performance. - Apply the change, then use
/stopfor a controlled shutdown if the server must be restarted. - After restart, run
/help, check whitelist status, and test a low-risk command before inviting players back.
When a command fails
“Unknown command”
Run /help and search the relevant family. The command may have been renamed, moved behind a subcommand, disabled by a module, or removed in your release. Do not assume that a result from the 19 January 2026 Hytale.game index exists unchanged on your server.
Best Value
“No permission” or no visible result
Try the command from the console, which HypeServ describes as having full permissions, or ask an existing operator to test it. If it works in the console but not in chat, review /op and /perm rather than changing the syntax.
The command parses but does the wrong thing
Inspect /help <family> for argument order, target selection, and named options. This matters especially for /tp, /gamemode, /inventory, and /server, where a valid command can still target the wrong player or subsystem.
An item ID or parameter is rejected
Use the current command suggestions and item reference. The /give examples above are content-dependent IDs, and inventory sizes, damage amounts, warp names, and other parameters may have validation rules that differ by build.
A disruptive command caused damage
Stop issuing additional changes, preserve the server output, and restore the most recent known-good backup if necessary. For future tests, use a disposable universe, announce staff actions, and prefer read-only diagnostics such as /server dump before changing player or world state.
Command safety checklist
- Verify syntax with
/helpon the live build. - Confirm the exact player, item ID, quantity, coordinate, or warp name before execution.
- Use the console for recovery when chat permissions are unavailable.
- Keep at least one other trusted administrator account available.
- Back up before inventory, progression, world, permission, or plugin changes.
- Reserve
/kill,/damage,/inventory clear,/memories clear, and broad/giveactions for approved tests. - Announce
/stop, whitelist changes, and other commands that can disconnect or exclude players. - Date your internal command notes because Hytale’s early-access command set can change between releases.
The dependable pattern is simple: discover with /help, execute with the least privilege that solves the task, back up before destructive changes, and verify the result on the server you actually operate.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
