Embark Is Rebuilding ARC Raiders' Skill Tree From the Ground Up

I want to be careful with this one, because there’s a lot of breathless coverage floating around and the actual news is both bigger and smaller than the headlines suggest. Embark Studios’ design director Virgil Watkins has confirmed that ARC Raiders’ skill tree is getting significant changes to better serve the game as it exists now and years into the future.

That’s the quote. Not “coming next patch.” Not “launching in May.” A design-direction statement that tells us where the game is heading, not when the rework ships. And that distinction matters enormously for anyone trying to plan how they play ARC Raiders over the next few months.

What Watkins Actually Confirmed

Let me separate the signal from the noise, because the community discourse has already started inflating this news into things it isn’t.

The confirmed facts:

Design director Virgil Watkins explicitly stated that the skill tree will see “significant changes” — not tweaks, not rebalancing, but structural reworks aimed at better serving both the current game and its long-term trajectory.

Embark is framing this as a response to how the game has evolved since launch. Internal data, player feedback, and design philosophy shifts are all being cited as reasons for the rework direction.

What Watkins deliberately didn’t commit to:

No launch window. No specific mechanic details. No confirmation of whether existing builds will be grandfathered, reset, or forced to respec. This is a direction statement, not a patch announcement, and treating it as the latter is where community speculation goes off the rails.

Why the framing matters: When a design director publicly commits to “significant changes” without a date, it usually means the internal design is still being iterated. That’s actually a good sign — it means Embark is taking the rework seriously enough to not rush it. But it also means players need to plan for uncertainty rather than a specific timeline.

What This Signals About ARC Raiders’ Direction

Let me offer an honest read on what Watkins’ comments likely mean, separated by confidence level so you can calibrate accordingly.

High confidence (based on explicit statements):

The current skill tree has systemic issues that a patch-level balance pass can’t fix. If surgical balancing was enough, Embark would be doing that instead of committing to a rework. The language “better serve the game” implies the current tree is actively holding something back.

Medium confidence (based on pattern recognition):

Expect the rework to reduce build homogenization. Most extraction-shooter skill trees end up with 2–3 dominant builds after the community settles, and Embark’s public emphasis on “years into the future” suggests they want more durable build diversity than the current tree provides.

Low confidence (pure interpretation, flag it):

The rework may shift ARC Raiders further toward class-like identities rather than the current hybrid system. This is speculative, based on how other extraction shooters have evolved their progression systems. Don’t build your strategy around this prediction.

What Embark almost certainly isn’t doing:

A full-game pivot or a genre shift. “Significant changes” to the skill tree is a progression system rework, not a reinvention of what ARC Raiders fundamentally is. Players worried about the game becoming something different can relax on that front.

My Reproducible Pre-Rework Testing Framework

I don’t want you trusting my take on any of this without doing your own verification. Here’s exactly how I’d recommend testing the current skill tree so you have a baseline when the rework eventually ships:

• Character baseline: Document your current skill tree build with screenshots, and note the specific passives you rely on
• Test scenarios:
  • Scenario A: Solo extraction run, standard difficulty, measure extraction success rate over 10 runs
  • Scenario B: PvP engagement testing, track win rate in contested zones over 20 encounters
  • Scenario C: PvE ARC encounters, measure time-to-kill on named ARC units
• Metrics to log: Extraction success rate, time-in-match, engagement win rate, damage taken per encounter
• Sample size: Minimum 10 runs per scenario, ideally 20+ for statistical reliability

Why this framework matters: When the rework eventually ships, you’ll have hard data on what your current build actually does — which is the only way to honestly evaluate whether the new tree is better, worse, or just different for your playstyle. Most players rely on vibes when evaluating reworks, and vibes lie constantly.

Ten runs minimum is the statistical floor. Anything less and you’re measuring noise rather than actual performance.

What We Know Versus What We Don’t (Quick Reference)

Source for the confirmed statements and their framing: and

What Playing ARC Raiders Between Now and the Rework Actually Looks Like

Let me replace the usual “patch predictions” section with what the player experience will likely feel like across the waiting period.

The immediate weeks feel unchanged. The current skill tree is what you’re playing, and nothing has shifted yet. If you’re enjoying your build, keep running it. There’s no tactical reason to stop playing because of a future rework announcement.

The middle stretch — once more details drop — will feel weird. Community discourse shifts toward speculation, content creators pivot to “what the rework might do” videos, and the meta stabilizes as players stop experimenting while waiting for the rework. This is when ARC Raiders engagement usually dips during any major rework announcement cycle.

The week before rework launch is when prep matters. Hoard resources, document builds, finalize any progression you want locked in pre-rework. This is the strategic window that rewards paying attention.

Launch week of the rework itself will feel chaotic. Expect balance issues, unexpected interactions, and a 48-to-72-hour window where the “optimal build” is genuinely unclear. This is where SSF-style testers thrive and meta-followers struggle.

That’s the experience chain. Not a prediction of dates — but a map of how the rework announcement will ripple through the game’s feel over the coming months.

Where to Focus Right Now

A few honest observations from watching extraction shooter reworks play out in other titles:

Don’t stop progressing your current build. Rework-induced paralysis is the single biggest mistake players make after announcements like this. Your current progression still counts, still teaches you the game, and will likely translate in some form through whatever the rework ships.

Document what your current build actually does. Screenshot your skill tree. Record a few runs. When the rework drops, you’ll want hard reference material to honestly evaluate whether the new system is serving you better. Memory lies after reworks — footage doesn’t.

Diversify your resource stockpile. Post-rework economies always shift. Items that were valuable pre-rework sometimes crater, while previously ignored gear becomes meta. Hold diversified assets rather than consolidating into what’s currently optimal.

Stay skeptical of early leak claims. Until Embark publishes patch notes, any “confirmed rework details” circulating on social media are almost certainly speculation dressed up as insider knowledge. Watkins’ quote is the only sourced statement that exists right now.

Respect the uncertainty. No launch window means no launch window. Don’t build strategic decisions around speculative timelines.

A Practical Note on Loadout Prep

If you’re planning to make the most of the pre-rework window — testing builds, running benchmarks, stockpiling for the eventual transition — you can Buy ARC Raiders Items on U4GM.com. I’ve used them when I needed to run comparative build testing without spending 30+ hours farming equivalent gear per variant. Fair pricing, reliable delivery, and their stock tracks current game economy, which matters when you’re trying to establish a real pre-rework baseline before everything shifts.

Not a shortcut around learning the game. Just a way to skip the parts of the grind that keep you from doing the actual testing work that matters when a rework is coming.

Final Thought

Embark committing publicly to significant skill tree changes is the most substantial design signal ARC Raiders has sent since launch. The fact that Watkins framed it around “years into the future” rather than a specific patch is, honestly, the most encouraging part. Studios that rush reworks break games. Studios that take the time to do reworks properly make games that survive their second year.

My advice: keep playing, keep documenting, and keep your resource base diversified. When the rework finally drops — whenever that is — you’ll be one of the players who has hard data on what changed, rather than one of the players arguing about vibes on Reddit.

Don’t panic. Don’t speculate. Do prep. See you in the extraction zones — current skill tree and whatever comes next.