7 Days to Die Admin Commands
In-game and Console tab commands for managing players, spawning items and controlling the server.
Becoming an Admin
From the panel: Settings tab > Player Management > Admins > Add Admin. Leave the platform on Steam, enter your SteamID64 as the Player ID, your in-game name, and a level. This writes the server's serveradmin.xml for you.
Levels the panel offers: 0 (Super Admin), 1 (Senior Admin), 50 (Admin), 100 (Moderator). Anyone not on the list is level 1000, an ordinary player. Lower numbers mean more power.
To find your SteamID64, join once and run "lpi" in the Console tab. It prints connected players with their platform IDs.
From the console: admin add <SteamID64> <level>, for example admin add 76561198000000000 0.
The Console tab runs as the server, so you do not need to be in game and you do not need admin rights to use it. In game, press F1 and your permission level applies.
Cheat Commands (F1 Console)
dm - toggle debug mode.
cm - toggle the creative menu, which gives access to every item.
god - toggle god mode.
fly - toggle fly mode.
noclip - walk through blocks.
killall - kill every zombie nearby.
settime <day/night/time> - set the in-game time. For example settime day, settime night, or settime 1300. WARNING: high risk of breaking timer-related save data.
These change the live game only. They do not change any server setting, and nothing here survives a restart.
Player and Teleport Commands
lpi - list connected players with their platform IDs. This is the command to run first; the IDs are what the rest of these take.
teleportplayer <player> <E/W> <y> <N/S> - teleport a player to coordinates. y=-1 places them on the ground. For example teleportplayer 17189 500 -1 -300.
kick <player> [reason] - disconnect a player. They can rejoin.
ban add <player> <duration> <unit> [reason] - ban a player. Units are minute, hour, day, week, month, year. ban remove <player> lifts it, ban list prints the current bans.
admin add <player> <level> and admin remove <player> - manage admins.
whitelist add <player>, whitelist remove <player>, whitelist list - manage the whitelist. The whitelist is active whenever it has at least one entry.
Everything in this section has an equivalent in Settings > Player Management, which writes the same file and is easier to get right.
World and Server Commands
giveself <item> [quality] - drop an item at your feet. Item names come from items.xml. Quality ranges from 1 to 600.
giveselfxp <amount> - give yourself experience.
spawnentity <playerID> <entityID> - spawn an entity near a player. Run se alone for the entity list. The player ID comes from lpi.
saveworld - force an immediate world save. Run this before a manual restart or a manual backup.
say "message" - speak to everyone on the server.
weather <setting> [value] - control weather. Settings include Rain, Snow, Defaults, and normalize. Value is an optional intensity from 0.0 to 1.0. Type help weather in-game for all options.
listplayers - list connected players with positions, health, stats, and IP addresses. More detailed than lpi.
shutdown - stop the server gracefully. Prefer the Stop button in the panel, which also stops the platform trying to keep the process alive.
help - list the commands available at your permission level.
Where to Run Them
Console tab - the supported path. It talks to the server over the platform's own connection, so there is no password to hold and nothing exposed to the internet.
In-game console - press F1 while playing. What you can run depends on your permission level.
The Telnet interface these run over is bound to the host and is not reachable from outside, so there is no external console to connect to and nothing you need to open.
Running these on a schedule
Any of the commands above can be put on a repeating schedule — an hourly world save, an evening airdrop, a nightly restart sequence with warnings, a buff for everyone who happens to be online — from the Command Manager tab on the Event Manager page.
Scheduling is not simply "the same command, later", which is why it has an article of its own. A wandering horde spawned from a schedule starts at the world centre rather than beside you, because a schedule has no position. The Send to every online player option identifies people by entity ID rather than by name, because a name with a space in it breaks the command. And Shutdown still does not bring the server back on its own.
The full walkthrough, the 25 schedulable commands, and the schedules worth building are in 7 Days to Die Command Manager.