In piracy and homebrew circles, ignoring the NFO file is the #1 cause of failed installations, bricked saves, or console errors. For this specific release, the NFO likely contains:
A common line in such NFOs reads: “DO NOT install over a legit copy. Backup your save first. Mods will disable trophies.”
Assuming a user has a jailbroken PS4 on firmware 9.00 or 11.00 (with exploit), the steps would look like: bloodbornev109incldlcandmodsreadnfops4 install
The entire process assumes the user has already disabled syscalls to avoid telemetry and is comfortable with risk.
This is not an official Sony package. Instead, it is a pkg file (PlayStation package) designed for jailbroken PS4 consoles. Official PS4s will reject it outright. In piracy and homebrew circles, ignoring the NFO
The “v1.09” part is critical. Retail Bloodborne on disc runs at v1.00. Patch 1.09 added quality-of-life fixes and DLC support. However, many mods require a specific base patch to function. Version 1.09 became the golden baseline for the modding community because it is stable and widely dumped.
The phrase “and mods” is where things get interesting. Standard Bloodborne mods include: A common line in such NFOs reads: “DO
Because Bloodborne never received an official PC release, PS4 jailbreak modding is the only way to play these custom versions outside of emulation (which remains immature for this title).
Installing in the wrong order will cause crashes, missing items, or the DLC not triggering.
Correct Procedure (via Debug Settings or Package Installer):