Define the role
A build page should start with what the class is supposed to do, not with a random list of upgrades.
Skill trees should be planned around a job: survive solo, burst a target, support a squad, clear PvE, or hold space during extraction.
Update with verified launch-build screenshots, exact values, patch notes, and official wording when available.
A build page should start with what the class is supposed to do, not with a random list of upgrades.
Take upgrades that make the main role consistent before adding luxury damage.
A skill path is only good if it supports the routes and fights you actually take.
| Search problem | Best answer | Why it matters |
|---|---|---|
| Solo | Escape or sustain | Burst or scouting |
| Squad support | Healing or control uptime | Survivability |
| Boss clear | Sustained damage | Recovery tools |
Skill tree pages catch players after they already chose a class. That is high-intent traffic because they are deciding what to upgrade next.
Until exact launch trees are captured, this page explains upgrade logic. After launch, add node names, costs, and screenshots.
What should I upgrade first?
Upgrade the tools that make your chosen role consistent: survival for solo, control for support, and reliable damage for boss or PvP builds.
Are exact skill nodes listed?
Not yet. Exact node names and values should be added only after the launch build is verified.