Bloodborne mods on PC
Nothing here edits the game. Replacement files, param tables, patches and plugins, layered at run time.
You never edit Bloodborne's files. bbhost layers mods from a mods folder, a params folder, byte patches and plugins — a randomizer, boss rush, mutators and the developers' debug menu already ship with it; the ports load loose files and XML patches.
Quick answer: you never edit Bloodborne's files. bbhost layers everything at run time from a mods folder, a params folder, byte patches and plugins — its official plugin set already includes a randomizer, a boss rush, gameplay mutators and the developers' own debug menu. bbport and the Windows port load loose-file mod folders with enable switches and load order, plus shadPS4-format XML patch files.
Official Bloodborne screenshot, PlayStation.
The one rule every project follows
No project here modifies your game files. Replacement files are served from an overlay folder before the game's own copy is opened, params are applied when a table loads, and byte patches are applied in memory. That matters for two practical reasons: you can switch any of it off without reinstalling the game, and if something misbehaves you can isolate it in one move.
bbhost: four ways in
bbhost's own documentation splits modding into four mechanisms, ordered by how much they ask of you.
| What you want to change | Where it goes | Needs code |
|---|---|---|
| Replacement files — menus, text, textures, layouts | the mods folder | No |
| Numbers — weapons, enemies, item drops, shops | <mods>/params/*.toml | No |
| Small code changes | patches/*.toml | No |
| Anything else | a plugin | Yes |
Replacement files. <mods>/dvdroot_ps4/<path> replaces the game's own dvdroot_ps4/<path>. Files are matched by the path the game asks for, so a replacement keeps the original name and container format — a compressed .dcx stays compressed. The log lists what it served from the overlay, so you can confirm a mod is actually live.
Params. The game's numbers live in 62 tables — weapons, armour, enemies, attacks, item lots, shops, effects, the lock-on camera and more. bbhost reads the field definitions the game itself ships, so the fields are named the way FromSoftware named them, not by guessed offsets:
# <mods>/params/EquipParamWeapon.toml - the Saw Cleaver is row 1000000
row.1000000.correctStrength = 250
row.1000000.weight = 0.5
# <mods>/params/LockCamParam.toml - every row
row.all.camDistTarget = 5.5
row.all.chrLockRangeMaxRadius = 30Where no field name fits, a raw type and byte offset works: f32, i32, u32, i16, u16, i8, u8. To see a row before changing it, dump it — BBHOST_PARAM_DUMP="EquipParamWeapon:1000000" ./bbhost prints every field with its value, type and the game's own description. Overrides apply every time a table loads, including reloads, and a table whose rows do not match its definition is refused with a log line rather than written wrongly.
Byte patches as data. patches/*.toml applies small code changes without a build step.
Plugins. Anything beyond that is a native plugin, which is how the shipped set is built.
What ships with bbhost
The official plugins are the strongest argument for this route if you have already finished the game once:
- Randomizer — items, shops and enemies.
- Boss rush — fights without the walk.
- Gameplay mutators — a set of switches for changing how a run plays.
- The developers' own debug menu — a font of its own, English text, Japanese in its
settings. Turn it on in the setup window's Plugins tab; in game, the backtick key opens it. The release notes are clear on one point: trying it online with friends is fine, cheating against other players gets an account banned.
Sessions that run gameplay plugins announce their rules to the online server, which keeps their messages, bloodstains, signs and statistics separate from vanilla players — a player can still be summoned into a randomizer host's world and play by that host's rules. More on that in multiplayer.
bbport and the Windows port: loose files and XML patches
bbport accepts separate loose-file mod folders — with a dvdroot_ps4/ directory inside, an extra wrapper folder, or the game's own folders such as chr/ directly; file-name case does not matter. Each folder has an enable switch and a place in the load order, and a sibling CUSA03173-mods/ overlay works too. The original game is preserved and later mods override conflicting files.
The Windows port stages mods and automatically compiles patches from run.bat, and its launcher puts community patches — Skip Intro, a performance patch and others — behind a checkbox list.
DLC follows the ports' own convention rather than a mod loader: add-on dumps go into user/addcont/<title id>/<entitlement label>/, which is how The Old Hunters gets reported to the game as installed.
The community patches these projects are built on
The frame-rate and camera work everybody uses is patch work, not project work, and all three ports credit it plainly: Kyo's 60 FPS++ timing list is built into the ports' frame-rate code, Lance McDonald's debug camera and illusion's Skip Intro ship as patch files, and auser1337, emoose and others contributed to the patch sets. If you want to know what is technically possible on this game, that patch file is a more interesting read than any list of mods.
Official Bloodborne screenshot, PlayStation.
The one caveat
Two of the four projects state that they do not support the game once patches, cheats or mods are loaded. Keep a clean profile — patches off, mods folder empty — for anything you intend to report, and switch plugins off before you diagnose a crash. Troubleshooting is written to be read that way round.
This page covers modding as documented by the four PC projects this site tracks. The wider community's mod scene for Bloodborne is larger than that, and it moves faster than any page can; where a project's own repository documents a mechanism, it is described here.
