THE BBSC WIKI

What is BBSC?

Bloodborne Seamless Co-op changes the game's traditional short summoning encounters into a long-running group session. A host can explore with as many as four guests, for a party of five. Deaths, bosses, lamps, area transitions and visits to the Hunter's Dream are designed not to disband the group.

This is an unofficial guide to the mod, not an official Bloodborne or Sony service. BBSC itself is a community project.

Requirements, platforms & compatibility

There are two Windows client routes into the same BBSC multiplayer experience. They are packaged differently:

• Own Bloodborne game data: CUSA03173, v01.09 as specified by BBSC; no game data is shipped in either BBSC package.
• Windows for both packaged client routes. Server hosting is a separate concern; Windows hosting is bundled, and Linux/self-hosted services can serve the same network roles.
• Every co-op participant must connect to the same shadNet + game-server backend, use mutually compatible BBSC builds, and set the same in-game multiplayer password.
• Each player needs an account on the selected server. An account created on one private server does not automatically exist on another.
• Back up saves before installing or updating experimental builds.

Starting a co-op session

1. Connect to the same server. Everyone must be signed into an account on the same BBSC/shadNet host.
2. Agree on a multiplayer password. Enter the same password in Bloodborne's Network settings to make pairing predictable.
3. Host: use the Hunt Bell. The host initiates the group.
4. Guest: use the Kin Bell. Guests seek the host's session. The mod is designed to allow cross-area matching and bring them to the host.
5. Play together. Up to four guests can join one host, for five hunters total.

The mod replaces some vanilla bell and disconnection lines with clearer co-op text. Other players must have compatible client and server settings; changing a single toggle in only one client may not produce the expected result.

Seamless items & bells

The official feature list names five co-op tools. This table describes their BBSC roles, not vanilla Bloodborne behavior.

The public release descriptions confirm item roles, but do not document precise item IDs, acquisition location, stack limits or every PvP interaction. Those details should only be added after checking the actual mod implementation or developer documentation.

Persistent sessions and travel

World-state & shared progression

World-state sync

Guests should see the host's current world state, including affected doors, bosses and lifts. This lets visitors interact with the host's version of an area while in the group.

Shared progress: on by default, optional

When a guest goes home, the mod can add the host's completed bosses, shortcuts, doors and lamps to that guest's own world. The package describes the sync as additive only: it does not remove guest progress. The mod also states it backs up saves before synchronization.

Guests can disable Shared progress if they prefer to preserve independent world progression. That preference is different from temporary world-state sync while visiting a host.

Loot, echoes and survival rules

• Guest loot: visiting hunters can collect and keep enemy drops and boss rewards; already-collected pickups do not reappear.
• Full Blood Echoes: the guest can receive the host's full rate instead of the usual reduced guest reward.
• No guest HP penalty: removes the normal summoned-guest 30% maximum health reduction.
• Bloodstain on death: an otherwise persistent death still drops a bloodstain and Blood Echoes when the option is enabled.
• Solid NPCs: visitors can see NPCs as solid rather than grey specters.
• Independent characters: guests keep their own leveling, gear, and item inventory.

These behavior switches are enabled by default in both distributed v0.0.1 mod manifests.

Enemy & boss scaling

BBSC includes custom scaling that strengthens enemies as more guests join. The setting is designed to replace the game's built-in boss co-op buff. Its per-guest defaults can be changed in the mod options.

Hostile NPC hunters such as Henryk and Djura have their own Scale NPC hunters toggle, which defaults to off.

Discord Rich Presence

The mod's Discord status option is enabled by default in both uploaded v0.0.1 manifests. Its description says Discord can show BBSC, the current area, boss fights and hunter count.

One player indicates a solo session and multiple hunters indicate a group, if the Rich Presence client exposes that information correctly. The manifest confirms hunter-count reporting, not a specific literal “Playing Solo”/“Playing Co-op” status string. The Discord app must be running and activity visibility enabled.

To disable: turn off Discord status in the mod's options. Discord Rich Presence is distinct from the website's proposed per-account Playing BBSC status; the public aggregate shadNet stats endpoint alone cannot identify which account is online.

Complete configuration reference

These 31 actual entries are taken from the mod.json inside both the uploaded Play and BBPort 0.0.1 archives. Their default values and ranges are preserved. The final column gives the corresponding environment variable for advanced launches.

Servers, P2P & public vs self-hosting

There isn't a separate shadPS4 server and a separate BBPort server. They are two client frontends that can connect to the same shadNet + BBSC game-server pair. The public developer host and a self-hosted host provide equivalent categories of backend service, but each host maintains its own accounts and sessions.

In either case the backend handles login and matching, plus supporting online APIs. Game traffic is peer-to-peer when a direct path works; the server package documents optional UDP NAT relay and an additional game-message relay. Do not assume every optional relay is active on a particular community server.

Community routing: these hostnames resolve to 199.195.193.131 (at the time of this guide). Both shadPS4 and BBPort players can connect here when configured; the original developer's host is a different account realm. Do not confuse the hostname with the backend type.

The mod manifest references 20444 for game-message relaying and the official self-host documentation mentions UDP 3478 for a NAT relay. Those are version-specific optional services; neither is advertised here as verified running on Seamless Hunt.

Install BBSC · choose your platform

Route A: shadPS4 (already bundled)

