Your 7 Days to Die server will not start after adding a mod

Take the newest mod out and start the server again. If it starts, that mod is the cause: update it or leave it out. The game's log, logs/latest.log, usually names the mod that failed.

Find the mod

1. In the panel, start the server. While the game loads, the Console shows only Waiting for telnet connection..., so a mod error does not appear there.
2. Open Files, then logs, then latest.log.
3. Read the last lines. Look for a mod name next to an error.

Take it out

1. Stop the server if it is still trying to start.
2. Open Files, then Mods.
3. Download the mod's folder with Download folder to keep a copy, then delete it with Delete folder.
4. Start the server.

If you added several mods at once, take them all out, then put them back one at a time with a restart after each.

Why a mod stops the server

• It was made for another game version. A game update is the usual moment this happens.
• It needs another mod that is missing.
• Two mods change the same thing in different ways.
• It is a code mod and its .dll does not match the game, or EasyAntiCheat is still on for it.

Check the mod's page for a version that matches your game, and install that.

If the world was hit

A mod that added items or blocks can leave a world that will not load without it. Put the mod back, or restore the backup from before you added it: How to back up and restore your 7 Days to Die world.

More: Your 7 Days to Die mods do not load and How to fix a server that will not start.