Installing and Managing Mods#
Elden Ring’s PC version has an extremely thriving mod scene — from pure graphics tweaks, to massive overhauls that rebuild the combat system, to turning the single landmass into a seamless co-op adventure you can push through with friends. But the prerequisite for all of it is understanding the “online safe zone” logic this game builds around Easy Anti-Cheat (EAC). This chapter explains how to install mods, where they go, when you can get banned, and how to use ModEngine2 to achieve “install and remove freely, without harming your saves”.
1. First, Understand This: EAC and Offline Mode#
Elden Ring’s online multiplayer is guarded by the EAC (Easy Anti-Cheat) anti-cheat system. Any modification to the game’s memory or files, once run online, is judged as cheating and triggers a ban. This is not a theoretical risk but a practical gate the vast majority of mod players run into.
Therefore, the Elden Ring mod ecosystem rests on one basic rule:
| Play style | Loads mods | Online | Risk |
|---|---|---|---|
| Run the game directly | No | Online (co-op/invasions possible) | None |
| Launch via ModEngine2 | Yes | Must be offline | No ban risk |
| Modded and forced online | Yes | Online | Very likely banned |
Knowing which state you’re in is the first thing to do before touching mods. As long as your launch method is clicking “Play” from Steam directly, you are running online under EAC protection; only when you switch to ModEngine2’s launcher do you enter the offline environment where mods work.
Once triggered, a ban is usually account-level and offers almost no appeal, so the red line of “modding online” must never be crossed.
2. Why ModEngine2 Is Recommended Over Direct File Edits#
Mod loading falls into two broad categories, and the difference directly affects your save safety.
| Loading method | Principle | Pros | Cons |
|---|---|---|---|
| Unpack and edit (UXM/Unpacker) | Unpack the game’s encrypted .packbnd files and edit the game’s own files directly | Thorough changes, stable results | Breaks on game updates or file-integrity verification; hard to roll back |
| ModEngine2 loading | Put mods in a separate mods directory and have the game “override-read” from it at launch | Game files untouched; delete the folder to uninstall; easy rollback | Must launch through ModEngine2’s launcher; cannot play directly online |
For most players, ModEngine2 is the safer choice. It keeps mod logic outside the game directory, meaning: if any mod misbehaves, you only need to delete its files from the mods folder — the game itself stays unharmed and your saves are untouched.
3. ModEngine2 Installation Steps#
The following is the most common modding workflow for Elden Ring on PC; each step maps to one verifiable action.
| Step | Action | How to verify |
|---|---|---|
| 1 | Get ModEngine2 from GitHub and extract it to a path without Chinese characters | Confirm modengine2.exe and the mods folder exist |
| 2 | Open modengine2.ini and point the config_app = true and config_app_path fields to the path where the Elden Ring executable eldenring.exe lives |
After saving, the program recognizes the game root directory |
| 3 | Extract the downloaded mods into the mods directory, forming the standard structure mods/<someMod>/... |
One subfolder per mod; don’t scatter files |
| 4 | Run modengine2.exe to launch the game |
A mod-related notice appears at the bottom left of the main menu, and the game is offline |
| 5 | Enter the game, confirm the mods work, then decide whether to keep them | If nothing happens, go back to step 3 and check the directory hierarchy |
One special warning about directory structure, the most common pitfall: ModEngine2 reads the folder one level below mods. If extraction nests an extra layer (e.g. mods/someMod/someMod/), the game won’t read the mod at all — the classic “installed but nothing happens”. When troubleshooting, first check whether each mod is nested exactly one level.
Also, the launcher path must contain no Chinese characters or special symbols. With Chinese characters in the path, ModEngine2 often fails to parse it and the launch fails — a very common problem among players in certain locales.
4. Save Backups: The One Step You Cannot Skip#
Not because mods will necessarily corrupt saves, but because large overhaul mods are generally incompatible with native saves. Mods that completely rework the skill tree, for example, use save fields with a different structure than native saves, and you likely won’t be able to switch back and forth on the same save.
| Backup target | Location (Windows default) | Notes |
|---|---|---|
| Game saves | Files like ER0000.sl2 under %AppData%\EldenRing\<SteamID>\ |
Each save is a standalone file; back up separately per mod before switching mods |
| Game files | Restorable via Steam’s file-integrity verification | With ModEngine2 you generally don’t need to touch the game files |
My advice is one save per mod: create a dedicated save for a given big mod, and when you’re done, copy it to a local backup folder with a clear name before installing the next one. That way you can return to any version at any time instead of nervously sharing a single save.
Another key to avoiding bans: never load a save into online multiplayer while modded. Even if you experienced a heavily modded game offline via ModEngine2, don’t take that “modified” save back into online mode — the save itself may trigger anomalies during file checks.
5. Representative Mod Categories and Where They Fit#
Elden Ring mods fall into broad categories, each with different installation difficulty, compatibility, and risk. Below I only list categories I can confirm exist and whose scope is clear; for individual mods, defer to their own release notes.
| Category | Representative direction | Gameplay impact | Compatibility risk |
|---|---|---|---|
| Graphics and framerate | Unlock framerate caps, widescreen support, lighting tweaks | No gameplay change; improves visuals and feel only | Usually low; mostly pure render layer |
| Seamless co-op | Turn the whole Lands Between into a fully co-traversable co-op map | Full-journey co-op, group map pushing | Conflicts often with other overhaul mods |
| Combat overhauls | Rework poise systems, weapon movesets, enemy AI, and player performance | Gameplay fundamentally changes | Incompatible with most mods; needs exclusivity |
| Content expansion | New weapons, spells, enemy maps, areas | Roughly an expansion pack | Saves incompatible with native |
| Randomizers | Shuffle bosses, items, and drops, or swap enemies/items | Changes the rhythm of exploration | Conflicts with overhaul mods |
Judgment Points for Each Category#
- Seamless co-op: these mods usually require all participants to load the same version to stay in sync; version mismatches cause disconnects or desynced maps. They generally bypass EAC, so all participants must play offline.
- Combat overhauls: these mods change the game’s core logic extremely deeply and basically cannot coexist with other overhaul mods. Before installing one, check its explicitly listed “incompatible mods list”, or you’ll easily hit hard bugs like skills failing or bosses freezing.
- Randomizers: the seed determines the layout of the entire map. If you and a friend want to see the same randomized map, make absolutely sure both of you enter the exact same seed, otherwise the two maps will differ completely.
6. Compatibility Judgment: Ask Three Questions Before Any New Mod#
Many “installed a mod and can’t get into the game” problems can be avoided before you even download. Before installing any new mod, confirm the following three things one by one.
| Check | Question to ask | If it fails |
|---|---|---|
| Game version | Which game version does this mod target? | On mismatch, switch mods or switch game version |
| Dependencies | Does the author require a prerequisite mod first (e.g. some framework/tool)? | Missing prerequisites make the mod dead on arrival |
| Conflicts | Does the author list conflicts with your existing mods? | On conflict, pick one, or look for a compatibility patch |
Once all three check out, move on to the “enable one at a time” verification stage.
7. Conflict Troubleshooting: Elimination One by One#
With many mods installed, crashes, freezes, and missing textures are almost inevitable. The most reliable approach then isn’t guessing — it’s subtracting.
| Step | Action | Purpose |
|---|---|---|
| 1 | Back up the current mods folder and saves |
Preserve a working state |
| 2 | Move all mods out of the mods folder |
Return to a clean baseline |
| 3 | Launch the game and confirm it runs normally | Rule out problems with the game itself |
| 4 | Re-add one mod at a time and test-launch | Isolate the one causing trouble |
| 5 | After finding the conflicting mod, check its compatibility notes or changelog first | Decide whether to switch versions or drop it |
This method is slow, but it reliably pins down the root cause and avoids the waste of “delete all mods and start over”.
8. Red Lines for Safe Modding#
| Scenario | Risk | Practice |
|---|---|---|
| Pure offline single-player | None | Freely load graphics, overhaul, and randomizer mods |
| When you need online | High | Switch back to the mod-free vanilla launch method |
| Saves touched by modded sessions | Very high | Keep that save in the offline environment only; never use it online |
| Multiplayer co-op mods | Version-dependent | Everyone must be on the same version and equally offline |
One-sentence summary: to enjoy the fun of mods, keep both yourself and that save in the offline world; when it’s time to return to online multiplayer, start over with an untouched vanilla save. Keep these two lines clear, and you can switch freely between “mod freely” and “play safely”.