Storm Spirit in 7.41f: decide when to farm and when to gank

Storm Spirit can reach a side-lane fight quickly and still make the wrong move. Judge a rotation by its expected reward, the resources it consumes and what you can do afterward. A kill that leaves you stranded without mana may not solve your team’s problem.

Before a gank, answer four questions

1. Who is the target? Pick a reachable enemy. Check their escape and any nearby ally who can save them.

2. Who helps? An allied stun is useful only if its owner is close enough and ready. A ping alone is not a coordinated attack.

3. What does the whole play cost? Budget for the approach, your spell sequence and a retreat. Ball Lightning costs mana both to activate and over distance. A fixed mana percentage cannot make every jump safe.

4. What comes next? Name the reward and your return route: protect a tower, take an objective with allies, or return to a safe wave. Know what you will miss in mid.

When the answers are weak, connect safe resources

Start with a wave you can safely collect, then choose a nearby camp that fits before your next useful lane visit. “Wave → camp → reassess” is a decision loop, not an order to farm the same area regardless of enemy movement.

Imagine you clear mid, see the enemy mid elsewhere and can reach a nearby camp without entering unwarded enemy territory. You have a short route to consider. If two threatening heroes then disappear, recheck the route instead of following your original plan automatically.

Stack only when you or a teammate can realistically collect the stack. Walking a long detour to stack while a safe wave dies is not automatically efficient.

Read this farming moment

The excerpt shows Storm using damage and attacks to clear neutral creeps, then moving on. The freeze-frame highlights 1, the nearby camp; 2, his remaining mana; and 3, the minimap. It illustrates what to inspect before choosing the next stop, rather than proving the entire route is safe.

After a camp, ask: “Where is the next safe wave, and can I reach it with enough resources to leave?” If the answer is unclear, reset or choose a safer resource. Do not spend your escape mana simply to move a few steps faster while enemies are missing.

Compare two possible rotations

Worth evaluating: an enemy dives your side-lane tower, your support has a ready disable, your teleport is available and you can afford both the fight and the exit. Check that help can actually arrive before committing.

Low confidence: a healthy enemy is near their own tower, your ally is retreating and you would need a long jump just to reach them. Unless new information changes the situation, finish the next safe action instead of spending time on a hope.

Neither example guarantees an outcome. They make the information you need explicit, so you can explain your decision after the game.

Stop when the advantage ends

After a kill, check mana, enemy positions and defensive cooldowns again. The second target is a new decision. State one next action to the team, then do it. If your defensive item is on cooldown, do not plan the next jump as though its active protection were available.

A five-minute replay exercise

Review minutes 6–11. For every departure from mid, write one line: intended reward, waves missed, mana spent, result and next action. Include successful ganks. Find one repeated cost you could avoid, such as waiting too long for a target or returning without a plan. Practise that correction for three matches instead of chasing a universal creep-score target.

Patch context and sources

The clip is from justhatemeee’s August 3 Storm guide, 09:04–09:12, recorded on 7.41e. Annotations, examples and exercises are by DotaPractice. Storm has no direct hero changes in 7.41f; item and matchup changes still matter. Use this lesson for decisions, not a copied build. Mana mechanics were checked against Valve’s ability data on October 6, 2026.

Storm Spirit · 7.41f