An Investigator’s Field Manual for Lovecraft's Untold Stories

StixUngodlyLUS

BepInEx 5 (x86) · Directors v1.0.0 · Graphics v1.1.0 · by StixsworldHD (StixsmasterHD4k)

Chapter V — Banishing Rites

Verification & Troubleshooting

When something eldritch goes wrong, it is almost always one of the small, mortal things below. Start with the verification checklist — it pinpoints which stage failed — then open the matching case file. The banishing rites for a clean uninstall close the chapter.

The verification checklist

Work top to bottom; each line depends on the ones above it. The Evidence gallery shows every folder exactly as it should look.

From loader to living panels
CheckWherePass looks like
1 · Loader files placedGame rootwinhttp.dll, doorstop_config.ini, .doorstop_version, changelog.txt and the BepInEx folder sit beside lus.exe
2 · Loader aliveBepInEx\After one launch: cache, config, patchers, plugins folders and LogOutput.log exist
3 · Plugins placedBepInEx\plugins\StixUngodlyLUSDirectors.dll (78 KB) and/or StixUngodlyLUSGraphics.dll (87 KB)
4 · Plugins loadedLogOutput.logLines StixUngodlyLUSDirectors v1.0.0 … loaded. (with 26 gated attack states) and StixUngodlyLUSGraphics v1.1.0 … loaded. 15 Harmony patches active.
5 · Configs generatedBepInEx\config\stixsworldhd.lus.ungodlydirectors.cfg and stixsworldhd.lus.ungodlygraphics.cfg exist
6 · Panels answerIn gameF1 opens Directors, F2 opens Graphics

Case files

The BepInEx folder stays empty — no LogOutput.log ever appears

The loader never ran. In order of likelihood:

  1. Wrong architecture. You downloaded win_x64. lus.exe is 32-bit; only win_x86 loads, and the x64 build fails with no error whatsoever. Re-download per Chapter I, Step II.
  2. The nested-folder trap. Confirm winhttp.dll is in the same folder as lus.exe — not one level up, not inside BepInEx_win_x86_…\.
  3. Antivirus ate the proxy. Check quarantine for winhttp.dll; restore and whitelist the game folder.
  4. Proton/Linux without the override. Add the launch option WINEDLLOVERRIDES="winhttp=n,b" %command%.
I grabbed a BepInEx 6 / IL2CPP / Unity.Mono build by accident

Asset names like BepInEx-Unity.Mono-win-x86-6.0.0… are BepInEx 6 pre-releases — a different framework generation. Both Stix plugins target BepInEx 5. Delete what you extracted (the BepInEx folder and the four loose loader files), then install BepInEx_win_x86_5.4.x per Chapter I. Any 5.4.x build is fine.

LogOutput.log exists, but the Stix plugin lines are missing
  1. Confirm the DLLs are really in BepInEx\plugins\ (screenshot in the gallery) and still end in .dll — not .dll.txt from a mis-save, and not still inside the .rar.
  2. Right-click each DLL → Properties: if an Unblock checkbox appears at the bottom (Windows' mark-of-the-web on downloaded files), tick it and Apply.
  3. Check your antivirus quarantine for the DLLs; the published SHA-256 hashes let you prove the files are the genuine ones.
F1 or F2 does nothing in game
  1. First confirm the plugin's loaded line in LogOutput.log (case file above). No log line = the panel cannot exist.
  2. Something on your machine may already own the key (overlays, recorders, macro software, laptop Fn-lock on the function row). Rebind: Toggle Key in the plugin's .cfg — and for Graphics you can also rebind right on the General tab.
  3. Remember which is which: F1 = Directors, F2 = Graphics.
The panel opens but the game is frozen behind it

Working as intended: Pause Game While GUI Open defaults to ON in both plugins. Turn it OFF (each plugin has its own switch) to tune while the world runs — the Graphics README recommends that for dialling in grain, scanlines and fog while walking. Edge case: if you close both panels in the exact same frame and time stays frozen, reopen and close either panel — the clock resumes.

My cursor was invisible / stuck over the F2 panel

That is precisely the bug Graphics v1.1.0 exists to kill: the game permanently hides the hardware cursor and locks the mouse during keyboard play; v1.1.0 forces a real, visible, free pointer every frame the panel is open and hands control back through the game's own input state machine on close. If you see this, you are running v1.0.0 — update from the Reliquary. Configs from v1.0.0 carry over as-is.

Performance dipped after cranking things up

Both READMEs name their heavy knobs honestly:

  • Directors: Pack Size and Max Enemies Per Room (pathfinding scales with crowd size), and extreme zone-size multipliers (longer level builds). The hard caps exist for a reason.
  • Graphics: Light/Shadow Map Scale pushed toward 1 (cost rises with the square), MSAA 8, and Particle Density 300 in crowded fights.

The Graphics Status tab shows live FPS and frame-time while you experiment. Quick rescue: the Potato Rescue preset (map scales up, half textures, capped particles), or walk your changes back — defaults are always vanilla.

The game just updated on Steam — are the mods safe?

Both plugins hook the game's systems at runtime rather than editing files, and discover content (attack behaviours, zone data) by reflection — so ordinary content updates and DLC are covered automatically. If a patch someday rewrites the internals a hook targets, the worst case is a plugin failing to load (check LogOutput.log) or a feature going quiet. Flip Master Enable OFF or remove the DLL to play vanilla meanwhile, and check the Reliquary for an updated build.

I want to prove my downloads are genuine

Compare against the published SHA-256 checksums. On Windows, in the folder with the .rar:

certutil -hashfile StixUngodlyLUSDirectors_v1_0_0.rar SHA256
certutil -hashfile StixUngodlyLUSGraphics_v1_1_0.rar SHA256

On Linux/macOS: sha256sum <file>. The printed hash must match the Reliquary character-for-character.

Banishing rites — clean uninstall

Remove just the mods

  1. Delete BepInEx\plugins\StixUngodlyLUSDirectors.dll and/or BepInEx\plugins\StixUngodlyLUSGraphics.dll.
  2. Optionally delete their configs from BepInEx\config\ — or keep them, and a future reinstall picks up your tuning exactly where you left it.

Remove everything (back to factory vanilla)

  1. Delete the BepInEx folder from the game root.
  2. Delete these four loose files beside lus.exe: winhttp.dll, doorstop_config.ini, .doorstop_version, changelog.txt (that changelog is BepInEx's, not the game's).

Still haunted?

When asking for help anywhere, attach BepInEx\LogOutput.log from a launch that shows the problem, and say which BepInEx zip you installed. Those two facts solve nine cases in ten before anyone has to guess.