Crossplay & connection checks

The headline: launch-day crossplay matchmaking failures were fixed in patch 1.0.1 on September 8. If you're still hitting connection problems after that, you're in the long tail — usually version mismatches, platform network hiccups, or local network friction. Work this list top to bottom; it's ordered by hit rate, not by effort.

The checklist

1. 01

   Confirm you're on 1.0.1 or later. The single most common cause right after launch: an unpatched client. Restart your storefront/console and let updates finish.

2. 02

   Restart the game fully — not suspend/resume. Console quick-resume states are a reported source of stale sessions. Reported

3. 03

   Check the platform's network status (PSN / Xbox Live / Steam). If the platform is limping, no local fix matters.

4. 04

   Verify crossplay is enabled in the game's settings — and ask your party to check too. One member with it off constrains the pool for everyone in reports. Unverified

5. 05

   Test NAT / network restrictions. Strict NAT and aggressive firewalls are the classic asymmetric-multiplayer culprits. Console network tests and router UPnP settings are the usual levers.

6. 06

   Try solo queue once. If solo works and party doesn't, the problem is the party link (usually one member's NAT), not your install.

Known-issue territory

If the checklist passes and matches still fail: matchmaking-side problems beyond crossplay are tracked separately in matchmaking stuck or slow. Persistent, checklist-proof failures are worth reporting to the developers with your platform and region — and worth a note to us so we can track patterns.