Dota 2 Glyph of Fortification: make the delay create a defense

A glowing building is not the outcome. The resource succeeds only if its temporary protection changes a lane, arrival, wave, fight, objective, trade, or Ancient defense enough to improve the next state.

1. Loss: What exact building, wave, lane access, objective, or game-ending threat disappears if nobody acts?
2. Response: What hero, spell, teleport, buyback, wave clear, pressure, or trade becomes useful because time was bought?
3. Aftermath: When protection ends, do we fight, clear, trade, reset, concede, or leave?

Activation rule: do not spend a shared defensive resource merely to watch the same loss happen a few moments later.

Track status before the building is one attack from falling. A team deciding during the final hit is already choosing from a smaller set of responses.

“Save tower” is incomplete. “Keep this teleport destination alive until two defenders connect,” or “delay their barracks hit until our wave reaches the Ancient,” tells the team what the button is buying.

1. Locate the defenders. Count travel, teleport availability, channel safety, buyback, and the position where each hero actually arrives.
2. Check useful resources. Arrival without health, mana, wave clear, saves, initiation, damage, vision, or an exit may not be a defense.
3. Read enemy commitment. Separate a small poke from heroes, summons, waves, ultimates, and positioning that cannot leave cheaply.
4. Name the first action. Clear the wave, save the structure, kill one exposed hero, force retreat, protect the Ancient, or complete the cross-map trade.
5. Set the abort condition. If the defender, spell, wave, vision, or trade no longer connects, stop feeding resources into the original plan.

A response must become useful before the enemy’s next uncontested action. “They can teleport” is not enough if the landing point is covered, the necessary spell is unavailable, or the wave cannot be cleared.

Fortification has affected lane creeps in parts of Dota’s patch history, but current behavior belongs to the live client. If the present patch protects a wave, judge that wave by the map action it enables.

Valve has changed tower-loss refresh behavior before. Read the current rule and team UI, then treat a possible refresh as a branch—not as permission to spend automatically.

Refresh rule: two poorly defined activations are not better than one activation with a response.

1. Expect the resource. Check visible team status and recent use rather than treating a damaged building as guaranteed.
2. Preserve contact. Keep heroes, wave, summons, vision, and key cooldowns in a state that can act after protection ends.
3. Use the delay. Reposition, clear defenders’ vision, control arrival points, hit another valid target, reset aggro, or stop spending vulnerable resources.
4. Read the counter-initiation. The defensive team may be buying an arrival, not merely structure health. Prepare for the hero and spell that the delay enables.
5. Recalculate. After the effect, compare finish time, enemy response, buybacks, wave state, resources, and exit. Do not continue because the original call was “push.”

Do not rank melee barracks, ranged barracks, towers, or the Ancient with a universal script. The correct priority depends on current health, lane pressure, exposed Ancient paths, enemy finish tools, your response, and the next objective.

• Status: “Glyph ready; hold it for their wave under bottom barracks.”
• Arrival: “Glyph now; two teleporting; clear wave first.”
• Commitment: “Wait for their carry to cross; then Glyph and jump the backline.”
• Trade: “Glyph the base; finish top tower; teleport out after.”
• Abort: “No defender can arrive; keep Glyph and clear the next lane.”
• After: “Protection ending; stop chase; reset behind tier fours.”

Use the Communication guide to keep team-resource calls observable, brief, and tied to the next action.

Use history to understand why a rule exists, not as proof that it still works the same way. For today’s match, use the live client and current official updates.

1. Choose one activation or non-activation. Start before the enemy wave or heroes reach meaningful structure contact.
2. Freeze before the decision. Record current Glyph status, threatened loss, waves, structures, visible and missing heroes, teleports, buybacks, resources, cooldowns, vision, and cross-map pressure.
3. Name two branches. Compare activating now with holding it, conceding, clearing another wave, trading elsewhere, or waiting for deeper commitment.
4. Write the intended job. Arrival, clear, commitment, trade, preservation, or Ancient survival.
5. Follow the aftermath. Record the first useful action after protection and the first avoidable loss after that action ended.
6. Create one trigger. Examples: “Name who arrives before Glyph,” “clear wave before chasing,” or “verify refresh before budgeting it.”