BBLauncher is a Bloodborne-only launcher and mod manager for shadPS4

A launcher for exactly one game

BBLauncher is described as a dedicated shadPS4 launcher focused entirely on Bloodborne, designed to simplify setup, modding, updates and quality-of-life features while staying fully open source. The single-game focus is the defining constraint and the reason the tool exists at all. A general emulator front end has to be flexible about what it launches, and that flexibility is exactly what makes modding awkward, because the modding conventions of a particular game are not something a general launcher can encode. By scoping itself to one title, BBLauncher can make the folder layout, the patch set, the mod directory convention and the save handling specific rather than generic. The project is written in C++, the licence is GPL-3.0, the default branch is master, and the last push was on 2026-10-10, with Release16.12 published the same day for shadPS4 0.16.0 and above, alongside a pre-release build and Release16.10 from 2026-08-09. The repository layout shows a Qt based desktop application with a CMake build, main.cpp at the root, a modules/ directory, a settings/ directory, a static Qt directory in qtstatic/, a WebView2SDK/ directory for the Windows web view, an externals/ directory with the .gitmodules file, and dist/ and .ci/ directories for packaging and pipelines.

Installing on Windows, step by step

The Windows install is short and it depends on shadPS4 as much as on itself. First you install the Visual C++ Redistributable for x64, and the README notes in parentheses that this is required for shadPS4 as well. Then you extract BBLauncher to any folder you like, run it, click Manage Builds and download shadPS4 from inside the app, and finally point the launcher at the shadPS4 install folder, for example CUSA03173, which depends on your game serial. The launcher downloads the emulator for you rather than making you fetch a separate archive, which is a small convenience but also the thing that keeps the two halves version-matched. After the install folder is configured you can skip the graphical interface entirely by launching BBLauncher with an argument.

-n

On macOS the argument is passed through the application's own argument handling.

--args -n

The mod manager and the folder convention

Mods live in a Mods directory inside the BBLauncher folder, and the launcher offers a mod folder icon for quick access.

BBLauncher/Mods

The structure inside that directory is not arbitrary. Each mod must be inside its own folder, and that folder should contain only valid Bloodborne directories, such as dvdroot_ps4, or individual subfolders like sfx, parts or map.

The Mod Manager is described as inspired by Generic Mod Manager from Nexus, and it automatically structures folders and includes error checking. That last point matters more than it sounds: a mod that installs into the wrong directory on a Bloodborne build usually fails silently as a missing asset or a crash, so a check at install time is the difference between a broken mod and a broken game. The feature list also includes downloading mods directly from the launcher, downloading and enabling Bloodborne patches, updating shadPS4 from within the app, remapping controls and changing shadPS4 settings, viewing save information and restoring backups through the interface, and trophy viewing, and trophy completion tracking. One of the fixes listed is for the 60 FPS crash sound glitch, which tells you the launcher is aimed at people running the game with frame rates above the default.

Separate update folders and save backups

The README strongly recommends installing Bloodborne using a separate update folder, and explains why in two sentences that matter for how you set things up. It allows the Mod Manager to apply optimisations more effectively, and if a reinstall is needed, only the update needs to be reinstalled rather than the entire game. That second point is about recovery time rather than aesthetics, and on a large game install it is the difference between a ten minute and an hour long fix when a patch goes wrong. On the save side, the launcher makes automatic save backups at configurable intervals and lets you view save information and restore those backups through the graphical interface, so the safety net is built into the same tool rather than being a separate backup script. Combined with the patch and mod download features, the value proposition is that every operation that touches the game files happens through one program that knows the directory layout.

Version-specific quirks the launcher documents

Two entries in the Common Issues section are worth reading before you file a bug. The first is the procedure entry point error on launch in Windows, and the answer is to re-download both shadPS4 and BBLauncher, because starting from BBLauncher v12.00 external DLLs are no longer required and the issue should no longer occur. That is a good example of a launcher absorbing an emulator packaging problem, and it also means a mixed installation of an old launcher with a new emulator is the likely cause when you see it. The second is the Linux data folder move. As of v10.02 the BBLauncher data folder, previously located next to the AppImage, moved to /usr/share/BBLauncher.

/usr/share/BBLauncher

To keep your existing mods and settings you copy your old files into that directory. The full release history is available on the repository's releases page, and the two most recent named releases both state the shadPS4 version they target, which is the fastest way to check compatibility before you download.

Building it yourself

The project is fully open source and the README invites you to build it, contribute or read the source. The build documentation is split by platform, with a building-windows.md document for Visual Studio Code and a building-docker.md document for the container route, both under the documents/ directory of the repository. The top level confirms the toolchain, with CMakeLists.txt at the root and separate preset files for Windows, Linux and the shared configuration, so the same CMake project drives all three. There is also a .clang-format file, a .ci/ directory for the continuous integration configuration, and a .gitmodules file with the externals/ directory checked out alongside the source. The presence of a static Qt directory and the WebView2SDK directory tells you the application embeds its own Qt build and its own web view runtime rather than relying on system packages, which is what makes a single self-contained folder distribution possible.

Where BBLauncher is the wrong tool

Four limits are worth naming. The first is the single-game scope, and it cuts both ways. If you play only Bloodborne on shadPS4, a launcher that knows the game inside out is exactly right, but if you run half a dozen other shadPS4 titles you now have two launchers, and the general shadPS4 application already does the basics. The second is the dependency chain. BBLauncher assumes shadPS4 is present and version-matched, it assumes the Visual C++ runtime on Windows, and it assumes your game files are in a folder it can find by serial, so it is not a standalone emulator and it cannot help you obtain or dump the game itself. That boundary is worth stating plainly: the launcher works with game files you already have, and how you get them is a separate question with its own legal answer. The third is the maintenance coupling. Release names encode the emulator version, so a launcher update and an emulator update have to move together, and the procedure entry point error in the troubleshooting section is what happens when they do not. The fourth is that the mod manager's convention is specific. Each mod in its own folder containing valid Bloodborne directories is a rule that mods have to follow, so a mod packaged for a different tool will not install correctly, and the automatic folder structuring is a convenience rather than a general mod format support. The alternative to weigh for anyone who only needs one of these features is the upstream shadPS4 launcher, which already handles builds and updates, and adding a separate save backup tool if the automatic interval backups are the part you wanted most, since that is the one feature with no equivalent in the base application.

Editorial conclusion

Adopt BBLauncher if you play Bloodborne through shadPS4 on a PC and you want a single-purpose tool that handles the emulator install, the game patches, mod organisation and save backups without you juggling folders by hand. Do not adopt it if you run other shadPS4 titles, because this launcher is focused entirely on Bloodborne, and do not adopt it if you need a launcher that also serves as a general front end, since that is what the upstream shadPS4 application already is. Verify two things before you rely on it: that your shadPS4 version is 0.16.0 or above, which is what the recent releases are built against, and that you use a separate update folder for the game install, because the README calls that highly recommended and the mod manager applies its optimisations more effectively that way. The practical first step is to install the Visual C++ Redistributable, extract BBLauncher to any folder, and let the Manage Builds screen download shadPS4 before you set the install folder for your game serial.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. rainmakerv3/BB_Launcher on GitHub
4. README
5. Releases