Fix common 7 Days to Die server errors

Most 7 Days to Die server problems come from a version or EasyAntiCheat mismatch, a world that’s still being built, or a mod in the wrong place. Find the problem below and follow the steps. The most common ones are first.

Joining problems

The game says your version doesn’t match

Why it happens: the player’s game and the server run different versions. 7 Days to Die updates often, and both sides must match. It’s most common right after an update, or when a player opted into an experimental branch in Steam.

Fix it:

1. Check the version on the game’s main menu, and the server’s version under Settings > Game version.
2. If the game just updated, restart the server so it moves to the new version. Servers follow the newest version by default.
3. Players should use the default branch in Steam (Properties > Betas), not an experimental one.
4. If you pinned the server to an older version, for example to keep mods working, players need to pick that same version in Steam’s betas list.

EasyAntiCheat errors when joining

Why it happens: the player’s EasyAntiCheat (EAC) setting doesn’t match the server’s. A modded server often has EACEnabled set to false, and a player who starts the game with EAC on can’t join it. It also works the other way round.

Fix it:

1. Check EACEnabled in serverconfig.xml.
2. If it’s false, players start the game with EasyAntiCheat off, from the game’s launcher.
3. If it’s true, players start the game normally, with EAC on.
4. If EAC errors appear on a server with EAC on, players verify their game files in Steam (Properties > Installed Files).

The server says it’s full

Why it happens: ServerMaxPlayerCount players are already on. Sometimes a player who crashed still holds a slot for a short while.

Fix it:

1. Raise ServerMaxPlayerCount in Settings, and restart. Keep it at 8 or fewer if console players use crossplay.
2. Set ServerAdminSlots to 1 or 2, so admins can always join a full server.
3. If a slot is stuck, list players with lp in Console. Kick the stuck one with kick Name.

The server doesn’t show in the browser

Why it happens: the server is asleep, still starting, hidden by ServerVisibility, or filtered out by the browser’s settings.

Fix it:

1. Look at Overview. A sleeping server isn’t in the public list. Join with Connect to IP, or open your wake link, then search again.
2. Check ServerVisibility is 2 for public.
3. Clear the browser’s filters and search for the exact ServerName.
4. Add the server to your favourites once you’ve joined, so you can find it again.

Console players can’t see the server

Why it happens: the server isn’t set up for crossplay, or a setting is outside what consoles accept.

Fix it:

1. Check ServerAllowCrossplay is true, EACEnabled is true, IgnoreEOSSanctions is false and ServerMaxPlayerCount is 8 or fewer.
2. Restart and read Console as the server starts. It warns you about settings that block crossplay.
3. Remove mods that players would need to install.
4. Wake the server first with the wake link. A sleeping server isn’t in the console list.

Server problems

The first start takes a very long time

Why it happens: with GameWorld set to RWG, the server builds a whole new random world on its first start. A 10240 world takes much longer than a 6144 one.

Fix it:

1. Watch Console. As long as new lines appear, it’s working. Don’t restart it halfway.
2. Wait. Once the world exists, later starts are much faster.
3. If you’re in a hurry, pick Navezgane or a pregenerated map like Pregen06k01, which are ready straight away.

A mod doesn’t load

Why it happens: the mod is one folder too deep, it’s made for another game version, or it needs EasyAntiCheat off.

Fix it:

1. In Files, check the path is Mods/ModName/ModInfo.xml. If there’s an extra folder in between, move the mod folder up one level.
2. Read Console while the server starts. Red lines that mention the mod tell you what went wrong.
3. Check the mod page for the game versions it supports.
4. If the mod has a .dll file, set EACEnabled to false. See mods.

Settings in serverconfig.xml do nothing

Why it happens: since V3.0, game rules like BloodMoonFrequency, LootAbundance, XPMultiplier and DayNightLength live inside SandboxCode. The game ignores the old lines.

Fix it: make a new code in the game’s Sandbox Options and paste it into Sandbox code in Settings, or into SandboxCode in the file. See blood moon and difficulty settings.

The server crashes on blood moon nights

Why it happens: usually the server ran out of memory with every player’s horde at once.

Fix it:

1. Look at RAM on Overview for the time of the crash.
2. Lower the blood moon zombie count or MaxSpawnedZombies.
3. Move up a plan. See how much RAM you need.

Console shows a helper card with a hint when it recognises a crash.

Still stuck?

Download the latest log from Files and send it to support@wilderack.com with what you tried. Real people read every message.