Hero Siege 7.0.12 quietly changes how Marksman players should read the Vault tree. The new Projectile tag may look like a small label, but it gives several familiar nodes a fresh place in build planning, especially for players managing resources such as Hero Siege Gold while preparing a new character.

Marksman Vault and its sub-nodes now carry the Projectile tag, with iArrow excluded. That distinction matters because tags often decide which modifiers, support effects, and conditional bonuses can recognize a skill. Older guides remain useful for their general direction, yet their recommendations should no longer be treated as final answers.

Reading the Vault Tree Through the New Tag

The first question is not whether every Vault node suddenly becomes stronger. Instead, ask which systems identify Projectile skills and whether those systems affect the part of Vault that your character actually uses. A modifier that previously seemed relevant only to arrows, bolts, or other ranged attacks may now deserve testing with Vault.

iArrow should be treated as a separate case. Since it does not receive the new tag, its behavior may differ from the surrounding nodes. This makes mixed setups particularly interesting: one point path may connect skills that now qualify for the same effect while leaving iArrow outside that interaction.

Build element	What to check
Vault main skill	Projectile-only bonuses and hit-based effects
Vault sub-nodes	Whether each node inherits the expected behavior
iArrow	Separate scaling and conditional recognition

Interactions Worth Testing Before Spending Points

Start with modifiers that explicitly reference projectiles, ranged attacks, travel behavior, or repeated hits. Record the result with identical equipment, targets, and skill levels. This keeps the comparison useful and prevents a gear change from hiding the actual effect of the tag.

Next, examine effects that trigger on impact, critical hits, penetration, or projectile count. A tag may qualify Vault for an interaction without changing its basic animation or tooltip. The most valuable discoveries may therefore appear in combat results rather than in the skill menu.

Compare single-target and group performance.
Test Vault with and without projectile-focused modifiers.
Check whether iArrow follows the same rules or remains independent.
Measure resource cost and clear speed, not only peak damage.

Why Older Season 10 Builds Need a Fresh Review

Season 10 guides were written around an earlier understanding of Vault's classification. Their core ideas may still work, but point order, support choices, and equipment priorities could change when Projectile-based effects enter the calculation.

Rather than abandoning a proven setup, compare it with a revised version. Keep the same weapon and defensive gear, then move only the points connected to Vault and its supporting nodes. This reveals whether the patch improves the build itself or simply favors a different investment path.

A Practical Patch 7.0.12 Testing Routine

Create a short checklist before entering difficult content: note the skill level, modifiers, target type, critical rate, and average clear time. Run several repetitions for each version, since projectile travel and enemy positioning can create uneven results.

After testing, choose the tree that performs consistently across bosses and groups. The best response to 7.0.12 is not to copy a new recommendation immediately, but to understand why the Projectile tag changes your options and adjust the build around verified interactions.

Marksman players now have a reason to revisit Vault with a mechanics-first mindset. Careful comparisons can reveal useful upgrades without forcing a complete rebuild, and players who decide to buy Hero Siege Gold should still prioritize testing their chosen setup before committing resources.