---
title: "How to Disable EAC on a 7 Days to Die Server"
description: "Disable Easy Anti-Cheat on your Winheberg 7 Days to Die server to run mods with compiled code, both server side in serverconfig.xml and client side at game launch."
category: jeux
subcategory: 7-days-to-die
icon: tabler:shield-off
date: 2026-09-08
author: Winheberg
slug: "disable-eac-7-days-to-die"
order: 86
image: /statics/images/docs/en/gaming/7-days-to-die/disable-eac-7-days-to-die.webp
tags: [7 Days to Die, EAC, Mods, Game panel]
keywords: [7 days to die eac, disable eac, easy anti-cheat, eacenabled, serverconfig.xml, dll mods, darkness falls, 7 days to die server]
link_fr: "/docs/7-days-to-die/desactiver-eac-7-days-to-die"
---
## Context
Easy Anti-Cheat, usually shortened to EAC, is the anti cheat bundled with 7 Days to Die. It is enabled by default on dedicated servers and blocks unsigned code from running, which includes any mod shipping a `.dll` file.
In practice, as long as EAC stays on, a mod carrying compiled code will never load, and overhauls such as Darkness Falls or Undead Legacy will not run at all. Modlets made only of XML files are perfectly happy with EAC enabled and need none of this.
This guide covers turning EAC off on the server side of your [Winheberg hosting](https://winheberg.com/en/gaming/7-days-to-die), then the step most players forget, launching the game without EAC on their own machine. It applies to servers managed from [panel.winheberg.com](https://panel.winheberg.com/).
> [!NOTE]
> Disabling EAC is a configuration the game supports, not a workaround. No sanction risk is attached to it.
## Requirements
- An active [7 Days to Die server](https://winheberg.com/en/gaming/7-days-to-die) on the Winheberg game panel
- A mod or overhaul containing at least one `.dll` file, otherwise this change serves no purpose
- A way to reach your players, since they will have to change how they launch the game
> [!WARNING]
> Without EAC, the server has no automatic anti cheat protection left. On a public server, plan a [whitelist](https://winheberg.com/en/docs/enable-whitelist-7-days-to-die) or human moderation before making the switch.
## 1. Check whether you actually need to disable EAC
Open your mod folder in the **Files** tab and look at what it holds.
::MdTable{caption="Do you need to disable EAC" variant="info" striped}
| Mod folder content | EAC |
|---|---|
| Only `.xml` files, usually inside `Config/` | Can stay enabled |
| One or more `.dll` files | Must be disabled |
| Full overhaul such as Darkness Falls or Undead Legacy | Must be disabled |
::
If your mod matches the first row, stop here, nothing needs changing.
## 2. Stop the server
In the **Console** tab, click **Stop** and wait for the shutdown to complete. The configuration file is read at startup, so editing it mid game would have no effect until the next restart.
## 3. Edit serverconfig.xml
Open the **Files** tab, find `serverconfig.xml` at the server root and click it to open the editor.
Look for the line containing `EACEnabled` and change its value to `false`.
```xml
```
Save with the **Save Content** button, then start the server again with **Start**.
> [!TIP]
> The file manager search box does not look inside file contents. Use your browser's find shortcut once the editor is open to jump to the line.
## 4. Launch the game without EAC on the player side
This is where most setups stall. A player whose client starts EAC cannot join a server running with EAC disabled, even with every mod correctly installed. Each player therefore needs to follow these steps.
1. Open Steam and go to the library
2. Click **Play** on 7 Days to Die
3. Choose **Launch game without EAC** in the dialog that appears
If no dialog shows up, a launch option has already been remembered. Right click the game, open **Properties**, then under **General** set **Selected Launch Option** back to **Ask when starting game**. The choice will be offered again on the next launch.
> [!IMPORTANT]
> This choice has to be made at every launch as long as no launch option is remembered. Spell it out for your community, in your Discord welcome message for instance.
## 5. Turn EAC back on
The reverse is identical. Stop the server, set the `EACEnabled` property back to `true` in `serverconfig.xml`, then restart.
```xml
```
Remove any mod containing `.dll` files from the `Mods` folder first, otherwise the server restarts with an anti cheat that blocks them, and you end up with console errors and no obvious cause.
## Troubleshooting
### ❌ Players cannot connect after the switch
- Confirm every player launches the game with the no EAC option
- Check that the server was restarted after `serverconfig.xml` was saved
- Make sure the saved value is `false` and not `False` or wrapped in broken quotes
- Verify players run the same mod versions as the server
### ❌ The serverconfig.xml change seems ignored
- Confirm you edited the file at the server root and not a copy stored elsewhere
- Check that **Save Content** was used before leaving the editor
- Look for a second `EACEnabled` property in the file, only the last occurrence would apply
### ❌ The mod still refuses to load with EAC off
- Confirm the `0_TFP_Harmony` folder is present in `Mods`, it is required for compiled code
- Check the mod structure, `ModInfo.xml` must sit directly inside the mod folder
- Confirm the mod targets the game version installed on the server
For the folder structure side, see our guide [How to Install Mods on a 7 Days to Die Server](https://winheberg.com/en/docs/install-mods-7-days-to-die)
## Best practices
- Enable a whitelist before opening an EAC free server to the public, it is the logical counterpart to the protection you gave up
- Document the no EAC launch procedure in your Discord, it will absorb most of your community support messages
- Turn EAC back on if you ever drop your compiled mods, there is no reason to leave the server unprotected
- Test the connection from your own client before announcing the server to your players
- Keep a copy of `serverconfig.xml` before editing, rolling back then takes seconds
## Need help
If the `EACEnabled` property has no effect after several restarts, or if your players are refused despite a correct setup on both sides, open a ticket with our support team from your [client area](https://billing.winheberg.com), **Technical** department, with the server filled in the **Related Product** field. Our team can review the startup logs with you.
Your server is ready to run compiled mods. 🎮