ARC Raiders skill tree planner: build, point cap and share link
Spend points across the three branches, see what unlocks next, and save the finished build as a link.
How we calculate
The source states one unlock rule, and it has two halves: you need at least one of the named earlier nodes, and at the same time enough points spent inside that branch. Both halves are checked together, so a node with only half the requirement met stays closed, and the planner says which half is missing instead of simply refusing.
The cost of a single rank is not published anywhere, so every rank counts as one point. That is the simplest assumption available and it is stated here rather than hidden. The level point cap comes from the data, with a warning next to it, because the same source also carries a second, smaller number. Expedition points exist too, but the total number of expeditions is not established, so the available points field stays editable.
A build link carries the tree version. The developer announced a skill revamp, and once the node list or its order changes, an old link would place points on different nodes in the same slots. Instead the planner reads the version, notices the mismatch and says so plainly, leaving the tree empty.
Sources
checked 18 August 2026
Questions and answers
Why does the tree have 45 nodes rather than 38?
Because that is how many the source page lists: three branches of fifteen rows each. The figure 38 and the 14/14/10 split come from the task description and did not survive our own parse of the page. We kept what the source shows and recorded the discrepancy instead of trimming the tree to the expected number.
Is the point cap 76 or 75?
Both numbers appear in the same article, so we refuse to pick one silently. We use 76, since that is the number in the sentence about points earned per level; 75 stays alongside as the alternative and the counter carries a warning. Official patch notes will settle this, not a retelling.
Why does every rank cost one point?
Because the per rank cost is not published at all. One point per rank is the simplest assumption consistent with how the system is described, and it is stated openly in the explanation above. If a published cost appears, the counters will need recalculating, which is why the assumption is kept in plain sight.
What happens to an old link after the tree changes?
The link carries a tree version number. If the node list or its order changes, that number changes too, and the planner refuses to restore the build and shows a warning instead. This is deliberate: points quietly rearranged would look like a working build while meaning entirely different skills.
Can the whole tree be maxed out?
No, and the arithmetic shows it: the sum of every rank in the tree is roughly twice the point cap. That is why the planner reports two separate percentages, one against the point cap and one against every rank in the tree. The second one never reaches a hundred, and that is not a calculation error.
Unofficial tool. Not affiliated with Embark Studios.