Support Roam Creates Deadly Gank in Bot Lane
A well-timed support roam transforms bot lane into a lethal ambush zone by combining vision denial, wave manipulation, a…
Table of Contents
Why Support Roam Is the Bot Lane’s Hidden Kill Switch
In League of Legends, bot lane is often decided by the support’s ability to control space, vision, and engage timing. A support roam is not merely a random walk to mid; it is a hidden kill switch that can turn the bot lane into a deadly gank corridor. When the support leaves lane, the enemy bot duo must suddenly respect missing pressure. They may not know whether the support is warding dragon pit, helping mid, or waiting in the tribush with the jungler. That uncertainty is the first layer of the gank. If the support roams from base after a recall, they can arrive in bot lane from an unexpected angle, bypassing the river ward that the enemy placed earlier. If they roam from mid after helping their mid laner shove, they can path through the river and flank the enemy bot lane from behind. The deadliest version happens when the support and jungler move together: a 3v2 collapse on a lane that already lacks mobility or summoner spells. Champions like Nautilus, Leona, Thresh, Rakan, Alistar, and Rell excel at this because they bring chain crowd control and can lock down a target long enough for the ADC and jungler to delete them. Even enchanters can create deadly ganks by speeding up the jungler, shielding the dive, or using Glacial Augment to slow the enemy’s escape. The key is that the support’s roam changes the numbers and the angle of the fight. The enemy bot lane may think they are safe because they have a ward in the river, but a support roaming through lane bushes or from behind the tower can invalidate that vision. In short, a support roam is a threat multiplier: it turns a normal 2v2 lane into a 3v2 or 4v2 ambush, and it forces the enemy to play passively or die.
Setting Up the Roam: Wave States, Timers, and Vision Control
A deadly bot-lane gank does not start when the support enters the lane; it starts with the wave state several seconds earlier. If the wave is pushing toward your side, the enemy bot lane must step forward to farm, which exposes them to a flank from the river or tribush. If the wave is pushing toward the enemy side, they can hide under tower, making a gank much harder unless you are prepared to dive. Therefore, the best setup is usually a slow push that crashes into the enemy tower, then bounces back toward your side. As the wave returns, the enemy duo walks forward, and that is your kill window. Alternatively, you can freeze the wave just outside your tower range, forcing the enemy to overextend for CS. Timers matter just as much. The support should look for level 3, level 6, and cannon-wave timings. Level 6 is especially deadly because most bot-lane ultimates—Leona’s Solar Flare, Nautilus’ Depth Charge, Rakan’s The Quickness, or Thresh’s Box—can chain with the jungler’s ultimate. Vision control is the third pillar. Before the roam, the support should clear enemy wards in the river, tribush, and lane bushes. A control ward in the tribush or a pink ward in the river brush can deny the enemy’s only warning. Deep wards behind the enemy tower or near the enemy jungle camps can also track the enemy jungler and reveal whether a countergank is coming. If the support is roaming from base, they should path through the jungle, use blast cones, and avoid common ward spots. If they are roaming from mid, they should move through the river with the jungler, not through the lane, so the enemy does not see them on the minimap. Finally, the support must coordinate with the ADC: ping the wave state, ping the target, and communicate whether the goal is a kill, a summoner spell, or simply pressure. Without wave and vision setup, a roam becomes a wasted trip; with it, the bot lane becomes a death trap.

The Execution: Pathing, Ping Communication, and Chain Crowd Control
The execution of a deadly bot-lane gank depends on surprise, angle, and crowd-control sequencing. The support should approach from a path that cuts off the enemy’s escape. If the enemy bot lane is pushed up, the support can come from the tribush or from behind the enemy tower. If the enemy is near their tower, the support and jungler may need to dive from two different angles: one from the river and one from the lane brush. The worst thing a support can do is walk into lane in full vision and try to engage from the front; that gives the enemy time to back off. Instead, the support should wait in fog of war until the enemy commits to a last hit or uses a key cooldown. Ping communication is essential. Before the gank, the support should ping “On My Way,” target the enemy ADC or support, and ping their Flash, Heal, Barrier, Cleanse, or Morgana Black Shield. The jungler should know whether to engage first or follow up. In the fight itself, the support usually starts the chain because their CC is often more reliable or longer-ranged. For example, Nautilus can hook the ADC, Leona can E-Q-R, Thresh can Flash-Q-Flay, Rakan can W-R, or Alistar can W-Q combo. The jungler then adds damage and secondary CC, while the ADC follows with maximum DPS. The focus target should be the enemy who is more likely to escape or the one who provides the most damage. If the enemy support is a Soraka or Lulu, killing them first may remove healing and shields. If the enemy ADC is a Jinx or Aphelios, locking them down prevents them from kiting. Summoner spells should be tracked: if the enemy ADC has Flash, the support may need to Flash-CC to guarantee the kill. If the enemy support has Exhaust or Ignite, the engage must account for the damage reduction or healing cut. Finally, the gank should not overstay. Once the kill or summoner spell is secured, the support should help shove the wave, take plates, or rotate to dragon. A failed gank that lingers too long can give the enemy jungler a free countergank and throw away the bot-lane lead.
Turning Ganks into Objectives: Snowballing Bot Lane and Beyond
A successful support roam gank is only the beginning; the real value comes from converting the kill into objectives and map pressure. After the enemy bot lane dies, the support and ADC should push the wave into the tower and take plates. If the jungler is nearby, they can start Dragon or Rift Herald. The support should use this time to place deep wards in the enemy jungle, track the enemy jungler, and set up the next roam. If the bot-lane tower falls, the support can rotate mid with the ADC or join the jungler for a top-side play. This is how a single deadly gank becomes a snowball: the enemy bot lane loses CS, XP, and tower plates, while your team gains dragon control and vision. The support should also consider itemization to enhance future roams. Mobility boots, Swifties, or Boots of Swiftness help the support move between lanes faster. Items like Shurelya’s Battlesong, Redemption, or Locket of the Iron Solari can turn a 3v2 dive into a safe and devastating play. If the support is a playmaker like Pyke or Bard, they can use their roam to create pressure in multiple lanes at once. Bard’s tunnels and Pyke’s camouflage make bot-lane ganks especially terrifying because they can appear from unexpected angles. However, the support must also know when not to roam. If the ADC is a weak early-game scaler like Kog’Maw or Twitch, leaving them alone against a kill lane can result in them being zoned or killed. The support should communicate recalls, wave states, and jungle tracking so the ADC can play safely. If a gank fails, the support should reset rather than forcing another bad fight. The best supports treat roaming as a rhythm: push, ward, roam, gank, convert, repeat. When done correctly, the support becomes a second jungler, and the bot lane becomes a deadly gank corridor that the enemy cannot safely enter. The result is not just one kill; it is control over dragons, towers, and the entire bottom side of the map.
