Arc Raiders players who clear the 100K damage challenge were not just finishing a milestone. They were getting automatically signed up for the upcoming fourth Expedition, which includes being “shoved off to the wasteland” without telling them. In other words, a core gameplay accomplishment could trigger a forced account-level outcome tied to the Expedition system, and that is exactly the kind of mismatch that makes players furious, churn, and then ask questions later in support tickets.

Embark’s response is blunt about timing. It says it will “revert the Departure sign-up for players whose sign-up behaviour appears representative of this issue,” and that the reversion will happen “in several waves, starting tomorrow, Friday, July 17, 2026 5:00 PM.” Even before the weekend, the studio’s instruction is practical: players should “check the in-game Expedition tab and verify that it shows the correct information for your case.” If the fix does not revert by the end of the day tomorrow, Embark tells affected players to “reach out to our support team as soon as possible.” And for anyone who genuinely wants to depart, Embark says the player can still opt in, because “Last Call will be available as usual for those of you who aren’t able to sign up for Departure before the deadline.”

To understand why this is such a big deal, you have to look at what Expedition means inside Arc Raiders. The “clearing your raider for Expedition” step is described as a “pretty big deal.” It involves tons of prep and a commitment to start the next season with a fresh character and stash, plus perks offered by the Expedition for the new avatar. That is not a casual toggle. It is a major player decision about progression, inventory, and identity in the game world. So when a bug turns part of that system into an automatic, hidden sign-up, it violates the expectation that the “Departure” choice is something the player controls.

This is where incentives matter, not just for players but for any operator running live service games. Players are typically willing to accept loss and trade-offs when they chose them consciously. They are less willing when the system makes the trade for them, even if the studio later reverts it. That difference shows up immediately in sentiment, and then it ripples outward into support costs. If people have to open tickets, provide screenshots, or document their intentional behavior, the operational load increases. The source even includes a Reddit quote that captures that fear: one player says they are “taking a screenshot of my intentional signup, damage completion and Expedition vault contents” so they can “open a ticket when they fuck this up.” Whether or not you like the language, the underlying point is serious: even players who did the right thing are preparing for the system to behave wrong.

Embark is trying to contain the blast radius with a cautious policy. The message to players explicitly says, “We want to err on the side of caution.” That is a subtle but important signal. It implies Embark is not simply flipping a global switch. Instead, it will revert the Departure sign-up for players whose “sign-up behaviour appears representative of this issue.” In live operations, that approach aims to avoid secondary harm, like undoing legitimate sign-ups for players who truly opted in. But it also means the fix depends on classification, detection, and timing. That is why the developer still tells everyone to check the Expedition tab, because the “correct information” may not appear instantly for every affected account. And it is also why Embark provides an escalation path: if the revert does not happen “by the end of day tomorrow,” contact support.

There is also a product-and-communication angle that matters for decision-makers. Embark is telling players how to verify status, how to escalate, and how opting in still works. It also points to “Last Call” being available “as usual” for those who cannot sign up for Departure before the deadline. That matters because a bug like this can turn a deadline into a trap. If a player thinks they are locked out due to a system error, they might either miss content or get stuck in a confusing state. By reiterating opt-in and Last Call, Embark is reducing the odds that players interpret the bug as a permanent change.

Second-order implications are not theoretical here. Auto sign-ups that alter progression and inventories can create persistent trust problems. Even after a revert, players may ask whether other Expedition-adjacent features are accurate. In addition, if a player’s raider clearing is tied to timing and seasonal structure, then any confusion about sign-up state can affect readiness for the next season. In other words, a bug that triggers “Departure sign-up” at the wrong time can indirectly affect engagement in the very window where live games most need player confidence. From a board or investor perspective, that is the real cost: not just the immediate annoyance, but the downstream risk of reduced willingness to participate in future seasonal resets.

For executives watching this space, the lesson is simple and uncomfortable. Systems that transform player effort into account outcomes must be transparent at the exact moment the outcome is created. When the system can exile players after they complete a “100K damage challenge,” the operational response has to be fast, targeted, and verifiable. Embark is saying it will revert starting Friday, July 17, 2026 at 5:00 PM, in waves, while advising players to check the in-game Expedition tab and contact support if needed. The strategic stakes for everyone in live service are clear: the fix may restore the data, but the comms and verification determine whether trust returns alongside it.