VGKAMI
Advertise Get listed

Game Guides

How to Install Mods on an Enshrouded Dedicated Server

October 26, 2026 10 min read

Enshrouded has no official mod-support system. To run community mods on a dedicated server, use the unofficial Enshrouded Mod Loader (EML): place its current dbghelp.dll beside enshrouded_server.exe, create a mods folder, and put each compatible mod there with mod.json at the package’s top level. Windows servers use the proxy DLL directly; Linux, Wine, and Proton require a WINEDLLOVERRIDES launch setting. Back up the complete save before changing files, add mods one at a time, and verify every mod against your Enshrouded build.

Is modding officially supported in Enshrouded?

No. Keen Games’ FAQ says, “at this stage, we cannot make promises that the game will be moddable, but it is something we would love to implement in the future.” EML is community software rather than a Keen Games feature, so an update can break the loader or an individual mod without an official compatibility guarantee.

EML’s documentation describes it as a Lua-based loader and framework. Its current scope is asset modifications loaded before the game starts; runtime modifications are planned for the future. Treat every mod as an independent dependency: a loader release that supports a game version does not automatically make every mod compatible with it.

What should I prepare before installing server mods?

Complete the clean dedicated-server setup first. The following items prevent most avoidable failures.

  • Official server files: In Steam, open the Tools section, install the Enshrouded Dedicated Server tool, browse its installed files, and run the server executable once. Keen Games says purchasing and unlocking Enshrouded unlocks this tool.
  • Initial configuration: The first run creates enshrouded_server.json. The official example uses ./savegame for saveDirectory, ./logs for logDirectory, query port 15637, slotCount 16, chat settings, and a difficulty preset. Your existing settings may differ; preserve them when adding EML.
  • A stopped server and a backup: Stop the process and copy the entire savegame directory to a separate location before installing a loader or mod. Do not rely on a partial character or world copy.
  • Version information: Record the installed Enshrouded build, then read the EML release notes and every mod page. A mod must explicitly support EML and your current game build.
  • File access: You need permission to write beside the server executable on a self-hosted machine. On a managed host, you need a panel feature that actually starts EML, not merely a generic file uploader.

How do I install EML on a Windows self-hosted server?

These steps use the proxy-DLL method recommended by the EML maintainer. Perform them while the server is stopped.

  1. Install and initialize the dedicated server. Use Steam’s Tools library to install the official server, browse its files, and launch enshrouded_server.exe once. Wait for enshrouded_server.json and the configured save and log directories to appear, then shut the server down cleanly.
  2. Back up the world. Copy the complete directory named by saveDirectory (normally ./savegame) outside the server folder. Keep this copy until the modded server has started and been tested.
  3. Download the current EML release. The release identified in the current documentation is EML v0.2.0, released on 2026-10-16, with a note for Enshrouded 1.0 compatibility. Download the release archive from the maintainer’s release page and check for a newer release before you proceed.
  4. Extract the proxy DLL. Open the archive and copy dbghelp.dll into the server root, the same directory that contains enshrouded_server.exe. Do not put the DLL inside mods, the save directory, or a nested extraction folder.
  5. Create the mod directory. In that same server root, create a folder named exactly mods if it is not already present. Use the spelling and capitalization expected by EML.
  6. Install one compatible mod. Follow the mod author’s dependency instructions. Extract the mod into its own folder, or place its archive in mods, with mod.json directly at the top level of that folder or archive. If extraction produces an extra wrapper directory, move the contents so EML can read mod.json without descending through another folder.
  7. Start the server once. EML should create eml.json after a successful proxy load. Allow the process to finish startup, then inspect the server and EML logs for load errors before inviting players.
  8. Add further mods incrementally. Stop the server, add exactly one additional mod, restart, and check the logs again. This gives you a precise rollback point if the next addition prevents startup.

What should the Windows server folder look like?

The important relationship is that the DLL and mods directory sit beside the executable, while each mod exposes its manifest at the package’s top level.

