Dota 2 day and night cycle: read the transition, not just the clock

Night can reduce what some units see while improving or enabling other heroes and abilities. Day can expand some sight lines while exposing movement to the same enemy. Neither phase is automatically safe, aggressive, defensive, or favorable.

Transition rule: name the phase, the local visibility change, the capability it enables, the enemy’s answer, and the action that finishes before that answer.

1. Read the live phase. Check the clock, HUD, environment, game mode, and whether an ability or other effect is overriding the normal state.
2. Inspect local visibility. Include the current heroes, units, wards, structures, terrain, elevation, trees, smoke, reveals, and observed enemy information.
3. Verify special modifiers. Read current facets, innates, talents, abilities, items, neutral items, summons, and upgrades; test uncertain interactions.
4. Price the next transition. Name which route, lane, ward, formation, target, resource, objective, or exit changes when the phase changes.
5. Choose a proportional action. Move, farm, fight, defend, ward, smoke, pressure, trade, take an objective, or leave only when the response window supports it.

Many standard matches have followed alternating five-minute phases since 7.20, but the live match remains the authority. DotaSense does not read the Dota clock, detect day or night, identify forced-night abilities, or correct a reminder automatically.

• Phase: the global or overridden day/night state that current game systems can reference.
• Source: the hero, summon, ward, structure, ability, item, reveal, or allied unit providing information.
• Geometry: range, elevation, cliffs, trees, terrain, obstruction, facing, path, and whether sight is ground-based or otherwise special.
• Access: whether the unit can safely reach the square from which the source becomes useful.
• Interpretation: what remains unseen, how old the evidence is, and which enemy route or concealment can invalidate the picture.

A phase change can modify the information contest without changing every source equally. Use the Vision guide to frame the question, source, sight line, denial, movement, and replay evidence.

Do not replace an old hero or item table with another one. Record only the sources that matter to the next action, and route patch-sensitive values to current panels and tooltips.

1. Read the current hero page. Include base vision, facet, innate, talents, abilities, upgrades, duration, cooldown, movement, attack, cast, flight, and targeting behavior.
2. Separate natural and forced states. Test natural day, natural night, a temporary override, and the moment the override ends.
3. Test both teams’ information. Check what the caster, allies, enemies, wards, structures, summons, and affected units can actually see.
4. Test the counter-response. Add current vision sources, formation, saves, immunity, dispels, movement, teleports, detection, objective trades, and exits.

Dueling Fates changed Night Stalker’s day vision, while Shifting Snows changed how Darkness affected enemy vision and the day/night cycle. Those histories are why exact hero bonuses and forced-night behavior belong in the current client—not a permanent matchup chart.

The transition is a planning deadline, not a command to fight. If the setup is late or the response is already visible, preserve the next state instead of forcing the expired idea.

• Delivery: which team can see, reach, reveal, or control the target before being seen or answered?
• Formation: does reduced or altered visibility help the initiator, the counter-initiator, the back line, the split hero, or the team holding prepared ground?
• Second round: what happens after the first reveal, spell, save, ward loss, phase override, or retreat path is used?
• Movement: which path remains safe if the enemy is already in the unseen area, and what observable evidence would change the route?
• Exit: can the team disengage before the phase, temporary effect, vision source, or numerical advantage expires?

Night does not guarantee a gank, and day does not guarantee a safe push. The useful question is which team can convert current information into a completed action before the other team’s response arrives.

Use the Objectives guide for the full finish-before-response framework. Phase is one input to the response calculation, not a universal Roshan or tower instruction.

1. Name the decision. Farm this lane, cross this entrance, hold this high ground, contest this objective, protect this ward, or escape through this route.
2. Name the unseen threat. Initiation, wraparound, teleport, ward, summon, projectile, split pressure, steal, or a hero whose current phase interaction changes access.
3. Choose the source and square. Use the current hero, unit, ward, structure, ability, item, high ground, or moving teammate that answers the question safely.
4. Plan source loss. Decide what the team does when the phase changes, the ward dies, the unit leaves, trees fall, an override starts, or the enemy denies the area.

More nominal vision is not automatically better information. The source must answer the right question from a square the team can defend or use.

1. Choose one transition. Record the live phase, clock, temporary effects, heroes, lanes, vision sources, resources, target, objective, and exits.
2. Write the intended advantage. Name the local visibility or capability change—not merely “it became night” or “it became day.”
3. Review first contact. Who saw whom, from which source and square, and which hidden route, ward, unit, spell, or response changed the plan?
4. Price conversion. Measure the lane, farm, ward, spell, item, health, time, position, objective, and exit gained or lost.
5. Write a narrower rule. Tie the next attempt to observable phase, local information, setup, response, and exit conditions.