Rescue Timing Ladder
At-a-Glance
- Category: Hook-State Systems
- Objective: Decide who rescues and when based on route quality and objective tempo.
Setup Protocol
- Define default roles before first queue pop.
- Agree on one fallback rule when the opener fails.
- Assign one player to macro oversight every match.
Decision Rules
- If two players are pressured, assign one stabilizer and one objective continuer immediately.
- If rescue route quality is poor, delay and reposition instead of panic trading.
- If killer overcommits one lane, convert opposite-side objective value immediately.
- If team resources drop faster than expected, simplify into safety-first macro for one hook cycle.
- If information is uncertain, make low-risk calls that preserve optionality.
- If lead player is downed, transfer macro call role instantly.
- If endgame is imminent, assign gate roles before final gen pops.
- If solo-like drift appears, reset plan to two-player micro units.
Common Mistakes
- Everyone trying to be primary caller at once.
- Swapping plans every 10 seconds with no clear trigger.
- Over-trading hooks because team did not assign rescue owner.
- Full-team heal pauses that kill objective tempo.
- No contingency when first chase goes bad.
- Ignoring map-side strong/weak lane updates after resource trades.
Role Examples
- lead: calls macro pivots and tracks hook-state tempo
- runner: takes high-risk lane checks and first-contact kites
- anchor: holds objective stability and safe rescue lanes
- support: manages reset windows and emergency body routes
Quick Checklist
- Roles assigned in loading screen.
- First 90-second plan confirmed.
- Rescue ownership clear each hook state.
- Objective split/stack call explicit.
- Fallback rule active when tempo breaks.
- Endgame role assignment done before collapse.