ARC Raiders fixed its crossplay mess fast, but the workaround was a warning sign

Breaking crossplay in a multiplayer extraction shooter is not a small oops. It is the kind of mistake that turns a content patch into a trust test, and that is exactly what happened when ARC Raiders pushed its 1.26.0 “Riven Tides” update on April 28. The patch brought a new map, a new Beachcombing condition, an ARC Turbine enemy, and fresh items. It also quietly kneecapped one of the game’s basic social promises by disabling crossplay across PS5, Xbox Series X/S, and PC. Embark Studios did move quickly with a workaround and then hotfix 1.26.1, but the real story is uglier than “bug fixed.” Players were asked to choose between playing with friends and keeping their carefully tuned settings intact. That should never have been the trade.

This was not just a toggle bug

The surface-level version is simple: after patch 1.26.0, the crossplay option in the Gameplay > Online menu was either switched off or effectively locked off for many players, which meant matchmaking was restricted to same-platform pools. In practice, that does more than inconvenience squads. It fragments the player base, slows queue health, and punishes the exact players a live-service game supposedly wants to keep engaged: the ones logging in immediately after a major content drop.

That matters more in ARC Raiders than it would in some giant evergreen shooter with a bottomless population. Extraction games live and die on friction. The good friction is risk, scarcity, and that feeling that one bad decision can cost you a run. The bad friction is menu nonsense, broken matchmaking, and technical problems that stop groups from forming before the match even begins. Patch 1.26.0 added the second kind at exactly the wrong moment.

Embark acknowledged the issue and recommended the immediate workaround: restore all settings to default. That did re-enable crossplay for affected users. It also wiped custom controls, keybinds, and accessibility-related preferences. So yes, the studio offered a fix. It was also the sort of fix that makes players stare at the screen and decide whether tonight’s session is worth rebuilding their entire setup.

The workaround solved the bug by making players eat the cost

This is the part PR language always tries to sand down. “Temporary workaround” sounds harmless. In reality, asking players to reset everything to default is blunt-force troubleshooting. It shifts the labor from developer to player. That is annoying for anyone. For players using custom sensitivity, remapped inputs, or accessibility adjustments, it is worse than annoying. It is a quality-of-life hit disguised as a menu reset.

There is also a useful industry lesson here. Live-service teams love to talk about player retention, squad play, and reducing barriers to engagement. Then a bug like this lands, and the emergency fix is “delete your preferences.” Those two ideas do not coexist nicely. If a game wants to be taken seriously as a long-tail multiplayer platform, settings integrity has to be treated like account integrity. Not identical, obviously, but close enough that wiping them should feel like a last-resort disaster recovery step, not the first public recommendation.

The uncomfortable observation is that this patch already had other points of player friction swirling around it. Background coverage on the wider Riven Tides rollout also flagged complaints about balance and durability changes, which meant Embark was not operating in a calm environment to begin with. When a content update is already drawing heat, even a fast technical response gets read through a harsher lens. That is not unfair. That is the tax for shipping a destabilizing patch into a live game.

Hotfix 1.26.1 matters because it restores confidence, not because it exists

The follow-up fix, patch 1.26.1, is the more important development than the workaround because it appears to restore crossplay and stabilize matchmaking without forcing players to keep living with a broken menu state. That is the baseline outcome players needed. Not a Discord message. Not a menu ritual. A proper patch.

Still, nobody should hand out participation trophies for cleaning up a launch-week problem your own patch introduced. The meaningful takeaway is that Embark responded quickly enough to stop this from becoming a longer-term population problem. In a multiplayer game, speed matters. Every extra day of broken cross-platform matchmaking teaches players not to trust major updates, and once that habit sets in, it is hard to reverse. Plenty of live-service games have learned this the ugly way: one rough patch does not kill momentum, but rough patches that train players to wait for the “real” version of the update absolutely do.

The better reading of 1.26.1 is not “Embark fixed it, all good.” It is “Embark avoided turning a technical own goal into a broader confidence crisis.” That is a meaningful difference. Gamers are used to hotfixes. What they are less forgiving about is when a studio normalizes destructive workarounds or acts like broken social features are edge-case annoyances. Crossplay is not optional glue in 2026. In games like this, it is structural.

What Embark needs to prove next

The next thing worth watching is not another apology post. It is whether Embark explains why the patch locked crossplay off and whether it hardens settings persistence so this kind of workaround is not needed again. That is the developer-facing question hanging over this whole episode. A reset-to-default fix suggests either corrupted config handling, a migration problem between patch versions, or a bad interaction between platform-side and user-side settings. Whatever the exact cause, players do not need the entire postmortem, but they do need evidence the failure mode is understood.

There is also a practical follow-up. If 1.26.1 really settles matchmaking, queue quality and cross-platform party behavior should normalize quickly. If players continue reporting weird lobby splits, failed group formation, or inconsistent crossplay states after the hotfix, then this story is not over. In live-service terms, the patch note is not the finish line. Stable behavior over the next several days is.

• Patch 1.26.0 introduced Riven Tides content but accidentally disabled crossplay across PC, PS5, and Xbox Series X/S.
• The initial official workaround was a full settings reset, which restored crossplay but erased custom controls and accessibility preferences.
• Hotfix 1.26.1 is the real fix to watch because it aims to restore proper matchmaking stability without making players rebuild their setup.
• The bigger issue is trust: multiplayer games cannot afford to break social features on patch day and call a settings wipe an acceptable stopgap.

ARC Raiders does not have a crossplay story right now. It has a patch discipline story. Embark recovered faster than some studios do, and that matters. But if the lesson from 1.26.0 is that core matchmaking features can break and the backup plan is “reset everything,” then the studio still has work to do beyond shipping 1.26.1.