Check what you are leaving behind
A roam starts with the bot wave. Has your wave actually reached the enemy turret, or can the opponent hold it outside turret range? Is the next wave moving toward your teammate, and can they collect it safely? A crash can create a window, but enemy waveclear and the next incoming wave affect how long it lasts.
Check your lane partner’s health, escape options, and the enemy bot lane’s ability to force a fight. A wave approaching your turret can be dangerous if your teammate is low and the opponents can dive. “They can farm under tower” is not enough of a plan. Leaving when your teammate is also recalling is different from leaving them exposed while they need help collecting.
Inspect the destination before taking the detour
Move your camera to the lane you want to visit. An enemy standing far forward is only part of the picture. Your ally may have no mana, be collecting a large wave, or lack a useful way to follow. Check whether the route is controlled and whether the enemy jungler could turn a small play into a losing fight.
Your purpose does not have to be a kill. You might cover an ally’s vulnerable moment, help your jungler move through a contested area, or place vision for a likely approach. Name the useful action before walking there. Spending time in river without a target or a return plan can cost bot lane pressure without creating anything elsewhere.
A good window can disappear while you travel
Imagine your bot wave reaches the enemy turret and your lane partner recalls. From base, you notice the opposing mid laner is extended and your own mid laner has resources to follow. A brief path toward mid may offer more than walking straight back bot. You ping your intention and check the lane again as you approach.
Now the enemy mid laner recalls before you arrive. The original gank has disappeared. You may still place a useful ward from a safe position or cover your ally’s push, but waiting indefinitely for another chance is a new decision. Compare it with returning bot before your teammate needs help on the next wave.
A roam can be well chosen and produce no kill. It can also produce a kill while imposing an avoidable cost on bot lane. Evaluate the information at departure, how the situation changed, and whether you stopped when the useful window ended. The scoreboard alone misses those distinctions.
Set the return condition in advance
Before leaving, identify what will require your presence again: a wave your teammate cannot approach, an enemy dive setup, or a planned bot play. That condition is more useful than a rigid roam timer. Reassess it when an opponent appears elsewhere or your teammate changes their own plan.
A recall route can create an opportunity to affect mid without a large detour, but it is not automatic permission to stay there. Account for travel back to bot and your own resources. Arriving at a second lane with no health or important cooldowns may create less value than returning to your lane ready to play.
Communicate the plan and review its cost
Use a clear movement ping and, when useful, a short message about what you intend to do. Teammates cannot reliably infer whether you are checking river, recalling, or committing to a roam. Their pings are additional information to inspect, rather than automatic proof that leaving or staying is correct.
After a game, review one roam from just before departure through your return. Note what happened to the bot wave, whether your destination could act, and when the opportunity changed. Choose one correction: check your ally’s mana before moving, verify the crash, or leave river as soon as the original target becomes unavailable. Better roaming often comes from ending a dead play promptly.