Verify & Troubleshoot

Is it actually running?

The fastest proof costs one line. Open scripts\config.lua, set verbose logging on, save, and launch:

config.verbose_logging = true

With that enabled, the overhaul prints a one-line banner to the UE4SS console the instant it loads — naming the version and confirming what it enabled — followed by per-entity confirmation lines as toys spawn. Three independent signals tell you it's live:

1. Signal 01 · The consoleOpen the UE4SS console

   In-game, press the console key provided by the built-in ConsoleEnablerMod — try ~ (tilde), @, or F10. A console window appears; with verbose logging on you'll see the overhaul's banner near the top and live lines as enemies and bots spawn.

   PRO MOVE

   Use the dev build for your first launch

   If you installed zDEV-UE4SS (recommended back in Chapter 02), a console window opens on its own at launch — no key needed. It is the single easiest way to watch the overhaul load in real time. Switch to the slim basic build later once you trust the install.

2. Signal 02 · The log fileRead UE4SS.log

   UE4SS writes a fresh log every launch next to its DLLs in Win64 (you can see UE4SS.log in the Chapter 02/03 screenshots). Open it after the game starts and scan for your mod folder name and a clean, error-free load:

   Open this in any text editor after launchingCOPY

   ...\Unboxed\Binaries\Win64\UE4SS.log

   You're looking for a line that mentions StixsworldHD_UngodlyAIOverhaul being started, and an absence of red [error] lines around it.

3. Signal 03 · The gameplayFeel it in a match

   The truest test. Start any mode and watch: teammates aim and build with intent, and enemies cut you off and flank instead of trailing single-file behind you. If the match feels noticeably sharper than vanilla, the overhaul is doing its job. Bind status_key (Chapter 04) to print a live status line confirming mode, difficulty and how many toys were enhanced.

Common snags — and the fix

Work top to bottom; the issues are ordered roughly by how often they come up.

The game won't launch at all

Almost always one of three things, in order of likelihood:

• Antivirus ate a file. A proxy dwmapi.dll sitting next to a game executable is exactly what some antivirus heuristics flag. See the quarantine fix below — this is the single most common cause.
• Files landed in the wrong folder. The UE4SS files must sit directly beside Unboxed-Win64-Shipping.exe in Win64 (or under ue4ss\ on the new layout). Re-check against the Chapter 02 screenshot.
• Wrong UE4SS build for your system. Grab the current release fresh from the official repo and re-extract.

The game launches, but the overhaul isn't loading

UE4SS is running but your mod isn't being picked up. Walk this checklist:

1. Check 01Folder name and nesting are exact

   The folder must be named exactly StixsworldHD_UngodlyAIOverhaul and sit inside the same Mods folder UE4SS already uses for its built-in mods. A classic mistake is a doubled folder — Mods\StixsworldHD_UngodlyAIOverhaul\StixsworldHD_UngodlyAIOverhaul\ — from extracting the archive into itself. There should be exactly one.

   Mods/
   └─ StixsworldHD_UngodlyAIOverhaul/
      ├─ enabled.txt
      └─ scripts/  ← config.lua + main.lua live here

2. Check 02enabled.txt is present

   The mod ships with an empty enabled.txt already inside it — that file is what flips it on. If it's missing (some extractors skip zero-byte files), just create a new empty text file named exactly enabled.txt in the mod folder.

   CAUTION

   Watch for a hidden .txt.txt extension

   If Windows is hiding file extensions, “enabled.txt” you create by hand can secretly be enabled.txt.txt. Turn on View → File name extensions in Explorer and confirm it ends in a single .txt.

3. Check 03Add it to mods.txt as a backup

   If your UE4SS build uses a master mods.txt and still doesn't load from enabled.txt alone, open Mods\mods.txt and append:

   Add to Mods\mods.txt — keep its existing linesCOPY

   StixsworldHD_UngodlyAIOverhaul : 1

   Make sure the two stock loaders (BPModLoaderMod, BPML_GenericFunctions) are still set to : 1 as well.

4. Check 04Hot-reload or restart

   After any change, restart the game or press Ctrl + R to hot-reload every UE4SS Lua mod. Then re-check the console for the banner.

UE4SS loads but the game renders oddly (or the console is invisible)

UE4SS reads its own settings from UE4SS-settings.ini in Win64 (visible in the Chapter 02 screenshot). If the overlay/console misbehaves or you see graphical glitches tied to the loader, the rendering backend is usually the lever. Open that file and set the graphics API explicitly to match the game (HYPERCHARGE is a DirectX 11 title):

[Overlay]
GraphicsAPI = dx11

Antivirus quarantined the loader

A DLL that hijacks a game's startup is, mechanically, indistinguishable from how some malware behaves — so heuristic antivirus sometimes quarantines dwmapi.dll or UE4SS.dll. They are safe open-source files, but you'll need to tell your antivirus that:

• Restore any quarantined UE4SS file, then
• Add an exclusion for your Win64 folder (or the whole game folder) so it isn't re-flagged on the next launch.

Another mod is conflicting

The overhaul is self-contained and targets shared engine AI classes, so hard conflicts are rare. If something behaves strangely after adding other mods, isolate it: in Mods\mods.txt, set the other mods to : 0 one at a time (leaving the overhaul and the two stock loaders on) and relaunch until the culprit reveals itself. Load order in mods.txt is top-to-bottom; the overhaul doesn't care where it sits.

Turning it off (without uninstalling)

Two clean ways to disable the overhaul while leaving everything in place:

• Per-mod: delete or rename enabled.txt inside the mod folder (e.g. enabled.txt.off), or set its line in mods.txt to : 0.
• In-config: set config.master_enable = false in config.lua — the mod stays installed and loaded but does nothing until you flip it back.