7 Days To Die Server Admin Commands

Running a 7 Days to Die server properly means understanding the command console inside out. Admin commands are not just cheats. They are the tools that let you moderate players, recover broken situations, diagnose performance problems, and keep your world stable over months of uptime.

This guide is written for real server owners and administrators. Not single-player testing. Not creative messing around. If you are hosting a public or private multiplayer server, this is the reference you want bookmarked.

If you do not yet run your own server, or you want full console access without manual config headaches, you can deploy a ready-to-go server with full admin control on EUGameHost’s 7 Days to Die server hosting here:
https://www.eugamehost.com/7-days-to-die-server-hosting

Quick Fire Commands Overview - Read below to learn how to use these.

Full 7 Days to Die Admin Command List

This is a comprehensive list of commonly available 7 Days to Die console commands. Availability may vary slightly depending on game version and server configuration. Always verify supported commands using help on your server.

General Help

Admin Management

Player Moderation (Kick, Ban, Whitelist)

Player Identification and Lists

Command Permission Control

Debug and Creative Tools

Time and World Control

⚠ Warning: Using settime repeatedly can break timers and events on live servers.

Teleportation Commands

Items, Buffs, and XP

Spawning and Events

Graphics and Visual Debugging

Weather and Environment

Server Diagnostics and Maintenance

What the command console actually does

The command console allows direct interaction with the game engine while the server is running. Through it, you can:

• Manage admins and permission levels
• Moderate players in real time
• Control time, weather, and events
• Spawn items, entities, and quests
• Diagnose lag, memory pressure, and entity overload
• Save, shut down, and safely restart the server

On multiplayer servers, commands can be executed:

• In game if you are an admin
• Via Telnet or a web console on dedicated servers
• Through a hosting control panel if provided

For serious communities, remote access via a panel or Telnet is essential. In-game only admin access does not scale.

How to open the command console

In game

On most keyboards:

• Press F1

Depending on layout, some players may use:

• "
• @
• Regional variants such as Ö or Ñ

When the console opens, you can type commands and press Enter.

Dedicated servers

On dedicated servers, commands are typically executed through:

• Telnet access
• A web console in your hosting panel

If you are hosting with a provider like EUGameHost, you can run commands directly from the game panel without joining the server, which is the correct setup for production servers.

Command syntax rules you must understand

Many command errors come from syntax mistakes, not permission problems.

• Commands may be case sensitive depending on arguments
• Text in <angle brackets> is required
• Text in [square brackets] is optional
• Some commands accept shortcuts, others do not

Always verify supported syntax by running:

help

Or for a specific command:

help ban

Never rely blindly on old command lists. Commands change between alphas and stable releases.

Admin permission levels explained

7 Days to Die uses numeric permission levels:

• 0 is full admin access
• 1000 is a normal player

Lower numbers mean more power.

A sensible real-world permission structure looks like this:

• Level 0: Owner, full control
• Level 10 to 50: Senior admins
• Level 100 to 300: Moderators
• Level 1000: Regular players

This prevents abuse and limits damage if an account is compromised.

Adding and removing admins

admin add <name/entityid/steamid> <level>
admin remove <name/entityid/steamid>

To find a player ID:

lpi

On dedicated servers, admin data is persisted in serveradmin.xml. Treat this file as critical configuration and back it up regularly.

Core player management commands

Listing players

Before taking action against anyone, identify them properly.

lp
lpi

lp shows connected players with stats and position.
lpi shows player IDs, which are safer to use than names.

Server messaging

Broadcast messages to keep players informed and reduce panic during issues.

say <message>

Use this before restarts, during lag investigations, or to issue warnings.

Kicking players

kick <name/entityid/steamid> [reason]
kickall [reason]

Kicks are temporary and should be used as a warning step before bans.

Banning players

ban add <name/entityid/steamid> <duration> <unit> [reason]
ban list
ban remove <name/entityid/steamid>

