shadPS4 test guide.
An opt-in direct UDP recovery build with the regular one-click BBSC launcher, account setup, server card, and tomb-crash workaround retained.
↓ Download shadPS4 experimental ZIP
Verify with certutil -hashfile "SeamlessHunt-shadPS4-DirectP2P-TestBuild-2026-10-17.zip" SHA256 · All checksums
Reference: Original shadPS4 BBSC setup video ↗ (made for the normal build; use the test CMD named below).
Prepare the shadPS4 test client.
Bring your own game
Only Bloodborne CUSA03173 v01.09 is supported. Don't copy or modify your original game dump.
Extract the whole ZIP to a new folder
Keep emulator, mods, tools and BBSC-Launcher.exe together.
Launch Direct P2P mode
Double-click PLAY BBSC - DIRECT P2P TEST.cmd, not only PLAY BBSC.cmd. It sets the direct recovery flag for the launcher process.
Sign into Seamless Hunt
Use Settings → Accounts and a real account. The included server card does not register an account. Approve the firewall request only if you trust the package.
Launch and test both directions
Both players need test builds. The host and joining player should switch roles and save logs for comparison.
Same server as production.
| shadNet | play.seamlesshunt.com:31313 |
|---|---|
| Web API | http://play.seamlesshunt.com:31315 |
| Game API | http://play.seamlesshunt.com:20443 |
| Fallback | UDP 3478 |
Know what the logs mean.
How do I test the old behavior?
Close the game and restart with PLAY BBSC.cmd. This does not opt in to Direct P2P Recovery unless you set the variable externally.
What indicates direct recovery?
Look for (direct recovery enabled; relay-first) and a later P2P direct recovery: '...' using direct gameplay path. Relay fallback can remain in use if UDP is blocked.
What if Bloodborne crashes near tombstones?
The normal installer includes an automatic workaround that can suppress some tomb_messenger responses and hide bloodstains/death visions. Use DISABLE TOMB CRASH WORKAROUND.cmd to opt out.
Settings appear wrong?
Close BBSC Launcher, run VERIFY SEAMLESS HUNT.cmd, then relaunch the test CMD. Avoid editing settings while the launcher is open.