7 Days to Die Console Commands: The Admin Reference

The 7 Days to Die console is how you run a server day to day: kicking someone, pulling a stuck player out of terrain, checking who is connected, spawning a supply crate, or working out why the server is struggling. This is a working reference for the commands that matter on a dedicated server, organised by what you are trying to do rather than alphabetically. It also flags the handful of commands that can quietly ruin a save, because a couple of the most useful ones are also the most destructive.

Where to Run Commands

On a Loafhosts server, open your server in the LoafHub panel and use the Console tab. Type the command and press Enter, with no leading slash. The console runs with full server authority, so you do not need to be in game or hold an admin rank to use it.

In game, an admin with a high enough permission level opens the console with F1 and types the same commands there.

Tip: The console in the panel acts as the server itself, so it works even when nobody is online

Note: Commands have no leading slash in 7 Days to Die, unlike Minecraft

Finding a Player First

Almost every moderation command needs to identify a player, and this is where most people get stuck. Two commands give you what you need.

Most commands accept a player name, an entity ID, or a platform ID. The entity ID from lpi is the most reliable, because names with spaces or unusual characters cause trouble.

Tip: Run lpi first and use the numeric ID in your command, it avoids every quoting problem a username can cause

Admin Levels and Permissions

7 Days to Die uses numeric permission levels rather than a simple admin flag. 0 is the highest and 1000 is the lowest, which is the reverse of what most people expect. A normal player sits at 1000.

The cp commands are how you build a moderator rank without handing over the whole server. Give a trusted player level 100, then use cp add kick 100 so they can kick but cannot touch anything you have left at level 0.

Note: Permission levels run backwards, 0 is full admin and 1000 is a normal player

Tip: Use cp to expose only the commands a moderator needs, rather than promoting them to level 0

Moderation Commands

A ban needs both a number and a unit, so ban add 171 7 days griefing works and ban add 171 griefing does not.

Tip: say is what your scheduled restart warnings should use, so players get told before the server goes down

Warning: kickall disconnects everyone including you if you are in game

Teleporting

Two commands, and the difference between them matters. teleport moves you. teleportplayer moves someone else.

South and West are negative, so a coordinate can look like tp -200 -1 300. Using -1 for the height is the safe habit, because it drops the target onto the ground rather than inside rock.

Tip: teleportplayer <stuckplayer> <you> is the fastest fix for someone trapped in terrain

Warning: Teleporting a player into solid blocks can kill them, always use -1 for the height unless you know the terrain

Time, Weather and the World

Warning: settime can break anything that depends on elapsed days, including blood moon scheduling. Use it sparingly on a live server

Tip: Run saveworld before any risky change, it is the cheapest insurance available

Items, XP and Testing

These are the commands worth restricting hard with cp. Anything that hands out items or creative mode should sit at level 0 on a server where progression matters.

Warning: creativemenu and debugmenu give effectively unlimited power. Never leave them available to normal players

Note: giveself drops the item at your feet rather than into your inventory, so make room first

Diagnosing a Struggling Server

If a server is stuttering, mem is the first thing to run, because it tells you whether you are looking at a memory problem or something else. version is the first thing to check after any crash, since a mod that has not been updated for the current build is the most common cause.

Tip: Run version after every game update, a mod built for the previous build is the usual reason a server stops starting

Commands That Can Ruin a Save

A short list, worth knowing before you paste something from a forum.

Warning: Take a backup before repairchunkdensity with fix, it modifies world data in place

Tip: shutdown is the clean way to stop a server, because it saves first. Killing the process does not

Settings You Cannot Change From the Console

Some things people expect to set with a command are actually configuration, and a few of those are managed by the panel rather than by the file. On a Loafhosts 7 Days to Die server, the Config Editor handles serverconfig.xml as a form with search, and settings like the server port, player slots, game difficulty, telnet, the web dashboard, and visibility are managed from the Server Settings (Startup) tab instead. They appear in the editor as read-only so you can see their real values without being able to set something that would be overwritten on the next boot.

That is the answer to a common confusion: editing difficulty inside serverconfig.xml on a managed server does nothing, because the startup configuration wins. Change it on the Startup tab.

Note: Player slots and game difficulty are set on the Startup tab, not in serverconfig.xml

Tip: The Config Editor shows locked keys with their real runtime values, so you can confirm what the server is actually using

Frequently Asked Questions

How do I use admin commands in 7 Days to Die?

Open your server in the LoafHub panel and use the Console tab, typing commands with no leading slash. In game, an admin presses F1 to open the console. The panel console runs as the server itself, so it works with nobody online.

How do I make someone an admin in 7 Days to Die?

Run admin add <name or id> <level>, where 0 is full admin and 1000 is a normal player. Get the ID with lpi first. To give a moderator only some commands, leave them at a middle level and use cp add <command> <level> to expose exactly what they need.

How do I find a player’s ID?

Run listplayerids, shortened to lpi, which prints every connected player with their ID. Use listplayers or lp if you also want positions, health and other detail. The numeric ID is more reliable in commands than a username.

How do I teleport a player in 7 Days to Die?

Use teleportplayer, shortened to tele. Either tele <player> <E/W> <y> <N/S> for coordinates, or tele <player1> <player2> to send one player to another. Use -1 for the height so they land on the ground instead of inside terrain.

What is the command to ban someone?

ban add <name or id> <duration> <unit> [reason], for example ban add 171 7 days griefing. Units are minutes, hours, days, weeks, months and years. Lift it with ban remove and review with ban list.

Why does my difficulty change not stick?

On a managed server, game difficulty comes from the startup configuration rather than from serverconfig.xml, so editing the file is overwritten on the next boot. Change it on the Server Settings (Startup) tab instead. The Config Editor shows that key as read-only for exactly this reason.

How do I stop my 7 Days to Die server safely?

Use shutdown from the console, which saves before stopping. Run saveworld first if you want to be certain. Force-stopping the process instead can lose everything since the last save.