Installing BepInEx 6 into Easy Red 2

Everything installs into the folder that contains Easy Red 2.exe. The fastest way to open it:

1. In Steam, right-click Easy Red 2 in your library.
2. Choose Manage → Browse local files. An Explorer window opens directly in the game root.

Typical locations — yours depends on which drive your Steam library lives on:

C:\Program Files (x86)\Steam\steamapps\common\Easy Red 2\
F:\SteamLibrary\steamapps\common\Easy Red 2\        <- the reference install in the screenshots

Before touching anything, a clean unmodded root contains Easy Red 2.exe, GameAssembly.dll, UnityPlayer.dll, baselib.dll, UnityCrashHandler64.exe and the Easy Red 2_Data folder. If you see those, you are in the right place.

1. Open the official Bleeding Edge build server: https://builds.bepinex.dev/projects/bepinex_be
2. On the latest build, find the artifact list and download the one named exactly like this (the trailing number is the build — 785 or newer is what the Ungodly series was built and tested against):

BepInEx-Unity.IL2CPP-win-x64-6.0.0-be.785+af0cba7.zip

Three parts of that name are load-bearing. Check all three before you download:

• Unity.IL2CPP — not Unity.Mono, not NET.Framework, not NET.CoreCLR.
• win-x64 — Easy Red 2 is a 64-bit Windows game; the x86 package will not attach.
• 6.0.0-be.### — the BepInEx 6 Bleeding Edge line. BepInEx 5.x cannot load IL2CPP plugins at all.

Open the downloaded zip and extract its entire contents straight into the game folder from Step 01 — the same level as Easy Red 2.exe, not into any subfolder. If Explorer asks to merge or overwrite, say yes.

After extraction, the game root must contain all five of these new entries sitting next to the game exe:

Easy Red 2\
|- BepInEx\                  <- the loader itself (core\, patchers\, ...)
|- dotnet\                   <- bundled .NET runtime BepInEx 6 IL2CPP uses
|- .doorstop_version          <- version marker for the injector
|- doorstop_config.ini        <- tells the injector what to launch
|- winhttp.dll                <- the injector: Windows loads it with the game
|- changelog.txt              <- BepInEx changelog (harmless, ships in the zip)
|
|- Easy Red 2.exe             <- already there
|- GameAssembly.dll           <- already there
|- UnityPlayer.dll            <- already there
'- Easy Red 2_Data\           <- already there

This is the single most common failure point: if you end up with Easy Red 2\BepInEx-Unity.IL2CPP-win-x64...\BepInEx\ — a folder inside a folder — the game will launch completely vanilla. winhttp.dll must sit in the same directory as Easy Red 2.exe, because Windows only loads it from there.

Compare against the reference install — this is exactly what your root should look like (screenshot taken after the first run in Step 04, so BepInEx already shows a fresh modified date):

1920 × 1080 — click for original

What these files actually do

No action needed — but it helps to know what you just installed. winhttp.dll is UnityDoorstop: the game asks Windows for the system WinHTTP library, Windows finds this one first, and it boots BepInEx before a single frame renders. doorstop_config.ini points it at BepInEx\core\BepInEx.Unity.IL2CPP.dll, and the dotnet\ folder is the self-contained .NET runtime the IL2CPP loader runs on. Delete winhttp.dll and the whole stack silently disarms — which is also the official one-file uninstall.

Launch Easy Red 2 normally through Steam. The first modded launch takes several minutes longer than usual — this is the important part, not a hang:

1. A BepInEx console window may appear alongside the game. Leave it alone.
2. BepInEx reads GameAssembly.dll plus the game's metadata and generates interop assemblies — managed mirrors of every game class, written to BepInEx\interop\. This is what lets plugins call IL2CPP code, and it only happens on this first run (and again after game updates).
3. Wait until the main menu fully loads, then quit the game.

That single run creates the working folders every mod page on this site refers to:

Easy Red 2\BepInEx\
|- cache\           <- interop generation cache
|- config\          <- BepInEx.cfg now exists; every plugin writes its .cfg here
|- core\            <- BepInEx itself (shipped in the zip)
|- interop\         <- the generated game assemblies (the 'bake')
|- patchers\        <- (shipped, empty by default)
|- plugins\         <- THIS is where the Ungodly DLLs go
|- unity-libs\      <- downloaded Unity base libraries for this engine version
|- ErrorLog.log
'- LogOutput.log     <- your first stop for any verification or bug report

1920 × 1080 — click for original

Two quick checks, no tools required:

• BepInEx\LogOutput.log exists and has a fresh timestamp. Open it in Notepad — the first lines identify the BepInEx version and the game. If the file is missing or stale, BepInEx never started: re-check Step 03 (files must sit next to the exe, x64 IL2CPP build, not Mono).

• BepInEx\interop\ is full of DLLs. Assembly-CSharp.dll and friends prove the interop bake completed. BepInEx\plugins\ and BepInEx\config\ now exist and are ready for the mods.