World / 7 min read
SpiritVale Threat Guide: Party Aggro
The official 0.16 rebalance announcement introduced a documented threat system. Monsters target the player in range with the most threat, and the party screen shows relative threat. For a party, that turns 'aggro' from something you infer after a wipe into something you can read while the fight is still happening — provided you understand what generates threat in the first place.
The rule is positional as well as numerical
The announcement's wording matters: monsters target the player in range with the most threat. Both halves carry weight. The most threat decides who the monster wants, but in range decides who is eligible at all. That is why a ranged player can build threat safely and then become the target the moment they step inside the encounter's radius, and why the same player can appear to 'hold' aggro while standing at distance without actually holding anything. When a pull goes wrong, the first question is not who had the most threat — it is who was in range when the decision was made.
Four documented sources of threat
The announcement lists four ways threat is generated: dealing damage, casting a targeted skill, casting near aggressive monsters, and using a threat-generating skill such as Taunt. Read that list as a warning about accidental pulls as much as a guide to holding attention. Dealing damage and casting a targeted skill are deliberate — you know when you did them. Casting near aggressive monsters is not, which is why a support player standing close to a pack can accumulate threat simply by working, without targeting anything. And Taunt is the one item on the list that exists purely to generate threat, which is what makes it the tool for reclaiming a fight rather than contributing to it.
The party display is your instrument
Because the party screen shows relative threat, your job before changing anything about your build is to read it. Watch it during an encounter you already know well and in which nothing goes wrong. Note where your row sits relative to the tank's while you are doing your normal rotation. That baseline is far more useful than any abstract claim about how much threat a skill generates, because relative threat is measured in the encounter you are actually running, at your actual position, against your actual group. A number you read off a page cannot account for any of those three things.
Why tanking is now a coordination role
Before the system was documented, holding attention was a matter of doing enough damage quickly enough. The 0.16 note changes the shape of the job: a player who generates threat deliberately, positions so that the monster's in-range check lands on them, and communicates the pull is doing something a high-damage player cannot replicate by damage alone. That is also consistent with the patch's stated goal of promoting cooperative play. The practical consequence for the rest of the party is that restraint becomes a real mechanic — a damage player who opens before the tank establishes threat is not just being rude, they are changing who the monster targets.
The no-KS protection, and its limits
The 0.16 announcement also says Spawner Bosses receive a 60-second no-KS protection for the spawner and the party, cleared when the spawner leaves the map. The later 0.30.10 patch notes refine the surrounding rules: No-KS is cleared if a monster changes target, and it applies only once for five seconds. Those two statements describe different situations and should not be merged into one. The 0.16 text is about a spawner boss and a 60-second window tied to the spawner's presence; the 0.30.10 text describes a five-second, single-application rule that ends when the target changes. If you are trying to work out why a kill credited the way it did, check both patches against the encounter you were in rather than assuming one number covers every case.
Testing threat instead of guessing
Change one thing at a time. Run the same encounter twice with the same party and alter a single variable — the point at which damage begins, or which player initiates — and watch the party display rather than the damage meter. Write down the encounter, the patch version, the party composition and what the display did. Three or four of those records will tell you more about how threat behaves in your group than any general explanation, and they remain valid until a later patch changes the underlying rules. Keep the notes separate from your interpretation of them; a single wipe does not establish a hidden mechanic, and a display you misread once does not establish a rule.
Keep the patch label attached
Every claim on this page comes from a specific official note, and threat is exactly the kind of system a balance pass can retune by changing how much threat one action generates while leaving the structure intact. That would make the description above still accurate in shape and wrong in detail. The habit that protects you is the same one the rest of this site uses: attach the version to the observation, and recheck the original announcement before you change a build, a rotation or a party role on the strength of something you read without a date.
Frequently asked questions
How does SpiritVale decide which player a monster attacks?
The official 0.16 announcement says monsters target the player in range with the most threat.
What generates threat in SpiritVale?
The announcement lists dealing damage, casting a targeted skill, casting near aggressive monsters, and using a threat-generating skill such as Taunt.
Where can I see threat while fighting?
According to the official 0.16 announcement, the party screen shows relative threat.
What is the Spawner Boss no-KS protection?
The 0.16 note says Spawner Bosses receive a 60-second no-KS protection for the spawner and party, cleared when the spawner leaves the map. The 0.30.10 notes separately state No-KS clears if a monster changes target and applies once for five seconds.