Dota 2 creep equilibrium: control where the next wave meets

The lane moves because one side preserves more creep health or reaches the next exchange earlier. A visually centered wave can already be pushing. A wave near your tower can move away after tower damage. A pull can drag allied creeps out of lane yet create enemy survivors that later crash into the tower.

Equilibrium rule: count the live wave, forecast which creeps survive, name the lane job, choose the smallest intervention, and inspect where the next two waves are likely to meet.

1. Read the wave. Count unit types, health, targets, positions, reinforcement, tower contact, hero damage, and outside interference.
2. Forecast survivors. Estimate which side keeps more useful health and damage when the current exchange ends.
3. Name the lane job. Choose safe access, denied access, pull, freeze, crash, pressure, reset, rotation, gank setup, or exit.
4. Intervene once. Use last-hit timing, deny, aggro, block, tank, spell, pull, cut, or restraint in service of that job.
5. Recount the next state. Check the new survivors, meeting point, camps, heroes, resources, tower, and missing responses before acting again.

Add hero attacks, spells, denies, tower shots, tanking, aggro, pull departures, returning creeps, summons, and missing enemies. “Do not touch the wave” is not neutral if the current survivor advantage already sends it toward a bad state.

Verify the live attack-order trigger, acquisition range, duration, cooldown, target selection, vision, de-aggro options, and hero-specific interaction. Valve’s 6.87 update changed lane-creep aggro duration and cooldown; 7.06 changed them again. A memorized number is not a durable aggro model.

1. Verify the current rule. Read deny eligibility, thresholds, damage, bounty, XP, hero-deny or special-unit behavior, and mode differences in the client.
2. Price the contest. Include the enemy last hit, your deny, harassment, spell resources, positioning, creep damage, and the next available last hit.
3. Price survivor impact. A deny removes allied health and damage from the wave; that can pull equilibrium back, accelerate an enemy crash, or remove protection.
4. Price access. The highest apparent bounty is not automatically the best contest if it costs health, mana, another creep, tower safety, a pull, or the next wave.

Valve’s 7.00 gameplay update, 7.06, and Dueling Fates changed how player and neutral denies distribute experience and how waves are composed. Use the current lane values; keep the durable idea that a deny changes both resources and wave damage.

• Name the desired first meeting point. Include lane matchup, tower edge, high ground, rune or camp access, harassment space, and which hero needs the safer first wave.
• Read both blocks. Your block interacts with the opponent’s block, unit collision, spawn path, terrain, movement, summons, and lane-specific geometry.
• Preserve formation. A broken or split allied wave can focus one creep, expose the ranged unit, change tower contact, or create a worse survivor pattern than a lighter block.
• Stop when the job is met. More delay is not inherently better. Reassess as soon as the opposing wave and first contact become visible.

Practice the current map and hero in a lobby. Do not copy a universal path, stop-key rhythm, or promised number of seconds across lanes, sides, patches, body sizes, movement states, and game modes.

A familiar clock cue is a preparation prompt, not a universal pull second. Calibrate each side and camp in the current map, then adjust for wave blocks, movement, day/night aggro, changed spawn boxes, missing trees, summons, and contested paths. New Frontiers materially changed lane and jungle geometry; live route evidence owns the timing.

There is no universal creep-count formula for a freeze or “double wave.” Count useful survivors and reinforcement, then include tower damage, heroes, spells, pulls, camps, and the response that begins when the wave becomes visible.

• Tower contact: inspect current targeting, damage, attack rhythm, armor or aura interactions, Glyph, backdoor state, denies, and how quickly it changes survivor health.
• Safety edge: judge enemy reach, high ground, trees, vision, creep cover, dive support, teleports, and the route each hero uses to contest a last hit.
• Farmability: a wave under tower may be safer from heroes but harder to last-hit, easier to dive, or more likely to rebound outward with allied survivors.
• Escape: preserve the path, spell, item, teleport, support position, or turn opportunity needed if the opponent crosses the wave.

“Just outside tower range” is a goal only when that exact position is useful and maintainable. Use the Towers guide to price live structure contact instead of relying on frozen ranges or shot counts.

The lane job belongs to the lineup and map state, not a permanent role. A support may hold a wave, a core may pull, a mid may leave equilibrium neutral, or an offlaner may crash instead of freeze when those actions create the best next state.

1. Identify why it broke. Count extra survivors, failed denies, tower damage, spell use, hero tanking, block difference, pull outcome, death, rotation, or missed reinforcement.
2. Choose the next safe state. The goal may be a clean tower last hit, full crash, pull, cut, trade, abandoned wave, protected stack, or rotation—not restoration of the previous coordinate.
3. Use the smallest correction. One aggro pull, deny, spell, tanked hit, camp pull, fast clear, or restraint can be better than repeatedly fighting the wave.
4. Protect the correction. Account for enemy access, missing heroes, dive resources, camp contest, teleports, tower contact, and where you stand after intervening.

1. Pause before one intervention. Choose a deny, aggro order, block, pull, spell, clear, tank, cut, or decision to leave the wave alone.
2. Record the live state. Count bodies, useful health, targets, reinforcement, tower contact, heroes, resources, camp state, and missing enemies.
3. Write the lane job. State the desired access, denial, pull, freeze, crash, pressure, rotation, gank setup, reset, or exit.
4. Forecast and compare. Predict survivors and the next two meeting points, then compare them with what actually happened.
5. Write one narrower rule. Tie the next action to observable wave, camp, tower, matchup, resource, map, and response evidence.