
In this article (4)
Arc Raiders analysis: you can't have everything
Key Takeaways
- Treat skill trees as decision systems, not completion checklists.
- Use hard limits to make builds readable, distinct, and worth debating.
- Guide players with clear priority paths while leaving room for weird builds.
Why it matters
- ProductProduct leaders can use constrained progression to make choices feel meaningful without adding endless feature bloat.
- InvestorsInvestors should watch systems that deepen retention through player identity rather than raw content volume.
Embark's reworked skill tree is a reminder that progression should create decisions, not just another chores menu with fireworks.
A skill tree that lets you unlock everything is not a tree. It is a grocery list with particle effects. The second every player can become the same maxed out murder spreadsheet, buildcrafting turns into homework with better lighting, and nobody needs more homework. Arc Raiders is poking that sacred completionist goblin directly in the eye, and honestly, good.
PC Gamer's report lands on the real lesson
PC Gamer framed the Arc Raiders skill tree change with the bluntest possible thesis: "You can't have everything." The same PC Gamer headline quotes the design rationale as, "We believe that creates more interesting choices and supports more playstyles." That is not just a balance note, that is a design philosophy wearing steel toe boots.
The important part is not that players lose access to toys. The important part is that the system stops pretending every decision is meaningful while quietly letting everyone arrive at the same final blob. If your build can do everything, your build says nothing, like a character creator where every face slider somehow ends at Handsome Squidward.
Hard limits make identity visible, which is the whole point of a skill tree unless we are just decorating a spreadsheet, 6 out of 10 glowing nodes.
Eurogamer's Embark report shows why timing matters
Eurogamer reports that Embark Studios is looking to heavily rework Arc Raiders' skill trees in future updates. That matters because skill systems are foundation work, not garnish. Change them late and players feel like the floor moved; change them thoughtfully and the whole game gets better at asking, "Who are you in this squad, and what are you giving up to be that?"
This is where the anti completionist move gets interesting. A constrained tree can make support, mobility, survival, and damage priorities feel like actual commitments instead of a queue you clear while listening to a podcast. The DMV of UIs is the one that asks you to fill every form eventually. A good progression system makes you pick a window, accept the cost, and live with the receipt.
Arc Raiders Hub turns constraint into a practical build path
Arc Raiders Hub's Recommended Skill Tree Progression Guide, updated June 3, 2026, says there are 76 skill points available before expedition rewards. The guide recommends a path that prioritizes mobility for everything, survival for loot optimization, and conditioning once fundamentals are locked in. That is the useful player facing version of constraint: not fewer decisions, but decisions with a shape.
That flow is why "you can't have everything" can feel generous instead of stingy. It gives new players a sane route without deleting weirdos who want to spec into some cursed niche plan and call it art. I will defend those weirdos with my whole chest, because half the joy of extraction style play is watching someone survive through decisions that look illegal but somehow work.
PC Gamer's quote is a design warning, not just a patch note
PC Gamer's cited line about creating more interesting choices and supporting more playstyles should be printed out and taped above every progression meeting. More content is not automatically more choice. Sometimes it is just more buttons between the player and the thing they actually care about.
The lesson for designers is painfully simple: progression is choice architecture. If everyone can unlock everything, the system rewards time served more than intention, which is how you get builds that feel like tax documents. If the tree has hard edges, players start making plans, comparing tradeoffs, and arguing about routes, which is how you know the system has a pulse.
The watch item now is how Embark turns this principle into the actual Arc Raiders player experience. If the limits are clear, respec friction is sane, and the tradeoffs are legible, this could be a strong case study in why saying no creates better play than handing everyone the entire buffet. If the limits are muddy, welcome back to menu jail. Either way, builders should pay attention, because the cheapest way to make progression matter is not more nodes, it is better consequences.
Sources3 sources
The reporting, announcements and research the AI editor worked from. Links open the original publisher.