STIXSWORLD INJECTION CHAIN
v1.8.0 Get the Mod
01 ✓ Before You Begin ▸ Game folder 02 Install UE4SS ▸ dwmapi.dll → UE4SS.dll 03 Install the Overhaul ▸ Mods / mods.txt 04 Configure ▸ config.lua 05 Verify & Fix ▸ main.lua live
02 Install UE4SS

Drop In the Loader

UE4SS is the scripting system that runs Lua mods inside Unreal Engine games. Install it once into Win64 and the game injects it automatically every launch — this is links 01 → 02 of the chain.

NOTE
How the injection actually works

When the game starts it tries to load Windows’ own dwmapi.dll. UE4SS ships a stand-in dwmapi.dll that the game loads instead, which quietly boots UE4SS.dll, which then reads your Mods folder. That hand-off is the “injection chain” — no game files are modified, and removing the loader is as simple as deleting the files.

  1. Stage 01 · AcquireDownload UE4SS from the official repo

    Grab the latest release straight from the source — the RE-UE4SS GitHub Releases page. Avoid random re-uploads.

    Open RE-UE4SS Releases ↗

    On the latest release you'll see two flavours. Pick based on what you want:

    • UE4SS_v{version}.zip — the basic / end-user build. Silent, no console window. This is the one most players want.
    • zDEV-UE4SS_v{version}.zip — the developer build. Same loader, but the UE4SS console window is visible by default, which is genuinely useful the first time so you can watch the overhaul load and confirm it worked.
    PRO MOVE
    First-timer? Grab the zDEV build

    The visible console makes verification trivial — you'll see the overhaul's startup banner print in real time. Once you're confident everything works, you can swap to the basic build, or just leave it; the console does no harm.

  2. Stage 02 · ExtractUnzip everything into Win64

    Open the .zip and extract its contents directly into the game's executable folder — the same Win64 you bookmarked in Chapter 01:

    Extract the zip contents here (next to the .exe)
    ...\HYPERCHARGE Unboxed\Unboxed\Binaries\Win64\

    You're placing the files beside Unboxed-Win64-Shipping.exe, not into a new subfolder of their own. HYPERCHARGE is a standard UE4 title and needs no special game-config patch, so the plain extract is all it takes.

    CAUTION
    Extract contents, not the folder

    If your unzip tool drops a single UE4SS_v... folder into Win64, go one level in and move the files out so dwmapi.dll sits directly next to the .exe. The proxy only works from the executable's own folder.

  3. Stage 03 · Verify the layoutConfirm the files landed correctly

    After extracting, Win64 should now contain the loader files alongside the game. The reference install uses the classic flat layout — everything sitting right in Win64:

    Win64/
├─ Mods/                       UE4SS mods live here (Chapter 03)
│  ├─ BPModLoaderMod/          built-in UE4SS mods
│  ├─ ConsoleEnablerMod/       unlocks the in-game console
│  ├─ ... (other built-in mods)
│  └─ mods.txt                 the enable list
├─ dwmapi.dll                  the proxy — loaded first
├─ UE4SS.dll                   the scripting system
├─ UE4SS-settings.ini          UE4SS configuration
├─ UE4SS.log                   created on first launch
└─ Unboxed-Win64-Shipping.exe  the game
    NOTE
    Two valid layouts — both work

    Newer UE4SS builds default to tucking UE4SS.dll, the settings and the Mods folder into a ue4ss subfolder, leaving only dwmapi.dll in Win64. The older flat layout shown here (and in the screenshots below) is fully supported for backwards compatibility. Whichever your download produces, the rule is the same: put the mod in whatever Mods folder UE4SS is already using.

    Here's exactly what a correct flat install looks like on the reference machine — click either shot to view it full size:

  4. Stage 04 · BootLaunch once and let UE4SS inject

    Start the game normally through Steam. The first launch is doing real work behind the scenes — the proxy fires, UE4SS initialises, and it writes its UE4SS.log into the same folder. Let it reach the main menu, then quit.

    Two signs it worked:

    • A fresh UE4SS.log appears (or updates) in Win64 with a current timestamp and no error lines near the bottom.
    • If you used the zDEV build, a separate console window appears alongside the game showing UE4SS booting.

  5. Stage 05 · Prove itOpen the in-game console

    UE4SS ships with a console-unlocker mod. In-game, press the console key — by default that's ~ / @ or F10. If a console drops down, UE4SS is live and reading mods. That's your green light to install the overhaul.

    PRO MOVE
    Hot-reload is your friend

    Once mods are loaded you can press Ctrl + R to reload all Lua mods without restarting the game. You'll lean on this in Chapter 04 when tuning the overhaul's config.

Loader confirmed?

If the console opens and the log is clean, links 01 and 02 of the chain are done — the game now loads UE4SS on every launch. Time to give it something to run.