Dota 2 split push guide: force a response without donating a hero

Lane damage is only the visible part. A wave that forces one defender may open Roshan, a ward line, farm, a favorable join, or a structure elsewhere. The same wave is losing when teammates die during the reveal, the responder arrives unseen, the building is protected, or the split pusher has no productive move after leaving.

Split-push rule: choose the wave, name the response you want, protect the map your team must hold, leave on observable evidence, and convert the new enemy positions.

1. Name the job. Fix a wave, force a defender, expose a response, threaten a structure, delay a push, create farm, or open another objective.
2. Read the live wave. Count useful survivors, reinforcement, travel, tower contact, protection state, and the time before the threat becomes visible.
3. Bound the response. List shown enemies, missing enemies, legal movement, likely arrival paths, catch tools, and the evidence that ends your window.
4. Protect team and exit. Define what four heroes can safely hold, your first escape, backup route, join option, and stop line.
5. Convert the movement. Leave, re-show, join, ward, farm, take another lane, defend, or start an objective as soon as the response changes the map.

Use the Creep Equilibrium guide to forecast survivors rather than assuming that every cleared wave reaches a structure. Show as late as the job allows: sometimes the threat is the hero, sometimes a spell or controlled unit, and sometimes the unseen possibility of joining the team.

Use the Towers guide for the contact-finish-exit decision and the Barracks guide for high-ground lane consequences. The durable question is not “can this build rat?” It is “what live access exists, what finishes before the response, and what remains afterward?”

Observed movement is evidence, not a guaranteed cooldown lock. Inventory, Boots, map targets, gates, abilities, buyback, death, cancellation, and allies can change the next arrival. Pair this with the Teleport guide and preserve an uncertainty margin.

• Give them a playable boundary. Name the tower, wave, high ground, vision line, spell range, or objective edge they can hold without crossing to prove the split works.
• Preserve wave clear and exits. Identify who clears, who provides information, who stops initiation, and which route or teleport target remains if the enemy continues.
• Respect the missing fifth body. Your team may lose initiation, save, damage, vision, auras, control, buyback threat, or a specific matchup while you are away.
• Set the abandon condition. If allies must spend critical resources, lose the escape route, reveal too many heroes, or face an immediate Ancient threat, the split job may be over.

“Four versus five” is not a complete state. Four heroes can delay a narrow lane with vision and ready wave clear, or collapse instantly in open ground without saves. Price their actual geometry, resources, information, and retreat before showing.

1. Hide or step away. The cheapest exit preserves the wave threat while breaking target access and making the responder prove where they went.
2. Use local terrain. Plan trees, ramps, fog, high ground, juke paths, allied vision, neutral areas, gates, and paths that do not converge on the expected catch route.
3. Spend mobility or protection. Verify the current ability or item, its cast conditions, interruption, damage lockout, dispels, detection, target legality, and where it actually leaves you.
4. Teleport or join. Prepare the target, arrival square, channel safety, team formation, and first useful action rather than treating any completed teleport as success.
5. Trade the hero only deliberately. Include death time, buyback state, enemy resources gained, wave loss, objective access, and whether the team can convert more than the opponent.

An escape tool is not an exit plan by itself. It may be used for wave access, disabled by live conditions, countered by vision or control, or lead into a second responder. Keep one branch for the expected catch and another for the answer that removes the first.

Test the current hero, facet, innate, talent, ability, item, controlled unit, and building interaction in the client. Buy for the missing job—wave access, movement, survivability, information, structure contact, join speed, or conversion—not because an old guide labels one item “core.”

The response is often the reward. Greeding for visible building damage can turn a won map exchange into a death. Recount both teams as soon as the defender appears: which heroes are now isolated, what objective is under-defended, and who can arrive next?

• Current loss: identify the exact wave, tower, barracks, Ancient access, hero, buyback, Glyph, or objective the enemy can finish if nobody returns.
• Your finish: measure real wave arrival, protection state, damage, enemy defense, Glyph, teleport targets, and time to the next durable structure—not nominal hero damage.
• Return branch: verify who can return, where they land, what interrupts them, which spells or items remain, and whether arrival comes before the decisive contact.
• Aftermath: compare surviving heroes, lanes, buybacks, structures, Roshan access, map control, resources, and which team gets the next uncontested action.

A lower-tier-for-higher-tier slogan is not a base-race model. Structures, waves, protection, Glyph, heroes, controlled units, teleports, damage, repair or healing interactions, and Ancient access change the finish order. If the evidence is incomplete, choose the branch that preserves more ways to stop a decisive loss.

1. Pause before the reveal. Record all waves, structures, protection, vision, shown and missing heroes, team resources, teleports, movement, buybacks, and objectives.
2. Write the split job. State which response the wave should force and what your team is supposed to gain from it.
3. Mark team and exit boundaries. Name where allies can safely hold, the first escape, backup route, join option, and the exact stop evidence.
4. Trace the first response. Note when an enemy begins moving, when you could know, when you leave, and what both teams do next.
5. Price the entire exchange. Include waves, farm, damage, structures, deaths, buybacks, vision, objectives, time, information, and the next uncontested action.
6. Write one narrower trigger. Tie the next split to observable wave quality, structure access, team safety, response evidence, conversion, and exit.