How to Install Mods and Modlets on a 7 Days to Die Server

How modlets are laid out

A modlet is a self-contained folder that layers changes over the vanilla data instead of editing the game's own files. The Mods folder does not exist by default, so create it at the root of the server install. The structure looks like this:

Mods/
  AuthorName_ModName/
    ModInfo.xml        (required)
    Config/            (XML files that patch the vanilla Data/Config files)
    Resources/         (optional Unity asset bundles)
    UIAtlases/ItemIconAtlas/   (optional item icons)

Without ModInfo.xml the game ignores the folder entirely. Current versions use the flat version 2 format that arrived with Alpha 21:

<?xml version="1.0" encoding="UTF-8" ?>
<xml>
    <Name value="AuthorName_ModName" />
    <DisplayName value="Readable Mod Name" />
    <Version value="1.0.0" />
    <Description value="Short description." />
    <Author value="AuthorName" />
    <Website value="" />
</xml>

Name, DisplayName and Version are required, and Name may only use letters, digits, underscores and hyphens.

Step-by-step: install a modlet on a dedicated server

1. Check version support

   Open the mod's page or readme and confirm it supports your server's exact game version. Major updates commonly break XML patches.

2. Back up first

   Copy your world save and your current Mods folder somewhere safe. Removing a mod that added blocks or items later can corrupt a world.

3. Extract and find ModInfo.xml

   Unzip the download on your computer and locate the folder that directly contains ModInfo.xml. That folder, not the zip or a parent folder, is what you upload.

4. Upload to Mods/

   Place the folder inside Mods/ using SFTP or your host's file manager.

   Copy

   Mods/AuthorName_ModName/ModInfo.xml

5. Restart and read the log

   Restart the server and read the console for mod-loading lines. Running the version command in the server console lists the game version and the loaded mods.

6. Tell players what they need

   Check the mod's documentation for client-side files, and give players the exact mod version.

Hosting with ChicagoServers? The 7 Days to Die server hosting page lists what is included, such as a one-click mod installer, free server backups and SFTP file access. The folder rules above are the same either way.

Server-side vs client-required mods

The wiki states it plainly: XML-based changes are pushed from the server to the client, but item icons and asset bundles are not and must be installed on the client. When a mod page says nothing, assume players need the same files and version as the server.

EasyAntiCheat and mods

EasyAntiCheat blocks unsigned modifications. Hosting guides agree on the practical split: pure XML and asset-only modlets do not require EAC to be disabled, while most mods that ship a DLL or Harmony patch do. Large overhaul mods generally fall in the second group.

To turn EAC off on the server, set this in serverconfig.xml and restart:

<property name="EACEnabled" value="false"/>

• Crossplay and mods are mutually exclusive. Crossplay requires EAC on and an empty Mods folder, and console players cannot join an EAC-off server.
• Players may need to start the game without EAC to join an EAC-off server. If clients are kicked on connect, check that first.
• Code mods run arbitrary code on your server. Install them only from sources you trust.

Load order and conflicts

The documentation does not describe a load-order setting you can control, so the safest approach is to avoid conflicts rather than order them. Two modlets that patch the same XML node can override each other; the usual symptom is a log line saying an XML patch did not apply. Practical rules:

• Run one overhaul mod at a time. They replace large parts of the game data and expect to be the only one.
• Do not delete vanilla entries such as 0_TFP_Harmony from Mods/. Harmony mods depend on it.
• If two folders declare the same Name, the second one is ignored with a log message.
• Remove one mod at a time when debugging. Delete the suspect folder, restart, and see whether the error clears.

Common errors and what they mean

Keeping a modded server stable through game updates

A major game update can break mods on the same day it ships. V3.0 changed enough that overhaul authors had to publish new builds, and Steam keeps older branches available to pin. Do not let a modded server update unattended: read the mod author's compatibility notes first, update the server and every mod together, and keep a backup of both the save and the Mods folder so you can roll back.

Frequently asked questions