7 Days to Die Server Config Generator

The name shown in the in-game server browser. Make it searchable — people find your server by typing part of this. Defaults to "My Game Host", which is what every un-configured server is also called, so change it unless you enjoy being one of a thousand "My Game Host" entries.

Short blurb under your server name in the browser. One line of "PvE, no wipes, friendly" does more to fill slots than the name does. Defaults to a generic "A 7 Days to Die server".

Optional link to your Discord, rules page, or community site — it shows as a clickable link on the server's browser entry. Empty by default. Worth filling in if you run a community server people might want to find again.

Leave blank for an open public server; set a password to make it private (friends still join via the browser or direct connect with the password). Empty by default. A password is the simplest way to keep a co-op game from filling with strangers.

If set, players see this message and must click "OK" before they finish connecting — handy for a rules notice or a "this server wipes on Sundays" warning. Empty by default (no prompt). Keep it short; it's a popup, not a manifesto.

The region your server is filed under in the browser, so nearby players can filter for low-ping servers. Set it to where the box actually lives, not where you wish it lived — mislabeling it just annoys the players who join expecting good ping. Defaults to NorthAmericaEast.

Default language for server-side text, using the English name of the language (e.g. English, German, French). Defaults to English. Mostly cosmetic for the browser listing — clients still see the game in their own language setting.

This picks the save folder, not just a label. The server stores its world and player data under this name; change it on a live server and you boot into a different — usually empty — save while the old one sits untouched on disk. Defaults to "My Game". Set it once and leave it alone unless you deliberately want a fresh save.

Which map to load: Navezgane (the handcrafted map), PREGEN01–PREGEN03 (pre-generated random maps that ship with the game), RWG (generate a fresh random world from the seed and size below), or the exact folder name of a custom world. Defaults to Navezgane. Only RWG uses the seed and size settings — everything else ignores them.

The text seed used to generate a random world — same seed plus same size always produces the same map. Ignored unless GameWorld is set to RWG; Navezgane and the PREGEN maps don't use it. Defaults to "asdf" (yes, really). Pick something memorable if you might want to regenerate the same world later.

Size of a generated RWG world in metres per side — must be a multiple of 2048, and the engine silently snaps anything that isn't. Bigger maps mean longer generation time and more RAM. Defaults to 6144. Ignored unless GameWorld is RWG. 8192 is a common "big but not punishing" choice.

The base game port. 7DTD actually uses this port plus the next two (port+1 and port+2) for game traffic, so forward all three on your router and leave at least a 3-port gap between servers on one box. Default 26900 opens 26900–26902. Sticking to 26900–26905 or 27015–27020 keeps you in the range Steam's LAN discovery expects.

Who can see the server in the browser. 2 — Public (listed for everyone, the default), 1 — Friends only (only your Steam friends see it), 0 — Not listed (hidden; players must direct-connect by IP). Drop to Not listed for a private game you don't want strangers stumbling into.

Comma-separated list of transports to turn off — the options are LiteNetLib and SteamNetworking. The default disables SteamNetworking, leaving LiteNetLib for direct connections. Disabling the wrong one (or both) kills connectivity, so only touch this if you know which transport your players actually use.

Caps how fast the server sends world chunks to a connecting player, in KiB/s. Higher gets people in-game faster but eats upload bandwidth; lower protects your connection at the cost of longer joins. Default 512, and the engine silently caps the useful maximum around 1300.

Total concurrent players allowed. Default 8. Each extra player costs CPU and RAM and spawns more zombies, so don't set 64 on a box that can barely hold 8 — performance falls off a cliff long before the slot limit on modest hardware.

Slots held open for players at or above the reserved permission level, so regulars can always get in even on a full server. These are taken out of Max Player Count — set 8 max with 2 reserved and the general public can only ever fill 6. Default 0.

The permission level a player needs to claim a reserved slot — anyone at this number or lower qualifies. Remember permission 0 is the owner and 1000 is a default player, so lower means more privileged. Default 100 roughly means "trusted regulars and staff".

Extra slots that open up above Max Player Count specifically for admins, so staff can always join even when the server is genuinely full. Unlike reserved slots, these are bonus capacity, not carved out of the max. Default 0.

The permission level required to use an admin slot — players at this number or lower get in. Default 0, meaning only the server owner / top-level admins qualify. Raise it if you want a wider staff group to share the bonus slots.

TCP port for the web control panel. Default 8080. Only relevant when the panel is enabled, and it must not collide with the Telnet port or your game ports. Forward it only if you actually need remote browser access.

Change this. It ships as the literal string CHANGEME, and if you enable the control panel without changing it, anyone who finds the port has full admin over your server. There is no scenario where leaving it as CHANGEME on an exposed panel ends well.

TCP port the Telnet interface listens on. Default 8081. Keep it different from the control panel port and your game ports. If you ever expose it beyond localhost, firewall it down to your own admin IP.

Here's the safe quirk: leave this empty and Telnet binds to localhost only — reachable from the same machine but not the network, which is the right default for a home server. Set a password and Telnet opens to remote connections, so only do that if the port is firewalled to admins. Empty by default.

How many wrong Telnet passwords an IP can try before it's temporarily banned. Default 10. Lower it to clamp down on brute-force attempts against an exposed Telnet port; 0 disables the limit (not recommended on a public box).

How long, in seconds, an IP stays blocked after hitting the failed-login limit. Default 10. Bump it to minutes if you're seeing persistent brute-force traffic — a longer cooldown makes guessing impractical.

