Ahri’s minirework has brought a lot of bugs to LoL. The clone army is flooding Summoner’s Rift
Ahri’s latest update turned out to be heavily bugged. Some of the errors can be extremely dangerous.
As probably most fans of the heroine know – Ahri received a mini-work in patch 12.3. The creators wanted the character to be interesting and fun to play again. Many years have passed since her release, so the skill set is already old. Refreshed Ahri has kept her distinctive elements, but also got some small changes in skills and conversion factors. You can read about the rework here: Riot reveals Ahri’s rework that would make the character “fun to play” again
It didn’t take long for players to find some bugs with the revamped champion. These can be really absurd.
An army of clones and more
The new Ahri caused quite a stir among the League of Legends community. The heroine is really popular and has a lot of devoted fans, so it’s no wonder that players were looking forward to the update that introduced the announced rework to the live servers. It quickly turned out that it contained a lot of strange bugs.
The famous YouTuber Vandiril showed in one of his videos that the new Ahri can trigger a clone attack. What is it actually about? It turns out that Lissandra with her passive – Iceborn Subjugation – can create dozens of Ahri-shaped Frozen Thralls.
This is because, after the fox’s death, its ball remains on the map and generates new clones. Each ball left is an even greater number of Thralls.
This isn’t the only weird interaction with the revamped Ahri. The heroine also causes problems when Thresh or Senna are on the opposing team. As you know, both characters can collect souls. As in the previous case, a bugged fox’s orb remains on the map and becomes a soul generator if Senna or Thresh are nearby. It doesn’t take long for the opponents to gain unimaginable statistics, and thus – to become invincible.
Some players are surprised that such big errors have been transferred to the live servers. Usually, bugs are caught at the PBE stage. This time, however, it did not happen. Hopefully, Riot notices the problem quickly and does something about it.
