A turret bug that made the community frustrated without any actions from Riot Games

An infamous League of Legends bug has resurfaced, with players pleading with Riot to repair the turrets’ target-select, which can occasionally ignore opponents inside its range.

Image via Riot Games

Riot is continuously detecting and correcting bugs that constantly popping up in theirs 150+ Champions MOBA. However, the most vexing issues are occasionally caused by the Rift itself.

Turrets are your first and last line of defense against a potential gank or retreat if your health is low. This is especially important if the other team is planning to dive you behind the turret. However, there is a reported bug that can occasionally confuse a turret’s aiming mechanism, resulting in amusing footage of players being harassed beneath their tower with no assistance from the game.

The most recent incident occurred from user ‘Daki2117,’ who successfully maneuvered a 1v2 under their top outer turret – until the game determined it was time for him to die.

As Kayn and Darius begin their dive, the latter picks up turret aggro, making them the ideal target for a burst down. However, after killing Darius, the turret can be seen targeting a nearby cannon minion, giving Kayn plenty of time to complete the dive. As a result, the bug allowed Kayn to dodge at least four turret bolts, which would have been enough to kill him given that he was barely above 50% health.

League gamers believe Darius’ Hemorrhage passive was the culprit in this scenario. Because the bleed was actively harming the Aatrox, it’s assumed the turret was still “searching” for Darius but didn’t locate them and went on to the minion. The bug basically disregarded Kayn and denied the player the opportunity to die with a double-kill.

This has happened before to prominent League of Legends streamer Tyler1, as well as numerous other people who have reported similar experiences.

Credit: Koe

Time will tell whether Riot decides to work on a remedy, but League players have been aware of the bug and have been requesting a patch for some time.