Try: water, woda, how to cure infection, motocykl
Show more results →Dedicated server: configuration, Sandbox and admin commands
Select the correct world, configure rules and learn a safe update procedure with essential admin commands.
Description
A dedicated server stores the shared world and player progress. Its configuration controls access and the selected save; Sandbox controls gameplay rules. This guide concerns the modern PC server, including V3.x.
First start
Install 7 Days to Die Dedicated Server through Steam Tools or SteamCMD. Keep server and client files separate if their versions must be independent. Copy the configuration supplied with that server version into your own configuration file.
Set the server name, private password, player limit and world. Launch the server using that configuration file. Check the log for completed world loading, test a local connection, then test internet access. A running process alone does not prove players can connect.
Settings that are easy to confuse
First decide whether you are creating a world or continuing an existing save. The names below are configuration settings, not console commands.
| Setting | Meaning |
|---|---|
| GameWorld | Existing world name, or RWG for generation. |
| GameName | Game save name; changing it can start another save. |
| WorldGenSeed / WorldGenSize | Seed and size for a newly generated map, not restored progress. |
| UserDataFolder | Directory for worlds, saves and user data. |
| ServerPort | Main port, default 26900. Additional ports depend on transport configuration. |
| ServerVisibility | Browser visibility; not a substitute for a firewall or password. |
| SandboxCode | Gameplay settings code compatible with the game version. |
Sandbox without carrying obsolete settings forward
Choose options in the Sandbox interface of the same game version and copy its generated code into server configuration. Keep a readable record of your rules too. A code from another version does not guarantee identical behavior; check settings migration messages after updating.
Change one group of rules at a time. Day length, horde frequency, loot abundance, biome progression and XP affect different systems. Crossplay additionally requires compliance with the publisher’s limits.
Useful administrator commands
On PC, F1 normally opens the console. On a server, use an authorized administrator account. help lists commands; help followed by a name shows syntax for that version. Read player IDs from the player list rather than guessing from similar names.
| Command | Purpose |
|---|---|
| help / help <command> | Command list and exact syntax. |
| listplayers (lp) | Connected players and their identifiers. |
| gettime | Current world time. |
| saveworld | Request a world save; still stop the server before backup. |
| say "message" | Message to players. |
| kick <player> "reason" | Disconnect a player. |
| help ban | Ban syntax including duration and reason. |
| help admin | Syntax for granting and removing privileges. |
| shutdown | Clean server shutdown. |
Updates, access and troubleshooting
Before updating, inform players, shut down cleanly, make a backup and review game and mod compatibility. Afterwards, verify the correct save loads and clients can join. If the release requires a fresh world, preserve the old backup.
Do not expose Telnet or an admin dashboard publicly without access restrictions and authentication. Grant only necessary permissions. For a fault, collect the version, error message and corresponding log excerpt, removing passwords and private information.
Debug commands, creative items and time changes are not routine world repairs. They can alter gameplay and achievement availability. Experiment on a separate copy.
Worked example
To move an existing base, copy the save and matching world, retain GameName, select the correct GameWorld and run a compatible version. Re-entering the old seed generates terrain; it does not restore the base.
Common mistake
Updating a running server process or starting the old world with an accidentally changed save name.