Station 04
Two archives, two DLLs, one folder. Unblock the downloads, drop the files in, launch, and the configuration files write themselves.
Step one of four
Two .rar files. Each holds one DLL and one README, and nothing else — no installer, no
dependencies, no shared runtime to add.
Graphics & UI suite
Raises the 640×360 internal buffer the whole game is drawn into, fixes an interface-scaling bug in the retail build, and opens up the display, quality and post-processing systems the engine keeps closed.
UngodlyGFX_Blasphemous_v1.2.0.rarBepInEx/plugins/UngodlyGFX.dllSHA-256851cea1b7660948e911c946d1534fcc611511fb5b4a66023b6d7368b6ff2b24d
Real-time dynamic difficulty
Puts every enemy statistic in the game within reach, then runs a live director over the top that reads six signals from your play and moves the difficulty while you are in the room.
UngodlyDifficulty_Blasphemous_v1.1.1.rarBepInEx/plugins/UngodlyDifficulty.dllSHA-25675d4d6ae997cb3d11b3f53810e3fbac52ed2df8d5056ce30e5922e7266b50ff6
Both archives are hosted on my own paid Google Drive account. That is a deliberate choice, and it is worth saying what it buys you:
Each tile offers three routes to the same archive: Download from my Drive starts the transfer immediately,
Open in Drive shows you the file in Drive first if you would rather look before you click, and
Copy bundled with this guide pulls the archive out of this website’s own files/ folder without
touching the internet at all.
Unblock both archives before extracting
Right-click each .rar → Properties → tick Unblock → Apply.
A DLL that still carries the internet marker can be refused silently by the loader, and a silent refusal is
the most annoying kind of problem to chase.
Step two of four
Extract both archives anywhere convenient — your Downloads folder is fine. This is what you get:
| File | From | Size | What it is |
|---|---|---|---|
UngodlyGFX.dll | Ungodly GFX 1.2.0 | 160.0 KB | The plugin. This is the only file that has to be installed. |
README.md | Ungodly GFX 1.2.0 | 17.2 KB | Full technical write-up: what it changes and why. |
UngodlyDifficulty.dll | Ungodly Difficulty 1.1.1 | 183.0 KB | The plugin. This is the only file that has to be installed. |
README.md | Ungodly Difficulty 1.1.1 | 30.3 KB | Full technical write-up: the director, the presets, the internals. |
Only the two DLLs get installed. The READMEs are the full technical write-ups — worth reading if you want the reasoning behind any particular setting, and safe to leave where they are.
No configuration file ships in the archives
That is on purpose. Both plugins generate their own configuration file on first launch, complete with every setting’s legal range and a plain-English description of what it does. A file you shipped alongside a DLL can drift out of date with it; a file the DLL writes itself cannot.
Step three of four
One destination, two files, no subfolders.
Where the DLLs go
<game folder>\BepInEx\plugins\Open BepInEx\plugins in the game folder
It was created by the launch you did at the end of station 03 and it is currently empty. If it is not there, BepInEx has not run yet — go back and launch the game once.
Copy UngodlyGFX.dll and UngodlyDifficulty.dll into it
Loose, side by side, directly in plugins. Do not create a folder for each one, do not
rename them, and do not copy the READMEs in with them.
Check the file sizes
Explorer should read 183 KB for UngodlyDifficulty.dll and 160 KB for
UngodlyGFX.dll. A DLL that reads 1 KB is a browser error page that got saved with the
wrong name — download it again.
Blasphemous/
├── Blasphemous.exe
├── winhttp.dll from station 03
├── doorstop_config.ini
└── BepInEx/
├── core/
├── patchers/
├── cache/
├── config/ the .cfg files land here on next launch
│ └── BepInEx.cfg
├── plugins/
│ ├── UngodlyGFX.dll you copy this
│ └── UngodlyDifficulty.dll and this
└── LogOutput.log
■ you copy this in ■ the game writes this itself ■ already there, leave it alone
Step four of four
Start the game. The main menu appears exactly as it always has — no splash, no watermark, no banner. Then press the keys:
| Key | Opens | Palette |
|---|---|---|
| F10 | Ungodly GFX — display, render scale, interface, quality, colour, post-FX, diagnostics | gold |
| F11 | Ungodly GFX on-screen readout | gold |
| F7 | Ungodly Difficulty — overview, director, enemies, combat, bosses, elites, player, per-enemy, diagnostics | crimson |
| F8 | Ungodly Difficulty live readout | crimson |
The mouse pointer appears with either panel and disappears again when you close it. The game pauses while a panel is open. Both panels can be closed with their own hotkey or with the Close button at the bottom.
Now close the game and look in BepInEx\config. Two files you did not create are sitting there:
| File | Size | Contents |
|---|---|---|
com.stixsworldhd.blasphemous.ungodlydifficulty.cfg | 63 KB | Twenty sections. Every enemy, boss, elite, projectile, player and director dial, each with its range and an explanation. |
com.stixsworldhd.blasphemous.ungodlygfx.cfg | 47 KB | 117 settings across eight sections: general, display, render scale, UI scaling, quality, colour, post-processing, overlay. |
BepInEx.cfg | 6 KB | BepInEx’s own settings. Written at station 03, not by either plugin. |
That is the install finished
Both panels open, both configuration files exist. Everything from here is either confirming it (station 05) or deciding what you actually want the game to do (station 06 and station 07).
Proof
If you want certainty rather than inference, open BepInEx\LogOutput.log. The chainloader announces its
count, then each plugin announces itself:
What two loaded plugins look like
[Message: BepInEx] Chainloader started
[Info : BepInEx] 2 plugins to load
[Info : BepInEx] Loading [Ungodly GFX 1.2.0]
[Info : BepInEx] Loading [UNGODLY DIFFICULTY 1.1.1]
[Message: BepInEx] Chainloader ready
2 plugins to load — BepInEx found both DLLs. If it says 0, they are in
the wrong folder. If it says 1, one of them is.Chainloader ready — the load phase completed without an exception taking anything down
with it.A plugin listed but no panel
If the banner is there but F7 or F10 does nothing, the plugin loaded and something else is intercepting the key — usually recording software or an overlay bound to the same function key. Station 08 covers it.
Optional
They are completely independent. Copy in one DLL, leave the other out, and everything works — there is no shared library between them and no load-order requirement in either direction.
If you do run both, they were built to coexist. Every point where two IMGUI plugins normally collide was separated deliberately:
| Point of contact | Ungodly GFX | Ungodly Difficulty |
|---|---|---|
| Plugin GUID | …ungodlygfx | …ungodlydifficulty |
| Panel hotkey | F10 | F7 |
| Readout hotkey | F11 | F8 |
| Window ID | 0x5C1F5 | 0x5D1FF7 |
| Input blocker | UngodlyGFX | UngodlyDifficulty |
| Palette | gold | crimson |
| Config file | …ungodlygfx.cfg | …ungodlydifficulty.cfg |
Pausing is cooperative too: each plugin only ever unfreezes time that it froze itself. If the graphics panel already had the game stopped when you opened the difficulty panel, closing the difficulty panel will not hand control back to a running game.