7 Days to Die Console Commands for Server Admins

7 Days to Die console commands for server admins work through an admin-capable in-game console, the server’s local Telnet interface or a hosting panel. They do not run when pasted into the Linux dedicated server’s stdin. This guide groups the useful commands by task and checks their names against the current stable server so you can identify players, announce a restart, check the clock, save the world and stop cleanly. If you are comparing a web panel for these jobs, use our control panel tasks to test first to check player tools, logs and task status.

For the focused teleportplayer syntax and destination checks, see how to teleport players on a 7 Days to Die server.

Choose where to run server commands#

Use the console that fits where you are and how your server is managed. A dedicated server has no game window for you to open, so an admin usually connects to the world from a PC and uses F1, or sends commands through Telnet or a host’s web panel.

Do not paste commands into the dedicated-server process’s stdin and wait for a reply: this server ignores stdin. Linux does not add a special terminal command mode; use the in-game route, a local Telnet connection or a panel console instead. If you are choosing between self-management and handing off the machine, see how to choose a 7 Days to Die host.

If you want common admin jobs in a browser, Game Hosting is our managed 7 Days to Die recommendation. Its panel has quick actions for saving, listing players, announcements, game time and the next horde, while the Players tab handles routine player actions from the selected account. That lets you reserve the text console for commands outside the shortcuts. See the 7 Days to Die server panel to compare that workflow with running the machine yourself.

The server command registry changes with game builds. The version checked for this guide was V3.2.0 b10, build 24994542; The Fun Pimps lists V3.2.0 Stable and the newer V3.3.0 Experimental b18 separately. If you run an experimental build, modded server or later update, ask its own console for help and help <command> before relying on a remembered alias.

List players and use the ID the server recognizes#

Run lp to list connected players. The full command is listplayers; both names reach the same command in the V3.2.0 b10 server tested for this guide. The output gives you each connected player and their platform identifiers, including Steam_… and EOS_… IDs.

Use the ID shown by the server when an account command asks for a player. Do not substitute an assumed Steam ID for an EOS ID, or guess from a display name that another player may share. The output is useful for identifying the account attached to this server session; it is not a history of players who have already disconnected. If you need to find a player’s ID outside the live list, use a dedicated lookup method rather than treating lp as a global search.

The shorter lp form is handy in a panel console, but the longer name is easier to recognize in notes. Both were returned by the V3.2.0 b10 help output. If either form returns “unknown command” on your server, check the running build and type help listplayers; do not copy a command list from a different version and assume it still applies.

Give admin rights without guessing at the level#

The admin command manages server admin entries. Check the current list with admin list; adding an account follows this shape:

admin add <player-id> <level> "<display name>"

The live V3.2.0 b10 help text confirms that 0 is the highest permission level and that players without an explicit level default to 1000. A display name is optional. That does not mean every trusted friend should receive level 0: use the level your group has agreed on, then grant only the people who need to operate the server.

If the command is rejected, check that the ID is a platform ID from the server, that the command is available on this build and that the account running it has permission to change admin entries. A successful admin entry also does not mean that every server command should be available to that account. The command permission system can set required levels separately; see its output before changing defaults. This guide does not map every level to a role, and it does not replace a careful permissions plan.

admin add accepts an ID, a level and an optional display name. Avoid putting a password or other private account detail in a display-name field: that name is shown as an admin label, not used to authenticate anyone. For a precise privilege matrix, check help admin and help cp on the build you actually run.

For current V3.3 syntax to kick, ban or whitelist a player, see our admin commands for moderating a server guide.

Announce maintenance to everyone online#

Use say when you need to tell connected players what is about to happen. For example:

say "Server restart in five minutes; log off now."

The command sends a server message to all connected clients. It is useful before a planned restart, a scheduled event or maintenance that will interrupt play. Keep the message specific: say what will happen and when, then give players time to reach safety and log out.

An announcement is only a message. It does not save the world, start a timer or stop the server. If you want routine reminders and restarts to happen on a schedule, use the scheduler in your server panel or follow a separate restart guide. For a one-off change, send the warning first, wait for the time you promised and then run the save and stop commands in order.

If you want a separate web or desktop tool to automate commands, compare the connection method and permissions in our guide to 7 Days to Die server managers.

If nobody sees the message, confirm that players are still online and that the command ran from a server-capable console. Typing say into a local single-player client is not the same as sending a server announcement to everyone connected to a dedicated world.

Check the clock before changing it#

gettime reports the current in-game day and time; its alias is gt. shownexthordetime reports when the next wandering horde is due. Use those read-only checks before you alter the world clock, especially when players are coordinating around an event.

The server’s help settime lists these forms:

settime day
settime night
settime <time>
settime <day> <hour> <minute>

For example, settime 3 12 0 sets day 3 to noon. settime changes the world clock; check gettime first and tell players before making a change. If you were only trying to learn when the next horde arrives, run shownexthordetime instead of moving the clock. For the persistent game rules that shape a world, use the V3 server settings reference rather than old standalone difficulty properties from an obsolete serverconfig.xml guide.

Aliases are conveniences, not a promise that every version or mod recognizes the same set. If gt or st fails, use the full command name or ask the server’s own help output. Avoid changing time as a way to test a command while the group is playing: the change affects everyone in that world.

Save before you stop the server#

saveworld writes a manual world save; its alias is sa. shutdown stops the game server. Saving first gives the server a chance to write the current world before you take it offline for maintenance.

1. Save the current world

   Send saveworld from an admin-capable console and wait for the server to finish the command before continuing.

2. Stop the game server

   Send shutdown when players are clear and you are ready to take the world offline. The command stops the game; it is not a restart command.

3. Confirm the server is stopped

   Check the panel or the server process status before editing files or starting maintenance. If the server is still running, do not assume that the shutdown request completed.

The distinction matters: saveworld does not stop the process, and shutdown does not mean “restart in a few minutes.” A panel may leave the server stopped until you press Start; check its status instead of assuming it will come back by itself. If you are editing configuration or replacing a save, stop the server first and keep a separate backup of the files you plan to change.

Both command names and descriptions came from help on V3.2.0 b10. The version in your panel or server log is the one that matters if an alias is unavailable. Do not kill the process just because the console appears quiet; confirm the status and give its save-and-stop sequence time to finish.

Read server health and command access#

mem prints memory information and exposes garbage-collection controls; the help output does not list an alias. Treat it as a diagnostic command, not a target to tune by copying random values from a forum. The information is a snapshot of the server process, not a guarantee that a particular amount of memory is enough for every map, player count or overhaul.

The command permission tool is cp, short for commandpermission. Start with cp list to see configured command requirements. On V3.2.0 b10, the help text says that a command with no explicitly configured requirement defaults to level 0. That default is separate from the rule that an account without an explicit admin level defaults to 1000.

Do not mix those two settings up: one describes a player’s admin level, the other the level required to run a command. If an admin cannot run something, check both the account entry and the command requirement before changing either. The cp add, cp remove and cp list subcommands can alter or inspect that policy; this guide only uses the list view. Keep access changes deliberate, and avoid pasting an old permission file over the one your server currently uses.

When a command or alias is missing, ask the running server rather than guessing:

help
help <command>

The first lists the commands registered in that server build; the second returns the matching command name, alias and available help text. That quick check is the safest way to separate an outdated list from a command that is simply outside your account’s permissions.