7 Days To Die modlets: install, host, and fix them

Short guide to install modlets on a 7 Days To Die server, keep players in sync, and pick the right hosting plan for modded play.

Jump to: Install modlets on your server · Sync players · Fix common errors · Choose a hosting plan

What are modlets?

Modlets are lightweight ZIPs that adjust XML settings without replacing core game files. They load on first start, are easy to stack together, and can be removed without reinstalling the game. If two modlets touch the same recipe or loot table, conflicts may appear, so install one change at a time and restart between tests.

Modlets vs overhaul packs

• Modlets: XML tweaks that usually work server-only. Great for balance changes, UI tweaks, loot, and small features.

• Overhauls: Big packs (textures, DLLs, quests) that always need client downloads and EAC off. See our guides for Darkness Falls, Undead Legacy, War3zuk, Sorcery, and Age of Oblivion.

Install modlets on your 7D2D server

1. Download the modlet ZIP from a trusted source (official forums, GitHub, Nexus). Check the archive includes a single top-level folder with ModInfo.xml.

2. In the control panel (see how it works), open Files & Mods and upload the ZIP or the extracted folder into /Mods.

3. Restart the server so the modlet loads. Watch the console for Loaded Mod: <name> to confirm it activated.

4. Add one modlet at a time when possible; if something breaks, roll back the last upload only.

Sync players so they can join

• Share the same ZIP with your players. They should extract it to %AppData%/7DaysToDie/Mods (Windows) or ~/.local/share/7DaysToDie/Mods (Linux).

• Keep EAC on for pure XML modlets; turn EAC off only when the author says the mod ships DLLs or assets.

• Ask players to restart the game after adding modlets, then connect to your server. A mismatch usually shows as a disconnect on join.

Verify the modlets loaded

• In the panel console, search for the mod name after restart.

• Check output_log/Player.log for missing dependencies (often Harmony). If Harmony is required, place it as a separate modlet in /Mods first.

• Run a quick craft/loot test in a safe zone before hosting an event night.

Fix common modlet errors

• Red XML errors: Two modlets edit the same recipe or loot table. Disable one, restart, retest.

• Missing assets or pink textures: The modlet includes content that must be on the client. Share the download and remind players to install it locally.

• EAC kicks: Disable EAC only if the author ships DLLs; otherwise leave it on to keep public players happy.

• Bad folder depth: Ensure the path is /Mods/ModName/ModInfo.xml and not /Mods/ModName/AnotherFolder/ModInfo.xml.

Remove or update modlets

1. Stop the server.

2. Delete the modlet folder from /Mods (or replace it with the new version).

3. Start the server and verify the console is clean.

4. Remind players to mirror the change on their side to avoid mismatches.

Where to find safe modlets

• Official 7DTD forums (look for the MODLETS tag).

• Author GitHub releases with clear versioning for the current game build.

• Community staples maintained alongside overhauls; if you upgrade to a full pack later, follow our guides linked above.

Choose the right hosting plan for modlets

• Plan M handles most XML modlets and 10K maps with room for backups. Start here: /server-hosting-plan-M.

• Plan L is better for heavier packs, War3zuk-scale tweaks, or 12K maps: /server-hosting-plan-L.

• Plan XL fits Undead Legacy-sized worlds and 16K experimental maps: /server-hosting-plan-XL.

• Want to compare limits before you switch? Check /compare-hosting-plans for player counts, map sizes, and mod support.