EnshroudedServer/
├─ enshrouded_server.exe
├─ dbghelp.dll
├─ ens(hrouded_server.json)
├─ eml.json
├─ mods/
│  ├─ ExampleMod/
│  │  └─ mod.json
│  └─ AnotherMod.zip
├─ savegame/
└─ logs/

The names of individual mod folders and archives vary. The structural checks that matter are dbghelp.dll beside the executable and a readable mod.json at each mod’s top level.

How do I run EML on Linux, Wine, or Proton?

Wine can choose its built-in dbghelp instead of the EML DLL unless you override the DLL search order. Put the EML DLL beside the Windows server executable, create the same mods layout, and launch the process with this exact setting:

WINEDLLOVERRIDES="dbghelp=native,builtin" wine path/to/enshrouded_server.exe

The value means Wine should prefer the native DLL in the server directory and fall back to its built-in implementation only when appropriate. Start the command from the directory containing the executable, or use a path that resolves to that file. If the server starts but EML does nothing, verify both the working directory and the spelling of WINEDLLOVERRIDES before changing mod files.

How does the Proton command differ?

Use the equivalent Proton invocation for the same executable, for example:

WINEDLLOVERRIDES="dbghelp=native,builtin" proton run path/to/enshrouded_server.exe

On a Steam client, place the same environment variable in the game’s launch options using the syntax required by your Steam installation. Proton prefixes and paths differ between systems, but the override value does not. Confirm that the prefix being used is the one that contains the server files.

Can a managed hosting panel install EML?

Sometimes, but the workflow belongs to the provider rather than Keen Games. A panel must both expose the EML files and launch the server with the required proxy behavior. A toggle labelled “mod loader” is not evidence of official support.

BisectHosting’s documented Enshrouded workflow is:

  1. Stop the server.
  2. Enable the provider’s Enshrouded Mod Loader setting.
  3. Boot once so the loader files and directories are generated.
  4. Stop the server again.
  5. Open the panel’s file manager and enter the mods directory.
  6. Upload the mod archive, unarchive it, and check that mod.json is at the expected top level.
  7. Restart and read the server log.

Other panels may hide dbghelp.dll, use a custom startup command, or require a support request. Ask the provider where its EML files are installed, which Enshrouded build it supports, and how to restore clean server files before uploading a mod.

Do players need to install the same mods?

Not always. The server is authoritative for many data changes, so server-only installation can be enough for changes such as stack sizes, chest slots, crafting or loot values, and stamina. Players can connect without copying those data changes locally when the mod is designed for server-side use.

A mod that changes a player’s local display, interface, or client behavior may require every player to install the loader and the same mod. Read the individual mod’s instructions rather than assuming that all EML packages are server-only.

What is the client installation pattern?

For a client that requires EML, the documented pattern is to copy dbghelp.dll into the Enshrouded game folder and create a mods folder there. The mod’s path must expose mod.json at the top level, just as on the server. Players should close the game before copying files and remove or update the client package when its author marks it incompatible.

Which EML and mod versions work together?

Compatibility is build-specific and can change after a game update. EML v0.2.0 is dated 2026-10-16 and its release notes include an Enshrouded 1.0 compatibility note. That statement covers the loader release; it does not certify every third-party mod.

Item Documented value How to use the information
Official Enshrouded mod support Not available EML is an unofficial community solution and can be affected by game updates.
Current EML release identified v0.2.0, released 2026-10-16 Check the maintainer’s release page for a newer build before installation.
Game-version note Enshrouded 1.0 compatibility listed Still verify each mod’s own support statement.
Supported modification scope Asset changes before game start Do not expect runtime code changes from the current loader scope.

After any Enshrouded patch, pause mod loading until you have checked the EML release notes and each mod page. If only the loader has an update, do not infer that a mod with no recent statement is safe.

Why did my Enshrouded server stop starting after I added a mod?

Most failures are isolated by removing the newest addition and then correcting the package or launch environment. Keep the clean backup untouched while diagnosing.

