Almost always the folder is one level too deep, or the server was not restarted. Each mod must be its own folder directly inside Mods, with ModInfo.xml directly inside that folder. Then restart: mods are read only when the server starts.
1. The folder layout
- In the panel, open Files, then
Mods. - Open each mod folder.
ModInfo.xmlmust be right there.
| Layout | Works |
|---|---|
Mods/BetterLoot/ModInfo.xml | yes |
Mods/BetterLoot/BetterLoot/ModInfo.xml | no, one level too deep |
Mods/ModInfo.xml | no, the mod needs its own folder |
Mods/BetterLoot.zip | no, unzip it first |
Fix a deep folder with Move folder: move the inner folder into Mods and delete the empty outer one.
2. Restart
Mods are read once, at start. Restart the server after every change.
3. Read the game's log
The game writes the mods it loads to its log file, not to the Console. After a restart, open Files, then logs, then latest.log. Look for your mod's name, and for errors or warnings just after it. A mod with an error in its XML is named there.
4. EasyAntiCheat
A mod that ships a .dll needs EasyAntiCheat off on Settings, Game Settings. With it on, the game skips the 0_TFP_Harmony loader those mods run on, and players cannot join a server running one.
5. The game version
A mod made for an older game version can stop working after an update. Check the mod's page for a version that matches the game, and update it on the server and on your players' games.
6. A mod that needs another mod
Some mods need another mod installed first. The mod's page says so.
If the server will not start at all after a mod, see Your 7 Days to Die server will not start after adding a mod. The full guide: How to add mods to your 7 Days to Die server.





