Terraria administration depends on which server layer you are using. A vanilla TerrariaServer instance accepts a fixed set of commands in its dedicated-server console, while player chat has only a few slash commands. TShock is separate server software that adds accounts, permissions, protection features, warps, and plugins.
For routine vanilla administration, the essential commands are playing, kick, ban, save, say, motd, password, and exit. Enter them in the server console without a leading slash. If you need in-game administration, per-user permissions, build protection, or plugins, install TShock and complete its authentication and administrator-account setup instead.
What are Terraria server admin commands and where do I enter them?
There are three command interfaces, and commands from one interface should not be assumed to work in another.
| Interface | Where you type | What it provides |
|---|---|---|
| Vanilla TerrariaServer | The dedicated-server console window | Built-in moderation, world-time, messaging, status, saving, and shutdown commands |
| Vanilla player chat | In-game chat, with a leading slash | A small player-facing set such as /playing, /p, and /me |
| TShock | TShock’s server software and in-game slash-command system | Accounts, groups, permissions, protection, warps, plugins, and additional administration |
Vanilla console commands generally do not need /. For example, type playing, not /playing, in the dedicated-server window. The same command appears as /playing when a player runs it from game chat.
Wait until the server has finished loading a world before issuing administrative commands. Keep the console open while the instance is running: it is the authoritative control surface for a vanilla server. Use the exact player name shown by playing, and replace angle-bracket placeholders such as <message> with your own text; do not type the brackets themselves.
How do I use the vanilla TerrariaServer console commands?
Start TerrariaServer, wait until the world is running, and type a command at the server console prompt. Commands that take a value use a space followed by that value, as in motd Welcome! or password NewSecret. If you are unsure which commands a particular build exposes, run help in that same console.
General, status, and session commands
| Command | Result |
|---|---|
help |
Displays the available command list. |
playing |
Shows connected players. |
clear |
Clears the console window. |
version |
Prints the server version. |
time |
Displays the current game time. |
port |
Displays the listening port. |
maxplayers |
Displays the configured player limit. |
password |
Shows the current server password. |
These status commands are useful after a restart or configuration change. For example, version, port, and maxplayers provide a quick check that the intended build, network port, and capacity are active in memory rather than merely present in a file.
Moderation and communication commands
| Command | Result |
|---|---|
kick <player name> |
Disconnects the named player. |
ban <player name> |
Bans the named player. |
say <message> |
Broadcasts a yellow server message to players. |
motd |
Displays the current message of the day. |
motd <message> |
Changes the message of the day. |
Use say for information that everyone currently connected should see, such as a warning that maintenance is about to begin. The MOTD is a standing welcome message, so use motd <message> for a change that should greet players on future connections during that server run.
World control and statistics
| Command | Result |
|---|---|
dawn |
Sets the world to dawn. |
noon |
Sets the world to noon. |
dusk |
Sets the world to dusk. |
midnight |
Sets the world to midnight. |
settle |
Settles all water in the world. |
death |
Displays player or server death statistics as supported by the game version. |
pvpdeath |
Displays supported player-versus-player death statistics. |
alldeath |
Displays supported all-player death statistics. |
allpvpdeath |
Displays supported all-player PvP death statistics. |
The time commands are immediate world controls, not chat messages. Coordinate them with players before changing the cycle during an event or boss fight. The death-statistics commands can vary with the game version, so treat the output shown by your running build as authoritative.
Saving and shutting down
| Command | Use it when |
|---|---|
save |
You want to write the current world state to disk. |
exit |
You want to save and shut down normally. |
exit-nosave |
You intentionally want to shut down without saving the current session. |
Use exit-nosave only when discarding the current session is deliberate. For planned maintenance, run save, notify players with say, and then use exit. A normal shutdown is preferable whenever players have built, stored items, or changed the world since the last save.
A practical vanilla administration pass
- Run
playingand note who is connected. - Send a warning with
say Maintenance begins in five minutes.if you need to stop or alter the world. - Use
kick <player name>for a temporary removal orban <player name>for a ban. - Run
savebefore planned maintenance or configuration work. - Finish with
exit, then restart using the intended startup command or configuration file. - After startup, verify
version,port,maxplayers,motd, andpasswordas appropriate.
How do I kick or ban someone on a Terraria server?
First identify the connected player, then apply the appropriate moderation command from the server console.
- Run
playingto display the connected-player list. - For a temporary removal, enter
kick <player name>. - For a ban, enter
ban <player name>. - Use
say <message>if the remaining players need an explanation or maintenance notice.
The vanilla command list documents the kick and ban actions but does not provide a separate unban command in the built-in console list. If you need richer moderation workflows, user groups, or permission-specific commands, TShock supplies that broader administration layer. Keep the spelling and spacing of the name exactly as it appears in playing; if a command does not match a player, refresh the list before trying again.
How do I change the Terraria server password or MOTD?
Password and message-of-the-day changes are made immediately from the console with a value after the command.
passwordshows the current password.password <new password>changes it.motddisplays the current message of the day.motd <new message>changes the message shown to players.
For a setting that should survive a restart, put the value in the server’s startup configuration rather than relying only on an interactive console change. After restarting, query password and motd to confirm that the running process loaded the intended values. Handle the password as an administrative secret: avoid posting it in a public announcement and use a strong value when staff or community members share access.
What startup parameters control a vanilla Terraria server?
TerrariaServer accepts command-line parameters for startup and persistent operation. The exact syntax depends on the server build, so confirm the options exposed by the version you run.
| Purpose | Parameters documented for TerrariaServer |
|---|---|
| Configuration and world selection | -config, -world, -worldname, -autocreate, -seed |
| Capacity and networking | -port, -players, -maxplayers, -ip |
| Access and security | -pass, -password, -banlist, -secure |
| Messages and discovery | -motd, lobby settings, announcement-box controls |
| Platform and network behavior | -steam, -noupnp |
| Process behavior | Priority controls |
Use -config <file path> to load a configuration file. A config file can persist the world path, world name, autocreation size, seed, difficulty, maximum players, port, password, MOTD, ban-list path, security mode, language, UPnP behavior, NPC streaming, process priority, and Journey Mode power permissions. Keeping these values in one file makes a restart reproducible and avoids retyping sensitive or operational settings.
World-selection options matter when several worlds exist on the host. -world identifies the world path, while -worldname supplies a world name; -autocreate and -seed apply when creating a world rather than simply loading an existing one. Capacity and network options belong in the same startup record as the password, MOTD, ban-list path, and security setting so that the process can be restarted consistently.
The configuration surface also includes less visible operational choices: language, UPnP behavior, NPC streaming, process priority, announcement-box controls, lobby settings, and Journey Mode power permissions. These are useful when the server’s behavior must be repeatable across restarts, but check the syntax accepted by the exact TerrariaServer build before editing a file.
Which values should be checked after changing startup settings?
- Run
versionandportafter startup to confirm that the intended server build and listening port are active. - Run
maxplayersto verify the player limit. - Use
motdandpasswordwhen you need to confirm the current in-memory values. - Check the selected world path before launching if more than one world is available.
- Confirm that the launch shortcut, service definition, or script points to the same file passed to
-configthat you edited.
Which commands can players use in Terraria chat?
Player chat is not the dedicated-server console. The documented vanilla chat commands are limited and require a leading slash.
/playingshows the player list in game chat./p <message>sends party chat./me <message>displays third-person text.
Do not present /p or /me as administration commands, and do not assume that a console command becomes available to ordinary players merely by adding a slash. A player can use /playing in chat, but commands such as save, kick, ban, and exit remain server-console operations on a vanilla installation.
What is TShock, and when is it better than the vanilla console?
TShock is third-party desktop server software from Pryaxis. The Official Terraria Wiki describes it as adding an in-game administration system, build protection, warping, plugin support, minor server fixes or tweaks, and access to hidden world settings.
Choose TShock when administration must happen in game, when different staff members need different permissions, or when you want protection and plugins. Stay with vanilla when a fixed console command set and configuration-file startup are sufficient and you do not want to maintain an additional server software layer.
TShock commands, groups, and permissions depend on the TShock installation and any enabled plugins. They are not an extension that can be typed into an otherwise vanilla TerrariaServer process. Adding TShock therefore changes the operational model: staff accounts, groups, database files, plugin versions, and compatibility checks become part of routine maintenance.
Which TShock version should I install?
The retrieved Official Terraria Wiki metadata lists TShock 6.1.0 as compatible with Terraria 1.4.5.6. Compatibility is version-sensitive, so check the current TShock release notes and the Terraria version you actually run before installing; do not treat that pairing as permanent. A Terraria update can require a corresponding TShock release, and plugins may have their own compatibility requirements.
How do I install TShock and become a TShock administrator?
The first administrator is created through an authentication bootstrap sequence. Perform it on the machine that hosts the server, or connect locally while the server is starting.
- Download the latest TShock release and extract it to a normal folder. Do not run it directly inside the compressed archive; the official guide warns that doing so can cause settings to be lost when the server shuts down.
- Start TShock and select an existing world or create a new one.
- Choose the server port. The Pryaxis getting-started guide gives
7777as the default Terraria server port. - Read the authentication code printed by the server.
- Join the server locally with
localhostor127.0.0.1when the server is running on the same computer. - In game chat, enter
/auth code, replacingcodewith the value printed by the server. - Create the administrator account with
/user add <username> <password> superadmin. - Log in with
/login <username> <password>. - Enter
/authto finish the setup.
Do the commands in that order. The printed auth code belongs to the current server session, so using an old code or connecting to a different instance can prevent the bootstrap from completing. Local connections through localhost or 127.0.0.1 avoid confusing the first setup with a different host or port.
The official TShock Getting Started documentation states: “The SuperAdmin account contains all privileges on your server. It’s important that your password is strong, long, and hard to guess.” Use a unique, long password because this account can perform every administrative action exposed by the installation. Once the first account works, give ordinary staff only the groups and permissions they actually need rather than sharing the SuperAdmin credentials.
What if TShock must be reset completely?
A full reset is destructive to TShock’s account and authentication setup. The guide identifies tshock.sqlite inside the tshock folder and auth.lck beside TerrariaServer.exe; deleting those files removes users and returns the installation to its pre-installation state. Stop the server first and make a backup before deleting anything. This is a reset procedure, not a routine way to recover a forgotten password.
What is the difference between TerrariaServer and TShock?
| Area | Vanilla TerrariaServer | TShock |
|---|---|---|
| Command surface | Fixed built-in console commands such as kick, ban, save, and say |
Broader command ecosystem, with additional commands supplied by TShock and plugins |
| Entry point | Dedicated-server console; startup flags and a config file for persistent values | TShock server software, in-game slash commands, and TShock administration |
| Permissions | Access is effectively tied to whoever can operate the server console | Accounts, groups, permissions, and a SuperAdmin role |
| Persistence | Command-line parameters and a server configuration file | TShock account and database setup, plus its own configuration and plugin data |
| Protection and extensibility | Built-in functions only | Build protection, warping, plugins, and additional server tweaks |
| Operational cost | Fewer components to update and troubleshoot | More capability, but compatibility and plugin maintenance become part of administration |
There is no command-by-command conversion between the two systems. A vanilla operator who moves to TShock must install and start the replacement software, create accounts, and review permissions. Conversely, a TShock operator who temporarily launches a vanilla server should expect only the built-in console list and no TShock users, groups, or plugins.
How do I troubleshoot common command and setup problems?
A command is rejected in the console
Check that you are typing into the dedicated-server console and that the spelling matches the built-in list. Remove the leading slash when using the vanilla console. Run help to display the commands exposed by that server build. If a command is listed in a TShock guide, verify that TShock is actually the process running the world.
A player cannot run an administration command from chat
That is expected on a vanilla server: most administration commands belong to the server console. Player chat has only the documented slash commands. Install and configure TShock if you need authenticated in-game administration.
The server starts on an unexpected port or with the wrong player limit
Inspect the active launch command and the file passed to -config. Then confirm the result in the running server with port and maxplayers. A stale shortcut or service definition can load a different config file than the one you edited.
The world or MOTD is not the one I expected
Check the world path, world name, and MOTD values in the active startup configuration, then compare them with the running output. If multiple worlds or configuration files exist, confirm the launch entry points to the intended file before restarting. Use motd after startup to see the in-memory message.
TShock settings disappear after shutdown
Make sure the extracted files are being run from a normal directory rather than from inside the compressed download archive. The official TShock guide specifically warns that archive-based execution can lose settings at shutdown.
The TShock authentication sequence does not work
Use the code printed by the current server session, connect through localhost or 127.0.0.1 when appropriate, and complete the sequence in order: /auth code, /user add, /login, then /auth. Check that the TShock build supports the Terraria version you launched and that the account command includes the superadmin group.
A shutdown might lose recent work
If preserving the current session matters, run save and use exit. Reserve exit-nosave for an intentional discard. Announce the shutdown first with say so players have a chance to stop building or leave safely.
Should I use vanilla TerrariaServer or TShock?
Use this decision checklist:
- Choose vanilla if one trusted operator can access the console and you mainly need player moderation, announcements, saves, time controls, and startup configuration.
- Choose TShock if staff need in-game commands, separate accounts, granular permissions, build protection, warps, or plugins.
- Test compatibility first when Terraria or TShock has recently updated, because TShock support is tied to specific game versions.
- Back up before changes when editing world paths, switching server software, or resetting TShock authentication files.
- Plan for maintenance when using TShock: its additional capabilities also mean account, database, plugin, and version upkeep.
The simplest reliable workflow for a vanilla server is playing, moderate with kick or ban, announce with say, save with save, and shut down with exit. TShock is the appropriate next step when those console-only controls no longer provide the permissions or protection your community needs.
Frequently Asked Questions
Why did my Terraria server settings vanish after I closed TShock?
The TShock Getting Started guide warns that running the program directly inside its compressed archive can cause settings to be lost at shutdown. Extract the release to a normal folder and launch it from there.
What port does a new TShock server use by default?
The Pryaxis getting-started documentation gives 7777 as the default Terraria server port. Confirm the active value with the server’s port setting if you changed it during startup.
Can I use TShock commands on a normal TerrariaServer installation?
No. TShock is separate server software, so its users, groups, permissions, and plugins are available only after TShock itself is installed and running.
What files are removed by a complete TShock authentication reset?
The documented reset removes TShock users and returns the installation to its pre-setup state by deleting tshock.sqlite in the tshock folder and auth.lck beside TerrariaServer.exe. Stop the server and make a backup before doing this.
Do vanilla Terraria console commands need a slash?
Generally no. Type commands such as playing, save, kick, ban, or exit directly in the dedicated-server console. The slash is used for the corresponding player-chat form, such as /playing.
How do I safely stop a vanilla Terraria server?
Run save if you want to write the current world state, notify players with say, and then use exit for a normal saved shutdown. Use exit-nosave only when intentionally discarding the current session.
Why can a player use /playing but not kick or ban someone?
Vanilla player chat exposes only a small slash-command set, including /playing, /p, and /me. Kick and ban are built-in server-console commands; authenticated in-game administration requires TShock.
What should I verify after editing a TerrariaServer config file?
Confirm that the launch command uses the intended file with -config, then check version, port, maxplayers, motd, password, and the selected world after startup. A stale shortcut or service definition may load a different configuration.
Is the TShock 6.1.0 and Terraria 1.4.5.6 pairing permanent?
No. That compatibility pairing is version-sensitive. Check the current TShock release information against the Terraria version you actually run before installing or updating.
The Bottom Line
Use the vanilla TerrariaServer console for the fixed command set: check players with playing, moderate with kick or ban, announce with say, save with save, and shut down with exit. Put recurring world, network, password, MOTD, and security settings in a configuration file. Move to TShock when you need authenticated in-game administration, groups, build protection, warps, or plugins, and complete its auth-code and SuperAdmin setup carefully.