Bloodborne PC co-op setup: game preparation, Radmin and a verified two-PC join
ItsOOGWAY · PC guides & recorded tests
Bloodborne PC co-op setup: game preparation, Radmin and a verified two-PC join
Play Bloodborne co-op on PC with a friend: this complete Windows guide covers the game update, launcher, Radmin VPN, host settings, guest settings and a successful two-PC join.
The key checkpoint: Use the matching recorded port on both PCs, separate VPN credentials from the game-party password and launch the host before joining from the guest.
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
Two PCs in one world
My friend is joining my Bloodborne world from another PC. You can see the summon message, his name, and both of us moving in the same area. This is the result we're setting up today. I'll show the full process from the Windows download to the game files, the network, and the settings on both computers. So if you're the person hosting, or the friend trying to join, you can follow your side without guessing what the other person needs to do.
The build in this recording is Bloodborne PC version zero point seven point five, from the project linked in the resources section. Co-op is still being developed. What I'm showing here is our successful two-PC connection and short in-game test. Before you download the launcher, both players need their own compatible Bloodborne files with update one point zero nine merged into the base game. My recording uses CUSA zero three one seven three. The important part isn't just the edition name on the package.
It's having the supported, updated files that this port expects. Both PCs also need to run the game themselves. This isn't streaming one person's game to the other computer. For this project, check that you're on sixty-four-bit Windows, with an AVX2-capable CPU and a Vulkan 1.3-capable graphics card and driver. The release includes the Python runtime needed by its launcher. Use the same port release on both computers. Don't update only one side halfway through setting up the party.
Matching game files, gameplay modifications and party options will save you a lot of confusion when it's time to connect.
Walkthrough 02
Windows port and extractor downloads
Open the linked GitHub project, go to Releases, and download its Windows package. Extract the whole ZIP into its own folder. Keep the supplied files together; you don't need to build the source code for this method. If your game files are already extracted and updated, you can move to the launcher section. If you're starting with your own PKG files, you'll also need the standalone PKG Extractor. Get the Windows package for version one point one from its official release page and extract it too.
Find your base-game PKG and drag it onto pkg underscore extractor dot exe. You'll see a terminal listing the files as it extracts them. Leave that running until it finishes. I'm shortening the wait in the edit, while keeping the drag-and-drop action clear. Extract your matching update package the same way. Now we have the base-game folder and the extracted update contents. The next step matters: the updated files need to go into the base game, rather than leaving the launcher pointed at an update-only folder.
In the recording, I open the extracted update folder, copy its contents, and paste them into the base-game folder. When Windows asks about replacing files with the same names, use the updated versions. Do this with the game closed, and keep a copy of your original dump before merging the update. The result should be one usable game folder, including the updated eboot.bin. Don't combine updates from unrelated game releases, and don't add a separate prepatched executable just because it says sixty FPS.
Start with the files supported by this port. Now open the Windows port folder and run launch underscore GUI dot bat. At the top of the launcher, click Browse and select eboot.bin inside your updated base-game folder. In my case, that's inside the CUSA zero three one seven three folder on the E drive. Your drive letter can be different.
Walkthrough 03
Create and join the Radmin network
Before adding your friend, make sure each computer can reach the game on its own. If one PC can't launch Bloodborne, fix that first. Changing the party code won't solve an incomplete extraction or a launcher pointed at the wrong executable. For this connection, we're using Radmin VPN. It gives the two computers a shared virtual network. Both of you need to install and open it. You don't need its remote-desktop server for this method; we're using the VPN connection.
On the hosting computer, choose Create network. Pick a network name and a password, then create it. Send those two details privately to your friend. On your friend's computer, choose Join network, enter that same network name and password, and join. This is what the extra recording from my friend's side shows. Check that you can see the other computer in Radmin before moving on to the game launcher. Keep Radmin running on both PCs.
We've connected the computers, but we haven't joined a Bloodborne party yet. That's the next stage, and it has its own settings. On the host PC, open the launcher's Party tab. Set Mode to Host a party and enter your name. In this run, Max players is set to three on both sides. We're testing with two people, but the configured limit still needs to match.
Walkthrough 04
Network password vs party password
Automatic summoning, Seamless party rules and Direct summon are enabled in this setup. Separate party saves is also enabled. Leave the other party rules at matching defaults for the first connection; you can experiment after you know the basic setup works. On the connection side, the port shown is nine three zero seven. I leave UPnP and the relay option enabled. Public DHT discovery and IPv6 are off in this recording, and Host over a VPN is set to Radmin VPN.
These are the choices used for our VPN connection, rather than a rule that every other connection method needs the same switches. The launcher shows a VPN address with the port attached. If you need to send an address manually, this is the host's address to copy. Your friend's own address is different, so don't swap those around. Set a party password in the Bloodborne launcher and give that to your friend as well. This is separate from the network password you entered in Radmin.
You can connect to the VPN successfully and still fail to join the game if the game's password doesn't match. That distinction also explains something important about this method. We're using the host's plain VPN address and port as the join address. That route needs the host's party password. A full generated party code works differently, so don't assume that every party must always have a password just because we're using one here. Once the host settings are ready, launch Bloodborne and enter a playable area.
Let the host's game finish loading before the guest launches. In our test, I'm already standing in the world when my friend joins.
Walkthrough 05
Successful summon on both PCs
Now switch to the guest PC. Open the same launcher version, select the guest's own updated eboot.bin, and go to Party. Set Mode to Join a party and use a different player name. Keep Max players matched to the host. With both computers in the same Radmin network and Party discovery enabled, the host can appear under Parties found. In my friend's recording, the list shows my host name, the available slots, the area, and build zero point seven point five.
Select the host and click Join selected. If the password window appears, enter the Bloodborne party password. This is a normal part of joining a protected party, not an error message. If the party doesn't appear automatically, the guest can paste the host's copied VPN address and port into Party code, then enter the same party password. Use the current value from the host's launcher. You don't need to copy the numbers from my video.
With the host already in the game, the guest can launch. My friend's recording shows the launcher starting Bloodborne, then the loading screen, and then his character entering the world. Keep the loading steps in that order; seeing a computer in Radmin is only the first checkpoint. For completely new characters, the project may still need you to finish the opening section before automatic summoning can bring you together. The host also has a Skip the prologue rule for new characters.
Our join here uses characters that are already ready, so I'm not showing a fresh-character playthrough. On my screen, we get the message that Lenovo has been beckoned. His character appears, his name and connection information are visible, and we can move around together. On his recording, you can see the same area from the guest side. That gives us confirmation from both computers.
Walkthrough 06
Community and testing
Once you're together, the in-game System menu has a Party page. In our session its status says Together. It also shows Summon again and Gather the party. Gather is for bringing guests back to the host, with a confirmation for the guest. It isn't a replacement for getting the initial connection working. If your friend can see the host but can't join, recheck the party password, the selected host address, and the port release on both PCs.
If the host never appears, start with the Radmin connection and Party discovery. For a blocked connection, check that Windows Firewall allows the port's game executable, bbport dot exe, rather than turning off your firewall entirely. Party play uses a separate save location. Before experimenting with an existing character, back up your user folder. The launcher has options for copying a single-player save into party saves and undoing a party session, but those aren't steps we need to click just to repeat the connection shown here.
That's the full route: prepare the updated game, open the Windows launcher, join the same Radmin network, configure one host and one guest, match the party password, and launch the guest after the host is ready. If you're testing Bloodborne co-op or other community PC projects, join my Discord through the link below. Share your build version and the exact step you reached. Whether you need a second person to compare settings with, or you've found something useful on your own PC, that's the kind of testing we're building the community around.
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