Patch 7.0.12 gives Marksman players a reason to question familiar Vault setups rather than repeat the most popular Season 10 path. The key update is that Marksman Vault and its sub-nodes now carry the Projectile tag, with iArrow remaining the exception. For players comparing Hero Siege Items, this detail may also change which bonuses deserve priority during testing.

The update is not simply a damage increase written into the skill tree. It changes how the game classifies these abilities, which can influence modifier checks, support effects, and equipment choices. The best response is to treat the new tag as an invitation to test interactions carefully before spending every available skill point.

A New Classification for Vault Skills

A Projectile tag generally tells the game that an ability belongs to the same mechanical category as other projectile-based attacks. That may allow Marksman Vault skills to benefit from effects that previously ignored them, especially bonuses tied to projectile damage, speed, travel behavior, or repeated hits.

Players should still avoid assuming that every ranged modifier now works automatically. Some effects may check the main Vault skill, while others may inspect a specific sub-node or the final attack created by it. Since iArrow does not receive the tag, it should be evaluated separately instead of being grouped with the rest of the Vault package.



<table>
<tbody>
<tr>
<th>Build element</th>
<th>Question to investigate</th>
<th>Why it matters</th>
</tr>
<tr>
<td>Projectile damage</td>
<td>Does the bonus affect Vault directly?</td>
<td>It may improve core output without changing the rotation.</td>
</tr>
<tr>
<td>Projectile speed</td>
<td>Does travel time or hit timing change?</td>
<td>Faster contact can improve clearing and target pressure.</td>
</tr>
<tr>
<td>Penetration or pierce</td>
<td>Can Vault pass through additional targets?</td>
<td>This could alter positioning and pack-clearing value.</td>
</tr>
<tr>
<td>iArrow</td>
<td>Does it remain outside the new category?</td>
<td>Its investment may need a separate justification.</td>
</tr>
</tbody>
</table>


Interactions That Deserve a Controlled Test

Begin with simple comparisons. Record damage against one target, then repeat against a tightly grouped pack. Test the same skill points with and without projectile-focused equipment or passive bonuses. This helps separate the effect of the new classification from ordinary critical hits, enemy defenses, and random damage ranges.

Next, examine behavior rather than numbers alone. Watch projectile travel, target selection, penetration, area coverage, and any secondary effect that appears after contact. Useful checks include.

Whether projectile speed changes Vault's practical clearing rhythm.
Whether pierce or penetration affects every Vault sub-node equally.
Whether on-hit effects trigger once per cast or once per target.
Whether iArrow behaves differently when paired with the same support choices.

Rebuilding Around Evidence, Not Old Season Paths

Older Season 10 builds remain useful as starting points, but they should no longer be treated as final answers. A tree that once invested heavily in generic weapon damage may now gain more from projectile-focused support, while a defensive or mobility node could become preferable if the new interaction improves clear speed.

Respec in small steps instead of replacing the entire tree at once. Keep the original version as a baseline, move points into one new interaction, and compare results in the same area with similar gear. This approach reveals whether a bonus improves real gameplay or only looks attractive in a character panel.

Making the Patch Work in Everyday Play

For regular mapping, prioritize consistency: reliable travel behavior, strong coverage, and a rotation that does not leave Marksman Vault unavailable during dangerous moments. For boss encounters, single-target performance and repeatable hit timing may matter more than wide projectile coverage.

Patch 7.0.12 rewards curious Marksman players who test instead of copying. Recheck every Vault sub-node, keep iArrow under separate review, and let measured results guide the final tree. When your tests identify a missing upgrade, you can buy Hero Siege Items that support the proven version of your build, then continue refining it as the season develops.