ARC Raiders Expeditions: Verify What Changes Before Departing

Separate a raid from an Expedition

An ordinary raid returns to the ongoing progression loop when you extract. The Expedition system concerns a different long-term decision with preparation and departure conditions. Do not interpret a familiar word as proof that the two actions have the same consequences.

Use the current official Expedition information and in-game project screen. An older help article can explain the general concept while missing later changes. Check publication or update dates and read the relevant newer notes before relying on a reset checklist.

This page does not promise a fixed current departure date, reward amount or recurring window. Those are live operational details. The useful planning task is understanding the present choice and preserving a clear list of what the game says will change.

Build a current change-and-carryover list

Write the progression categories that the current system identifies as changing and those it identifies as retained. Keep uncertain items pending until the official source or interface resolves them. Do not fill gaps from a friend's experience during an earlier cycle.

Embark's September 8, 2026 update changed quest handling so an Expedition no longer resets quests by default and offers a choice. That dated change is a concrete reason not to copy a 2025 reset list unchanged. Read the actual current selection before confirming.

For a worked example, a Raider has unfinished quest progress and assumes departure will erase it automatically. They review the current choice and decide deliberately instead of discovering afterward that their expectation came from an outdated guide. The administrative check happens before the irreversible confirmation.

Compare the next cycle with your actual goals

Consider whether you want a fresh progression loop and whether you understand the resources and preparation required. A reward shown on a page does not establish that departure is the right choice for every player. Keep the value of current projects and the intended future session in the comparison.

Do not rush because a window creates urgency without first reading the conditions. If a requirement is incomplete, use the supported process and current notice rather than an unofficial shortcut or a promise that a missing step can be bypassed.

In a group, communicate the personal progression change. Teammates may be planning around equipment or access you will no longer have. Shared play can continue with different progress, but the dependency needs to be understood rather than discovered in the next deployment screen.

Confirm through the official interface

Read the final summary slowly and verify the selected options. Keep any confirmation or status the game provides. Do not assume a button click succeeded if the interface still shows the prior state, and do not repeat a major action blindly when a response is delayed.

After departure, inspect the actual starting state and choose one manageable next objective. If it differs from the documented expected result, use official support with the date, version and relevant details kept private. This website cannot restore progression or determine eligibility.

Finish by dating the record and linking the source used. Expedition systems evolve, so a careful guide should preserve the method of verification rather than pretend one reset list is timeless. The useful outcome is a chosen progression change with understood consequences, not a rushed reset driven by an old schedule or a reward headline.

Questions that come up