Baldur's Gate 3 supports cross-play between PC, Mac, Xbox, and PlayStation 5 through Larian Network. The feature makes it possible to plan a campaign around friends' platforms rather than one hardware ecosystem, but a little preparation prevents the most common avoidable friction.
This is a spoiler-free setup guide. It focuses on the confirmed cross-play basics and on simple group coordination, not on character builds or story decisions.
Start with a group decision, not a save file
Before anyone creates a campaign, decide who will host and whether the group wants a modded or unmodded run. The host should be someone whose schedule and connection make them a sensible continuing point for the campaign.
Larian's Patch 8 announcement says players can create and join cross-play lobbies through Larian Network. Treat that as the shared starting point: make sure every player can access the relevant account and lobby flow before the first long session.
Keep versions aligned
Cross-play is not a reason to ignore updates. Ask everyone to install the current game update before the first session, then make the same check whenever the group returns after a break. That is a simple habit, but it avoids turning planned game time into troubleshooting time.
The publisher's Patch 8 note confirms cross-play and cross-platform progression across PC, Mac, Xbox, and PlayStation 5. It does not mean that every player can use a different game state or mod setup.
The mod rule: match the host
If the group plans to use mods, make the mod list a deliberate shared decision. Larian says that all players joining a cross-play lobby must have the same versions of the mods installed. The game can prompt players through Mod Verification to enable, update, downgrade, or install missing mods.
That makes an unmodded first campaign the lowest-friction choice for a group that mainly wants to get started. A modded group can work well too, but only if someone maintains a short written list of the intended mods and versions.
A practical mod checklist
- Pick a host before selecting mods.
- Share one agreed mod list with the whole party.
- Have everyone complete the game's verification prompts before the session begins.
- Do not add or update a mod mid-campaign without telling the group.
- If a player cannot match the list, return to the shared baseline before troubleshooting anything else.
Build a session routine
Cross-play solves platform access; it does not solve party coordination. Agree on a few basics early:
- A regular session time and a way to say when someone will miss it.
- Whether the host advances the campaign without the full party.
- A light note of the current quest or next destination, kept free of spoilers for absent players.
- Who makes final decisions when the party is split.
These are social choices, not game requirements, but they make a long role-playing campaign easier to resume across different devices.
What to do when someone cannot join
Work from the least invasive checks first:
- Confirm that everyone is attempting to join the intended cross-play lobby through Larian Network.
- Confirm the game is updated on every platform.
- If mods are enabled, confirm every player has the same mod versions as the host.
- Restart the lobby flow after those checks rather than repeatedly changing unrelated settings.
Avoid guessing at platform-specific fixes that are not documented by the publisher. If the problem persists after the shared checks, use Larian's current support materials and state the platform, game version, and whether the campaign uses mods.
The useful takeaway
Patch 8 made a PC, Mac, Xbox, and PlayStation 5 party possible. The key to a smooth campaign is not a hidden setting: it is a shared lobby, matching updates, matching mods when mods are used, and a small amount of group planning.