7 Days to Die uses a folder-based mod system. Mods (called “modlets”) go in a Mods folder in your server’s root directory. Each mod is a folder containing a ModInfo.xml file and the mod’s content files.

Before You Start

EAC must be disabled for mods to work. Edit serverconfig.xml via File Manager or SFTP and set EACEnabled to false, then restart the server.

Step 1: Create the Mods Folder

If a Mods folder doesn’t already exist in your server’s root directory, create one:

Open the File Manager in your Game Control Panel
Navigate to the root directory
Click Create Directory and name it Mods

Step 2: Download the Mod

Download mods from trusted sources:

7daystodiemods.com
Nexus Mods
The mod’s official GitHub or forum page

Most mods download as a .zip file. Extract it on your computer first.

Step 3: Find the ModInfo.xml

After extracting, look for the folder that contains ModInfo.xml. This is the mod’s root folder. The structure should look something like this:

MyModName/
├── ModInfo.xml
├── Config/
│   └── (XML patch files)
├── Resources/
│   └── (optional asset bundles)
└── UIAtlases/
    └── (optional custom icons)

The folder containing ModInfo.xml is what you upload. Not the zip file, not a parent folder - the folder with ModInfo.xml directly inside it.

Step 4: Upload to the Server

Upload the mod folder into your server’s Mods directory:

Using File Manager: Navigate to Mods/, then upload the mod folder. For single files, use the upload button. For folders with subfolders, use SFTP instead.

Using SFTP: Connect to your server via SFTP and drag the mod folder into the Mods directory.

The final path should look like:

Mods/
├── MyModName/
│   ├── ModInfo.xml
│   └── Config/
├── AnotherMod/
│   ├── ModInfo.xml
│   └── Config/

Step 5: Restart the Server

Restart your server through the Game Control Panel. Check the server console output for mod loading messages. Successfully loaded mods will appear in the console log.

How XML Mods Sync to Clients

For modlets that only modify XML files (which is most of them), the server automatically pushes the changes to connecting clients. Players don’t need to install anything - they just connect and the mod’s XML changes are applied.

However, mods with custom assets (icons, models, textures, sounds) need to be installed on each player’s client as well. The asset files don’t sync automatically. The mod’s documentation will specify whether client installation is required.

Installing Multiple Mods

You can install multiple modlets at the same time. Each one goes in its own folder inside Mods/. Most modlets are compatible with each other since they use XML patching rather than file replacement.

Overhaul mods are the exception. Only install one overhaul mod at a time (Darkness Falls, Age of Oblivion, Rebirth, etc.). They modify the same core systems and will conflict. For overhaul mod installation, see the specific guide for the mod you’re using:

Installing Darkness Falls

Troubleshooting

Mod not loading

Verify ModInfo.xml exists directly inside the mod folder (not nested in a subfolder)
Check the server console for error messages
Verify EAC is disabled
Make sure the mod is compatible with your game version (V2.5)

Server won’t start after adding a mod

Remove the mod folder and restart to confirm it’s the cause
Check for XML syntax errors in the mod’s config files
Verify you didn’t accidentally modify any vanilla files outside the Mods folder

Players can’t connect after adding mods

If console players can’t connect, that’s expected - mods require EAC off, which disables crossplay
If PC players can’t connect, they may need to disable EAC on their client as well (launch without anti-cheat)
If the mod requires client-side installation, players need to install the mod on their PC too