1. Download BBSC-0.0.1-Play.zip from the official BBSC releases. Check the developer's newer hotfixes before choosing which package is current.
2. Extract the whole archive to one folder. It already includes emulator/shadPS4.exe, BBSC-Launcher.exe, and mods/CUSA03173/bbsc/. Do not overwrite it with a normal shadPS4 release.
3. Provide your legally obtained Bloodborne CUSA03173 v01.09 data; back up any existing game saves. Start PLAY BBSC.cmd. The package is designed to reuse your normal shadPS4 settings and saves; for an earlier portable setup, follow COPY MY SHADPS4 SETTINGS.cmd.
4. Choose your backend. To connect to Seamless Hunt, import/select the correct server card using JOIN-HOST.cmd and verify the game and shadNet URLs point to play.seamlesshunt.com or its current IP. The unmodified archive may still point to the original public host.
5. Create an account at seamlesshunt.com for this server, then use the launcher's existing-account sign-in; website-only registration disables the upstream “Create Account on Server” action here.
6. Everyone uses the same server, compatible mod build and in-game multiplayer password. Host rings Hunt Bell; guests ring Kin Bell.

Route B: BBPort Windows (two downloads)

1. Download and extract the current standalone Supermedo BBPort Windows release. As checked on 14 October 2026, that is Windows 1.7.2. The supplied BBSC test scripts call for 1.6 or later, but compatibility with newer updates must be checked.
2. Start BBPort's Bloodborne.exe, select your own eboot.bin for CUSA03173 v01.09, and confirm that BBPort works normally by itself before adding BBSC. Back up BBPort's user folder (saves/settings).
3. Download the BBSC BBport_latest test release or the matching BBSC-0.0.1-BBport.zip from official releases. Check its included README and files before applying it; a hotfix for shadPS4 is not automatically a BBPort patch.
4. For the supplied BBSC 0.0.1 BBPort archive: extract the BBSC helper to its own folder, not into BBPort. Run PLAY BBPORT + BBSC.cmd. Its file picker locates BBPort's Bloodborne.exe and your game eboot.bin, then starts BBPort using bbsc/bbsc-launch.exe + the mod. It does not replace BBPort's executable.
5. Use the server card for play.seamlesshunt.com:31313. The launcher generates user/host_overrides.custom.json in your BBPort installation, routing the game API and summoning to the same host. Do not casually overwrite the original host_overrides.json.
6. Create an account at seamlesshunt.com and use existing-account login in the Seamless Hunt–configured helper. The original BBSC helper's direct-register option is unsuitable for this server (private registration is enabled).
7. Launch PLAY BBPORT + BBSC.cmd, choose online at the game's title screen, then host/join with the Hunt/Kin Bells.

No server package needed for ordinary players. BBSC-0.0.1-Server.zip is for people who want to host a backend, not for connecting to either an existing public host or Seamless Hunt. Keep private registration keys and login passwords private.

Updates, releases & replacing files safely

These are three separate release streams. Their version numbers and files must not be conflated:

Updating shadPS4 + BBSC

Back up the working BBSC Play folder and saves. Follow the specific BBSC Play/hotfix release instructions, keeping the bundled modified emulator and mod compatible. Nexus Mods explicitly says its download contains only mod files and should be used for updates to an existing BBSC install. Do not install it as a complete Play package, and do not drop a generic shadPS4 build over BBSC's custom emulator.

Updating BBPort + BBSC

1. Back up BBPort's user folder, current host_overrides.custom.json and BBSC helper folder (including any account/server configuration).
2. Update BBPort itself using Supermedo's released updater or the official ZIP, following its instructions; confirm the normal game still launches and your saves are present.
3. Get the corresponding BBSC-for-BBPort test release. Compare its instructions and files with your current BBSC helper, and replace only files the BBSC developer designates for this platform. The older ZIP's integration launcher remains in its own folder.
4. Confirm the wrapper still locates Bloodborne.exe, bin/bb-probe.exe and your eboot.bin; verify it targets the correct server and that user/host_overrides.custom.json is regenerated correctly.
5. Test online authentication and in-game BBSC summoning. If a new upstream BBPort layout breaks the wrapper, revert to the last verified working combination rather than assuming every “latest” is compatible.

Known issues & troubleshooting

Sources, checks & remaining uncertainty

Reviewed 14 October 2026. This wiki documents BBSC 0.0.1, including the official hotfix/test release names known on that date. The supplied package manifests describe gameplay settings; the independently maintained BBPort Windows release has its own version number.

• Official BBSC source repository and GitHub release list: client packaging, shadPS4-bundled Play archive, self-host and BBPort distributions, release/hotfix names.
• BBSC Nexus description and Nexus files tab: official gameplay claims and mod-only update warning.
• Supermedo BBPort Windows releases: current 1.7.2 version, independent native-port online systems, Windows release changes.
• User-supplied archives: BBSC-0.0.1-Play.zip (bundled emulator/shadPS4.exe, launcher, HOW-TO-PLAY.txt), BBSC-0.0.1-BBport.zip (HOW-TO-PLAY.txt, tools/play-bbport.ps1, bbsc-launch.exe), BBSC-0.0.1-Server.zip (self-host README and network notes), and mod.json from both client archives (31 settings and default scaling).
• Seamless Hunt deployment: play.seamlesshunt.com and website-only registration are this community's server-specific setup; not the upstream package defaults.

Not independently confirmed: that the new BBSC BBport_latest binary works with every Supermedo v1.7.2 configuration; literal Discord Rich Presence wording; some undocumented item internals and exact in-game damage/stagger formulas. The calculator represents manifest defaults, not measured enemy stats. Server-side relay availability varies by host.