Riot Games has implemented a global damage bug hotfix for Poppy, Kayn, and other champions, revealed today by League of Legends lead gameplay designer Mark “Scruffy” Yetter.
The fix is designed to remove multiple game-breaking exploits where Poppy, Kayn and other champs could use specific spells to strike all enemy champions without even seeing them.
The exploit had put a grinding halt to League’s competitive experience earlier this month. Many players have struggled to enter a game over the past couple of weeks without cheaters ruining the game for everyone. In certain cases, those taking advantage of the bug racked up hundreds of kills without even leaving spawn.
There is no need to queue for ranked games if there is a clear and present risk that you will lose miserably only because another player is abusing a bug that Riot has known about and has been struggling with for more than a year now.
New Poppy’s bug that gets 300 kills per match!
The bug first appeared in March 2019, but only Kayn’s W ability, Reaping Slash, was affected. Those who exploited the bug were able to use Reaping Slash to hit the entire enemy team and jungle monsters, which ruined the game completely. The error resulted in Kayn being temporarily removed in 2019, before Riot issued a fix. The bug came out again in May 2020 after the patch, forcing Riot to disable Kayn once again and release another update.
Kayn suddenly has been locked on all servers around the world due to a “crazy” bug
The bug emerges for the third time in mid-June. But this time also included Poppy and other champions in the exploit. Poppy, Kayn, and other champs could carry out global attacks from the fountain, or elsewhere on the map, while using the spell exploit.
These bugs, though, did not just ruin people’s games. The exploits have also, in many cases, led to permanent bans on players who have been killed over and over. Several League players have reportedly received account bans for deliberate feeding after being repeatedly killed by the bug.
Yetter claims that today’s fix should completely remove the issue once and for all. But the bug has reappeared multiple times now, so it’s hard to assume that the issue is completely fixed until Riot releases more information about why the exploit happened in the first place.
You must log in to post a comment.