Dota 2 evasion and True Strike: price the attacks that connect

Evasion does not reduce every physical-looking threat and does not answer spell damage, control, or lack of movement by itself. Its value grows when the enemy can make many relevant attack attempts and each prevented connection removes meaningful damage, lifesteal, a proc, or another hit-based effect. It shrinks when attacks cannot reach you, spells decide the fight, or current accuracy makes avoidance unreliable.

Evaluation rule: count the attacks that matter, verify which can miss, price what a connected hit delivers, and name the action surviving enables.

1. Profile the threat. Separate attacks from spells and other damage, then identify attack rate, contact time, targets, hit effects, control, and who is actually killing you.
2. Verify the interaction. Read the current evasion, miss, blind, accuracy, True Strike, break, dispel, immunity, attack, item, and ability behavior for this matchup.
3. Combine only applicable checks. Do not add percentages or assume every source stacks; calculate only after confirming today’s combination rules.
4. Price the whole job. Compare avoidance with health, armor, reduction, movement, saves, control, damage, attributes, actives, cost, timing, and item slots.
5. Measure the result. Review relevant attacks attempted and connected, damage and effects per connection, contact time, resources spent, and the second action created.

Disarm, attack immunity, untargetability, displacement, attack range, movement, and fog can stop attacks without using the same probability check. Break may matter only when the relevant current effect is a breakable passive. A dispel may matter only when the relevant miss or blind is removable. Identify the actual layer before selecting a counter.

This is the probability model for independent avoidance checks: convert each applicable avoidance chance into its chance to fail, multiply those failures, then subtract from one. It explains why another source can add less displayed combined avoidance than its headline value. It is not permission to combine sources the current game treats as exclusive, replaced, suppressed, or governed by another rule.

The Attack Speed guide measures completed attacks and contact time. The Armor guide separates pre-mitigation attack damage from damage actually lost, and the Lifesteal guide helps price the sustain removed when an eligible attack does not connect.

Small samples are noisy. One fight can contain more or fewer misses than the displayed chance suggests. Judge the decision from threat share, current interaction, repeated attempts, and the action created—not from one lucky escape or one streak of connected attacks.

An enemy accuracy purchase does not automatically erase every stat, active, or utility effect on your item. It can, however, reduce the attack-avoidance part enough that another purchase would have created more reliable survival or output. Use the Item Builds guide to compare jobs and deadlines instead of following a hero table.

• Verify accuracy or True Strike. Read the current item, ability, talent, buff, proc, and target conditions and test whether the attacks that matter actually connect.
• Use non-attack damage or control. Spells, displacement, saves, disarms, kiting, and target isolation may solve the fight without asking the same attack check.
• Use break only when it applies. Confirm that the relevant avoidance is a current breakable passive and that break can be applied and maintained on the needed target.
• Change target order. Attack a reachable hero, force a save or active, remove another threat, or secure the objective when chasing the high-avoidance target breaks formation.
• Increase useful attempts carefully. More attack speed matters only when range, control, vision, survivability, and contact time let those attacks complete.

A dedicated accuracy purchase should earn its cost through attacks that would otherwise miss and through its other current effects. If the defender is already dying to spells, cannot reach the fight, or can be controlled through the required window, a different item may solve more of the actual outcome.

The Teamfight Positioning guide turns those threat and access changes into observable movement triggers.

1. Recreate the exact sources. Match hero level, ability state, talents, items, neutral items, buffs, debuffs, target type, and any conditional threshold.
2. Change one variable. Add or remove one avoidance, blind, accuracy, True Strike, break, dispel, immunity, or terrain condition per trial.
3. Run enough attacks. A short streak cannot validate a probability. Use repeated trials and record attempted, connected, and missed attacks.
4. Inspect the combat log. Separate misses, damage, attack effects, spell events, and target-state changes instead of relying only on animation or floating text.
5. Retest after patches. Keep the method and discard the frozen outcome when an official update changes an item, ability, status, or combat rule.

1. Choose one fight. Use a death, survival, missed kill, accuracy purchase, avoidance purchase, blind, break, or target-selection decision.
2. Count the relevant attempts. Record which attacks could reach, which connected, which missed, and which were never attempted because contact ended.
3. Price each connection. Note damage, effects, lifesteal, control, resource changes, and whether a different defense would have changed the same hit.
4. Check the whole job. Include every current stat and active, cost, timing, slot, enemy response, and the action the purchase enabled or delayed.
5. Write the next condition. Define the attack share, accuracy state, item job, second action, and observable enemy adaptation that would make you buy, delay, or skip it.