ARC Raiders · Practical guide
How ARC Raiders Players Organize Progression and Gear Choices — Comparing Common Approaches #1
ARC Raiders, Embark Studios' PvPvE extraction game set on a machine-held future Earth, rewards players who make decisions before a match rather than during a panic. Anything you carry onto the surface can be lost, and only what you extract stays in your stash, so progression is really a series of small bets. This guide turns those bets into a seven-day routine: one setup evening, a short checklist before every raid, a gear log you fill in afterward, and a weekly review that tells you when a loadout has earned a change.
Day one: set up a ledger instead of a wish list
Most players open the week by thinking about what they want to build. A more useful start is writing down what you already own. Spend the first evening, or the first half hour of it, sorting your stash into three groups and noting them in a plain text file or a paper notebook.
- Keepers: items you would be genuinely annoyed to lose, which stay at home until you have a clear reason to take them out.
- Working kit: gear you are comfortable risking on an ordinary run, the pool you will actually draw loadouts from this week.
- Surplus: duplicates and materials with no current recipe attached, which you can spend, recycle or bring along as cheap filler.
Then set a single goal for the week. It might be a crafting target, a stash size you want to reach, or simply finishing more raids alive than last week. One goal keeps the later decisions short, because every item and every exit can be judged against it. If you play in a squad, share the goal with the group so nobody is surprised when you leave a fight early to protect the haul.
Before each raid: a sixty-second loadout decision
The routine only works if the pre-raid step is quick enough that you actually do it. Answer the same four questions every time you queue, ideally out loud if you play with a squad, so everyone hears the plan. The answers do not need to be clever; they need to be consistent, because consistency is what makes the log comparable later.
- What is this raid for: materials, a specific component, practice, or a relaxed run with friends?
- Which working-kit items match that purpose, and which keepers can stay safely in storage?
- What is the most I am prepared to lose here if the run goes badly, counted in items rather than hours?
- What signal will tell me to head for extraction early, such as a full bag, low supplies or a squadmate down?
Weapons in ARC Raiders are equipment like any other item: something you carry in, may lose, and may need to rebuild. Choosing one is a budget question first. A modest option you can replace after a bad evening often supports the weekly goal better than a rare one you hesitate to use.
After each raid: a gear log you can read on Sunday
The log is the heart of the routine. Right after extraction or a lost run, add one short line while the details are fresh. Five fields are enough, and they make patterns visible within a few sessions.
- Purpose and outcome: what the run was meant to achieve and whether it extracted, failed or ended early by choice.
- Kit taken and kit lost: the main items you carried and which of them you no longer have.
- Net haul: the materials or components that actually reached your stash, not what you picked up along the way.
- One cause: the single moment that decided the run, written as a fact rather than a complaint.
- If logging by hand feels slow, a roundup of tools speed-focused raiders adopt is one place to compare utilities and habits, as long as anything you add stays within the game's rules.
Keep entries short. A line such as "materials run, extracted, lost nothing, haul fits weekly target" is more useful on review day than a paragraph of frustration written after a defeat.
Midweek: when a loadout has earned a change
Changing kit after every loss feels productive but usually just adds noise. A better rule is to wait for evidence across several runs. By the middle of the week your log should show whether a setup is working, and the change triggers below keep the decision honest.
- The same item appears in the lost column three times without helping you extract, so it is costing more than it returns.
- Your net haul keeps falling short of the weekly goal even on runs that end safely.
- Your working kit pool is shrinking faster than surplus and crafting can refill it.
- An official update or patch note changes an item you rely on, so your earlier entries no longer describe the current game.
Rankings are tempting at this point, and a ranked weapons list arguing early loadouts count makes the case that what you carry shapes your progress from the first days of an update. Use a list like that to pick candidates for testing, then let your own log decide whether a new choice stays in the rotation.
End of week: three ways to run the review
On the last evening, read the log from top to bottom and pick one of three review styles. Each fits a different kind of week.
- Steady review: nothing changed much, so you keep the same loadout and adjust only the goal; fits weeks when the log shows slow but reliable gains.
- Swap review: one or two items rotate out of the working kit and surplus gets crafted into replacements; fits weeks when a change trigger fired.
- Reset review: you return to cheap, replaceable kit for a few days to rebuild the stash; fits weeks of heavy losses or a major update.
Finish with a quick checklist: did you meet the weekly goal, which item cost the most, which run gave the best haul, and what single habit will you change next week? Write the answers at the top of a fresh page so the next cycle starts from evidence.
Keeping the routine light
None of this needs to feel like homework. The ledger takes one evening, the pre-raid questions take a minute, and the log takes a line per run. Over a few weeks, that small effort replaces guesswork with a record of what actually moves your stash forward, and gear choices start to feel like plans rather than gambles.