13 Reference
Update & uninstall
Every part of this install is a file you added, and removing it is deleting that file. No game file is patched, replaced or edited at any point, so there is nothing to repair and no uninstaller to run.
Updating a mod#
Replace the DLL. That is the entire procedure — there is no migration step and nothing to clean up first.
Close the game
Windows will not overwrite a DLL that is currently loaded, and a half-written plugin file is one of the few ways to produce a genuinely confusing failure.
Copy the new DLL over the old one
Into
BepInEx\plugins\, confirming the replace prompt. Nothing else from the archive needs to move.Leave the config file exactly where it is
Settings are matched by name. Anything that still exists keeps your value, anything new appears at its default, and anything removed is ignored. Your tuning carries across.
Deleting the
.cfgis how you reset a mod, not how you update it.
Removing one mod#
Delete its DLL from BepInEx\plugins\. The other mods are unaffected — they share no
state and none of them depends on any other.
| To remove | Delete this | Optionally also |
|---|---|---|
| Ungodly Ravenfield AI | BepInEx\plugins\UngodlyRavenfieldAI.dll |
BepInEx\config\UngodlyRavenfieldAI.cfg |
| Ungodly Ravenfield Enhanced | BepInEx\plugins\UngodlyRavenfieldEnhanced.dll |
BepInEx\config\com.stixsworldhd.ravenfield.ungodlyenhanced.cfg |
| Ungodly Ravenfield Gore | BepInEx\plugins\UngodlyRavenfieldGore.dll |
BepInEx\config\UngodlyRavenfieldGore.cfg |
Leaving the config file behind costs you nothing and means your settings are waiting if you reinstall later. Deleting it is only worth doing if you want a guaranteed fresh start.
Removing everything#
Five items from the game root, and the modding layer is gone entirely.
- Ravenfield\
- BepInEx\you add thisdelete the whole folder
- .doorstop_versionyou add thisdelete
- changelog.txtyou add thisdelete
- doorstop_config.iniyou add thisdelete
- winhttp.dllyou add thisdelete
- MonoBleedingEdge\leave — part of the game
- ravenfield_Data\leave — part of the game
- ravenfield.exeleave — never modified
- steam_appid.txtleave
- UnityCrashHandler64.exeleave
- UnityPlayer.dllleave
Close the game first. After that, launch it normally — it will start as an entirely stock copy, because it always was one with a loader sitting beside it.
Getting a guaranteed-clean copy#
If you would rather not trust a manual delete, or you suspect something else has been changed:
Right-click Ravenfield in your Steam library
Choose Properties.
Installed Files, then Verify integrity of game files
Steam checks every file it shipped against its manifest and re-downloads anything that differs. It takes a minute or two for a game this size.
Reinstalling later#
If you kept your config files, reinstalling is just putting the DLLs back — every setting you tuned
is waiting for you. If you deleted the whole BepInEx folder, start from
the loader install and everything regenerates at defaults.
Either way the process is identical to the first time, and the four folder screenshots on the verification page still apply.
Thanks for playing with them#
All three of these came out of reading Ravenfield's own decompiled source and finding things that were broken, half-finished or never wired up — a skill tier the game implements and never spawns, a prepared defence it builds for every objective and then forgets about, an AI budget that starves the bots exactly when a battle gets interesting. Most of what these mods do is finish work that was already started.
If something here does not behave, the troubleshooting page is the first stop, and the log will usually name the problem outright.