Independent player guide

Hero Siege Incarnation Tree Guide

The Incarnation Tree opens at level 100 and replaced the old Hero Level skill tree in Season 9; the official Season 10 announcement says more than 600 new nodes were then added.

FocusHero Siege Incarnation Tree Guide: Unlock and Season 10 Nodes
FormatExplainer
Current boundarySeason and date labels stay attached to changeable details.

When does the Incarnation Tree unlock?

The official Season 9 announcement says it opens at level 100.

Opening level
Level 100 is the stated Incarnation Tree opening point in the Season 9 announcement.
Announcement version
Until that threshold is reached, treat the tree as later progression rather than a missing early-game menu.
Different client state
The threshold explains why a lower-level character may not see the system even when reading a current guide.

Continue ordinary progression until level 100 rather than searching for an unlisted quest or purchase. If a level-100 character still sees a different state, the Season 9 statement may no longer describe the live client; no alternate unlock procedure is established here.

What role does the Hero Siege Incarnation Tree play?

The Incarnation Tree is the level-100 progression system that replaced the old Hero Level skill tree in the Season 9 announcement.

That replacement explains why an older guide may name a different tree for the same stage of character growth.

The Incarnation Tree replaced the old Hero Level skill tree as the level-100 progression system in Season 9. An older Hero Level guide can refer to the predecessor rather than a second simultaneous tree. Recognizing the replacement prevents players from searching for both systems or applying old navigation to the Season 9 structure. The statement defines role and history only. It does not list node effects, reset rules, an optimal path, or how later seasons may revise the interface.

What changed in Season 10?

The Ebontharn announcement says more than 600 new nodes were added to the Incarnation Tree.

  1. Season 9 baseline: The Ebontharn announcement adds more than 600 nodes to the Incarnation Tree in Season 10.
  2. Season 10 expansion: Keep the addition attached to that season and avoid turning it into an unsupported claim about the exact present total or optimal path.
  3. Current interpretation: The scale of the addition warns that a Season 9 node overview cannot represent the complete Season 10 tree.

It does not reveal which branches received nodes or how those nodes should be valued for a build. Compare guide dates before following a path, then read current node text. Avoid calculating an exact total from separate announcements without confirmation.

A level-100 character is the intended subject of the Incarnation Tree answer. Below that point, the missing tree has a documented progression explanation. At that point, the Season 9 replacement history explains why older Hero Level instructions may no longer match. Season 10 then adds scale—more than 600 new nodes—without supplying node effects or an optimal route. These three observations solve access, naming, and guide-age questions respectively. They should not be collapsed into a build recommendation. When selecting nodes, inspect the current tree; when diagnosing an old guide, compare its system name and season with this timeline. A live level-100 character also separates an access question from a content question: absence below the threshold is explained by progression, while a different state at or above it calls for current-client observation. Once the tree is open, the Season 10 addition describes expansion but cannot select a branch for a particular build. Node wording in the present client must carry that later decision because the announcements provide no effects, costs, reset behavior, or comparative path support.

Before you rely on this guidelevel 100 and replacement of the old Hero Level tree come from the official Season 9 announcement; more than 600 added nodes comes from the official Season 10 Ebontharn announcement. Do not infer an exact present total, branch layout, optimal path, reset rule, or alternate unlock from those dated statements; inspect current node text in the live client.