Bloodborne PC co-op connection checks: VPN reachability, party roles and the host address
ItsOOGWAY · PC guides & recorded tests
Bloodborne PC co-op connection checks: VPN reachability, party roles and the host address
Bloodborne PC co-op not connecting? Check the Radmin network, host and guest roles, party discovery, the correct host VPN address, and the game party password using our working two-PC setup.
The key checkpoint: VPN membership and joining a game party are separate checks. Compare versions, launch the host first and use the current host VPN address with the matching game-party password.
Before you start
- Use the recorded versions and the supported inputs listed in the original notes below.
- Compare the last successful checkpoint before choosing a fix.
- Keep original files, relevant logs and a known working setup when testing changes.
Resources from this video
Links, downloads & documentation
Every original URL from the video description is collected here, including recorded releases, setup discussions and related videos. Use the version-specific notes when following a recorded build.
Watch the complete video
Open this video on YouTube ↗. Screenshots below link to their exact recorded moments.
Walkthrough 01
Start with both games launching normally
This guide assumes Bloodborne already launches on both PCs. If you still need the game extraction and installation steps, use the complete setup video linked in the resources section. Here, we're concentrating on joining the party.
Walkthrough 02
Verify that both PCs can reach the VPN
Start with the network. Both people need to be inside the same Radmin network, not just have the app installed. One person creates the network, and the other joins using its name and password. Check the member list on both sides before changing the game settings. If the other computer isn't reachable, sort that out first. Radmin has a Ping option when you right-click the other computer. It's a useful network check, although a successful ping doesn't prove that every part of the game's connection is allowed.
Walkthrough 03
Compare the actual port versions
Next, compare the port version. Both launchers in our recording are zero point seven point five. If only one person has updated, bring both PCs onto the same release before trying again. The same principle applies to the supported one point zero nine game files and gameplay modifications. If Bloodborne gives you a version-mismatch message, read what it says differs. It can be the port build, game files, gameplay patches, mods or party options. Changing the password again won't repair a version mismatch.
Walkthrough 04
Assign host and guest roles and launch host first
Now check the roles. On the computer that will own the world, Party Mode should say Host a party. On the other computer, it should say Join a party. Give the players different names and match Max players. Ours is set to three, even though only two of us are connected. The host needs to launch first and reach the game. Leave it running while the guest joins. If both launchers are waiting to join, there's no host for either one to connect to.
For the Radmin method shown here, the host selects Radmin VPN under Host over a VPN. The launcher displays a VPN address with port nine three zero seven. If you send an address manually, copy that value from the host, rather than sending the guest's own address or an unrelated internet address. Here's the detail that's easy to miss. Radmin's network password and Bloodborne's party password are separate. The network password gets you into the virtual network.
The party password gets you into the protected game session. Being accepted by one doesn't mean the other is already correct.
Walkthrough 05
Match the separate party password
Set a party password on the host and enter the exact same password on the guest. In our test, the guest uses a plain VPN address and port. The project requires a party password for that plain-address route. This isn't a claim that the full generated party-code method always needs one. In the guest's launcher, look at Parties found. My friend's recording shows the host name, build, slots and area. With Party discovery enabled and the host running, select that row and click Join selected.
The small password window is expected for a protected party. Enter the game's party password and confirm it. Don't mistake that request for a failure before you've actually entered the password.
Walkthrough 06
Try the current host address and verify Together
If discovery is empty but the VPN connection is established, try the manual route: set Join a party, paste the host's VPN address and port into Party code, enter the matching party password, and launch while the host is already in the world. If you've changed the host's party password or generated a new code, copy the current details again. Don't keep retrying an older code from a previous setup. For reference, our recording leaves UPnP and the relay option enabled, with public DHT discovery and IPv6 off.
Those settings describe this working Radmin setup. Flipping every connection switch at once makes it harder to tell which change helped, especially if you're using a different connection method. If it still stalls, check the game's firewall permission on both PCs, especially the host. The executable to look for is bbport dot exe inside the port package. Use an app-specific permission for the network you're using; you don't need to shut down the whole firewall for this guide.
Once the guest loads, check the actual game state. On my side, we get the summon message and my friend's character appears. On his side, he reaches the same area. The Party page says Together. That's stronger confirmation than only seeing a name in the VPN window. If the party connects but a new character isn't appearing beside the host yet, check whether the opening section is still required. Also read the party status before assuming the network has failed; a join can be waiting on the host's current activity.
Gather the party is available from the host's in-game Party page after you're connected. It asks the guest before bringing them over. Use it when you need to regroup, not as a substitute for a correct address, password and host setup. If you're still stuck, keep the exact message and the launcher log from both PCs. Note whether the guest stopped at network connection, party discovery, password confirmation, loading or summoning. That makes a report much easier to investigate than a screenshot that only says it didn't work.
If your result differs
| Situation | Next useful check |
|---|---|
| The process stops at a different checkpoint | Record the exact message, current build and last successful stage. Compare that stage with the matching video section. |
| A setting is selected but the result differs | Repeat the same scene and change one option at a time. A menu target does not establish measured performance. |
| A newer release changes the interface | Check the linked release notes and instructions. This companion preserves the recorded route and its limitations. |
Comments
Post a Comment