The server hangs immediately after a new mod

  • Stop the process and remove the newest mod from mods.
  • Inspect the EML and server logs for a malformed or unreadable mod.json, a duplicate mod ID, or a Lua error. These conditions can stop startup.
  • Check that the manifest is at the folder or archive top level, not inside an additional extraction directory.
  • Restore the mod only after confirming its dependencies and the current Enshrouded build.

EML appears inactive on Windows

Confirm that dbghelp.dll is named exactly as shown and sits beside enshrouded_server.exe. Check that the server is launching from the intended installation directory and that eml.json appears after a successful start. A DLL copied into mods cannot act as the proxy.

EML appears inactive on Linux or Proton

Re-run the server with WINEDLLOVERRIDES="dbghelp=native,builtin". Verify that the command starts in, or points directly to, the directory containing the EML DLL and executable. Without the override, Wine may load its built-in dbghelp and leave EML inactive.

The server broke after an Enshrouded update

Record the new game build, then check for an EML release and updated mod pages. The v0.2.0 Enshrouded 1.0 note is not a promise for later builds or for every package. Re-enable mods one at a time after the loader and each dependency are confirmed.

The panel starts the server but no mods load

Ask the host whether its toggle adds the proxy DLL and whether the startup command is equivalent to the documented EML launch. Check the panel’s actual file tree for mods and a top-level mod.json; a successful file upload alone does not prove that EML is being loaded.

How do I remove EML or roll back safely?

  1. Stop the server and preserve the complete savegame directory before deleting anything.
  2. Remove the newly added mod first and test a clean restart.
  3. For a full rollback, restore the clean server files or the backup you made before EML installation.
  4. Delete dbghelp.dll and the mods directory only after the save is safe and you no longer need the loader.
  5. Keep enshrouded_server.json if you want to retain your port, slot, chat, and difficulty settings; restore it from backup if it was changed accidentally.

A separate patcher route can rewrite enshrouded_server.kfc. It is not the EML method and should not be combined with these DLL instructions. Steam updates or file validation can undo that kind of patch, so restore the original files before switching approaches.

Which installation approach fits my server?

Approach Loader setup Primary control Main risk to plan for
Windows self-hosted dbghelp.dll beside the executable and a local mods directory Direct access to files, logs, and backups You must maintain compatibility and recover the files yourself.
Linux, Wine, or Proton self-hosted Same files plus WINEDLLOVERRIDES="dbghelp=native,builtin" Full control of the launch command and prefix A missing override can silently bypass EML.
Managed hosting panel Provider-specific EML toggle and file workflow Panel controls instead of shell access The provider may hide the DLL or use a different startup implementation.
Client-required mod Players also place the DLL and mod layout in their game folders Each player’s local installation Everyone must use the versions required by the mod author.

For any approach, the safest operating pattern is the same: preserve the world, verify the loader and mod versions, make one change, restart, and read the logs before making the next change.

Frequently Asked Questions

How many EML mods can an Enshrouded server run at once?

There is no authoritative published mod-count limit. The practical limit is determined by compatible dependencies and whether every package loads cleanly, so add packages incrementally instead of assuming a fixed maximum.

How can I report a broken Enshrouded mod effectively?

Capture the Enshrouded build, EML version, mod versions, launch method, and the relevant startup log lines. Reproduce the failure with the newest mod removed; that distinguishes a package problem from a loader or Wine configuration problem.

Does EML provide a performance or compatibility guarantee?

No authoritative adoption, performance, or compatibility-rate statistic is published. EML is actively developing community software, and its documented scope and supported game builds can change.

Can current EML mods change Enshrouded while the server is running?

The documented loader scope covers asset modifications before game start. Runtime modifications are described as planned, so a package requiring live code changes is outside the current stated scope.

What should I verify when a mod archive looks correctly uploaded but is ignored?

Open the archive or extracted folder and check that mod.json is directly at its top level. If the file is one directory deeper because the archive contains a wrapper folder, EML may not recognize the package.