Supported duration units include minutes, hours, days, weeks, months, and years.

Best practice is progressive discipline:

• Warning
• Kick
• Short ban
• Longer ban for repeat offenders

This protects your community without driving away legitimate players.

Whitelist control

For private servers or events:

whitelist add <name/playerid/steamid>
whitelist remove <name/playerid/steamid>
whitelist list

Whitelist is ideal for closed testing, creator servers, or early access communities.

Command permission control with cp

The cp system controls which permission level can execute specific commands.

cp list
cp add <command> <level>
cp remove <command>

Examples:

• Allow moderators to kick but not shut down the server
• Restrict spawn commands to level 0 only
• Prevent helpers from using time manipulation

This is how you safely delegate power.

Time and world control commands

Viewing time

gettime

Setting time

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

Important warning: Changing time frequently can break timers and world events. Use time commands only for testing or controlled scenarios. For live servers, adjust time settings in configuration files instead.

Teleportation commands

Teleporting is one of the most useful admin tools for support.

tp <E/W> [y] <N/S>
tp <playerid>
tp offset <incE/W> <incy> <incN/S>

Teleporting players:

tele <playerid> <E/W> <y> <N/S>
tele <playerid> <targetplayerid>

Use cases:

• Players stuck underground
• Recovering from chunk errors
• Investigating griefing reports
• Moving players to event areas

Debug and creative commands

Debug mode

dm

Enables debug tools including god mode and advanced menus.

Creative menu

cm

Used for building, testing, and controlled admin events.

These should never be enabled casually on survival servers. Abuse destroys trust quickly.

Item, buff, and XP commands

Spawning items

giveself <itemname> [quality]

Buffs and debuffs

buff <buffname>
debuff <buffname>
buffplayer <playerid> <buffname>
debuffplayer <playerid> <buffname>

Experience

giveselfxp <amount>
giveselfskillxp <skillname> <amount>

These are mainly used for testing, recovery after bugs, or admin-run events.

Entity and event control

Listing entities

listents

Critical for diagnosing lag caused by runaway spawns.

Spawning entities

spawnentity <playerid> <entityid>
spawnscouts
spawnwh

Use carefully. Excessive entity spawning can destabilise servers.

Weather and environment commands

weather <type>
weathersurvival <on/off>
spectrum <mode>

Useful for events, testing biome behaviour, or troubleshooting environmental damage.

Server performance and diagnostics

Memory and system info

mem
systeminfo

Logging diagnostics

loggamestate <message> [true/false]

Manual saving

saveworld

Shutdown

shutdown

Recommended crash response workflow:

1. Announce restart with say
2. Run saveworld
3. Log state with loggamestate
4. Restart cleanly

This significantly reduces world corruption risk.

Common admin mistakes that kill servers

• Giving too many people level 0 access
• Using time commands live instead of config settings
• Spawning entities excessively
• Leaving Telnet exposed without proper security
• Trusting outdated command lists without checking help

Good administration is boring, consistent, and disciplined.

Why hosting environment matters

Many admin issues are not caused by bad commands but by poor hosting setups. Lack of console access, slow restarts, and limited permissions create unnecessary downtime.

If you want:

• Full command access
• Web console and remote admin
• Proper restart controls
• Stable performance for long-running worlds

Use a host built for game servers, not generic VPS setups.

You can deploy instantly with full admin control on:
https://www.eugamehost.com/7-days-to-die-server-hosting

To browse all supported titles and understand how game servers differ from generic hosting, see:
https://www.eugamehost.com/game-servers

Final advice

Mastering 7 Days to Die admin commands is not about memorising everything. It is about understanding which tools to use, when to use them, and when not to.

If you can confidently manage:

• Player moderation
• Teleports and recovery
• Server health diagnostics
• Safe restarts

You are already ahead of most server owners.

If you want next:

• A hardened Telnet and admin config example
• A permission tier template for staff
• Or a full troubleshooting guide for lag and crashes

Say the word and we build it properly.