LoL preseason bug makes Lulu untargetable due to her Pix passive

The League of Legends preseason patch has finally hit the live servers but it unfortunately has brought some nasty bugs with it. 

Only a few hours after the big preseason patch was released, a game-breaking bug was discovered on Lulu. This bug makes Lulu untargetable and is seemingly triggered because of a bug in the code for her Pix. When the bug occurs, Pix will be the one targeted by tower shots, skill shots, auto attacks, and other forms of damage instead of Lulu. 

This bug is obviously very game-breaking and has already had an impact on several games reported in the League of Legends community. The bug won’t make Lulu unkillable, as she still takes damage AOE abilities. But it does prevent enemies from shutting down Lulu with skill shots though and can make Lulu tank towers and objectives for an infinite amount of time. 

Lulu is really broken right now…

Lulu bug causes game-breaking interactions with champions

In a video made by YouTuber Vandiril, one specific interaction is shown of the Lulu bug that might be explaining what is going on. A clip is showing how a Blitzcrank hits his hook on Lulu, but instead of catching Lulu he gets Pix and pulls it in. 

From the looks of it, the bug is making it so Lulu is no longer considered the target in the game; instead, Pix is. This makes up for the bug as Pix is only a part of Lulu and not something that can usually be damaged. Now that these bugs make Pix the target, there won’t be any way to deal damage to it or Lulu. 

Other clips also show how Lucian is using his ultimate on Lulu, but the shots never actually hit Lulu as Pix is there to absorb it all. The same goes for when opponents try to auto attack Lulu, where Pix is also there to absorb any incoming attacks. 

If players manage to kill a Lulu while this bug is activated, her corpse and Pix will be sitting on the map until she respawns. This has resulted in tower aggro being locked on Lulu’s corpse and minion waves getting stuck because of it. 

Since this bug is considered very game-breaking, it should only be a matter of time before Riot puts through a hotfix to get it solved.