Radius in blocks around a placed bedroll where zombies won't spawn — your safe sleeping area. Default 15. Larger zones make a base feel safer but can suppress spawns over a wide area; smaller zones keep the danger close. This is spawn suppression, not a force field — wandering zombies can still walk in.

Real-world days a bedroll stays active after the owner last logged in, before the game stops treating it as their spawn. Default 45. Lower it to clean up abandoned spawns on a busy server; raise it so occasional players don't lose their respawn point between sessions.

The master PvP switch. 0 — No killing makes it a pure PvE server (nobody can hurt anyone). 1 — Kill allies only, 2 — Kill strangers only (party-safe PvP), and 3 — Kill everyone (full free-for-all, the default). Pick 0 for co-op survival, 2 for a friendly-fire-off PvP server.

How close party members must be (in blocks) to share kill XP and quest credit. Default 100. Larger ranges let a spread-out party still share rewards while clearing a big POI; smaller ranges require you to actually stick together. Mostly matters for co-op quest progression.

Players at or below this character level get a protected zone around their spawn where enemies won't spawn — new-player breathing room. Default 5. Raise it to shield newcomers longer on a tough server; set 0 to disable the protection entirely. Works with Safe Zone Hours below.

How many in-game hours a new player's safe zone lasts. Default 5. Combined with Safe Zone Level, this gives fresh spawns a finite grace period to find their feet before the world turns hostile. Longer hours = gentler onboarding; 0 turns it off.

How many land claim blocks each player can have placed at once. Default 1 (one protected base). Raise it to let players protect a main base plus outposts or a horde base — common on co-op servers — but more claims means more of the map locked down per person.

Width in blocks of the square protected area, centered on the claim block. Default 41 (a 41×41 footprint). Keep it odd — an even number can't center perfectly on the keystone, so the game expects odd values. Bigger claims protect more but let players wall off larger chunks of the world.

Minimum spacing in blocks between one player's claim and another player's, so people can't box each other in. Default 30. Larger dead zones spread bases out and reduce griefing-by-proximity; smaller ones let a tight-knit group cluster their bases together.

Real-world days a player can be offline before their land claim stops protecting their base and it becomes vulnerable. Default 7. Raise it so people who play weekly don't come back to a raided base; lower it to recycle abandoned bases faster on a busy server. Works together with the decay mode below.

How protection fades while a player is offline, up to the expiry time. 0 — Slow/Linear (default) eases protection down gradually, 1 — Fast/Exponential drops it off quickly, and 2 — None keeps the base fully protected right up until the expiry moment, then it's open. Choose 2 for a forgiving server, 1 for a cutthroat one.

Multiplier on block hardness inside a claim while the owner is online. Default 4 (blocks are 4× tougher to destroy). Higher = harder to raid; set it to 0 and claimed blocks become outright indestructible — not unprotected, indestructible. That's the single most misread land-claim setting, so be deliberate with 0.

Same hardness multiplier, but for when the owner is offline. Default 4. Again, 0 means indestructible, not unprotected — set it to 0 and an offline player's base literally cannot be damaged (great for casual servers, terrible for PvP raiding economies). Pair with the offline delay below.

Minutes after a player logs off before the offline durability modifier kicks in. Default 0 (offline rules apply immediately). Set it to, say, 30 so a player who rage-quits a raid doesn't instantly get the offline protection bonus — a common anti-abuse tweak on PvP servers.

Hard cap on the total number of zombies alive across the entire map at once. Default 64. This overrides Blood Moon Enemy Count — if the per-player horde math exceeds this number, this wins. It's also the biggest performance lever: pushing past ~80 hurts framerate and server tick on most hardware, big group or not.

Whole-map cap on living animals (deer, boars, wolves, bears, etc.) at once. Default 50. Like the zombie cap, it's a performance dial — lower it on a strained server, but go too low and hunting for food and hides gets frustratingly sparse.

The farthest view distance (in chunks) the server lets clients request. Default 12 (the max). The engine silently clamps this to the 6–12 range, so values outside it do nothing. Lowering it reduces how much world the server has to stream and simulate per player — a real win on a busy or under-powered box.

How many explored map chunks the server stores per player before old ones get trimmed. Default 131072 (effectively "all of it"). It controls memory used by each player's revealed map; the default is generous, and you'd only lower it on a server pushing extreme map exploration into RAM limits.

Extra chunk buffer around each land claim where dynamic mesh still applies, so destruction near the edge of your base still behaves correctly. Default 3. Larger buffers extend the realistic-collapse zone outward at some CPU cost; only matters with Land Claim Only mode on.

How many dynamic mesh regions the server keeps cached in memory at once. Default 3. Higher uses more RAM in exchange for smoother repeated destruction in the same areas; keep it low on a memory-constrained server. Only relevant with Dynamic Mesh enabled.

Controls where admin command usage is logged (or hidden). 0 — Show all (default), 1 — Hide from Telnet/panel, 2 — Also hide from remote, 3 — Hide everything. Hiding it keeps nosy co-admins from seeing every command you run, but it also reduces your own audit trail — leave it at 0 unless you have a reason.

The permission level a player needs to use Twitch integration features on the server. Default 90. Remember lower numbers are more privileged (0 = owner, 1000 = default player), so 90 limits Twitch features to fairly trusted players. Raise it toward 1000 to let everyone use it.