The Invisible League Of Legends Attack Bug Riot Can't Seem To Resolve

The Invisible League Of Legends Attack Bug Riot Can't Seem To Resolve

Bugs and glitches are an unfortunate fact of life that usually just have to be tolerated when playing a game as hugely popular as League of Legends. The story of one such bug that's teetered between irritating and insufferable got a lot more interesting this week after a player figured out how to reproduce it.

The bug in question affects Nidalee, a popular champion who's already been a hot topic of debate amongst League players for a while since she's currently so powerful that people go back and forth incessantly about whether or not she's due for some sort of rework or nerf. One of the main things that makes her such a formidable (and therefore often irritating) character to go against in League is her special attack known as "Javelin Toss". As the name suggests, the attack involves Nidalee hurling her spear at an enemy.

While it can be dodged, the spear takes away a substantial chunk of a target's health bar if it isn't. The technical issue, commonly referred to as Nidalee's "invisible spear bug", renders her javelin, well, invisible right after she throws it using her special attack. If it's invisible, it's obviously much more difficult — if not impossible — to dodge.

Given how competitive the climate of League of Legends is, Nidalee's invisible spear bug has sparked calls from fans for Riot to disable the champion until the bug is resolved. She actually was suspended as a playable champion at one point late last year, but for a separate and unrelated technical issue. The invisible spear bug, on the other hand, has remained as one of those intermittent annoying-but-not-quite-game-breaking issues because it never seemed to appear often enough to warrant anything as drastic as pulling her out of the game.

This week, one player who goes by the handle "FLASHnFUSE" on YouTube posted on the League of Legends forums showing how he'd managed to reproduce the invisible spear bug twice in a row using a technique he'd come up with by repeated trial and error.

Here's the video of him showing it off:

And the explanation for how it was performed:

I reproduced this several times in an empty custom game (and a full of beginner bots custom game). I didn't record until I thought I could reproduce it easily and spent another 3 minutes until I reproduced the bug twice in a row.

What I did to do this bug: first thing I did was swap the attack move click to right click instead of shift-right click. Made things easier.

-I would mash right click (attack move click) and the "S" key (hold position) to try to get the wind up animation to just the right point

-throw a spear at the very end of a wind up animation, when the attack has technically "left" Nidalee.

-reissue the attack command

-the auto attack will connect with the minion (or tower, which tends to be easier to reproduce the bug at simply because of the longevity of a tower) and as the missile from the auto attack disappears, so will the nidalee spear.

The timing window for this bug is INCREDIBLY narrow, but the spear from Nidalee's Q disappears when the projectile from her auto attack hits a minion and disappears.

The times this bug successfully recreates, the spear from Nidalee's Q disappears as the auto attack damage is counted, but if you miss the timing on reproducing this bug you will not auto attack until well after you've thrown the spear. I think this bug's source is something to do with the client's disposal of projectiles.

Admirably (and adorably, if you ask me), FlashnFuse was clearly trying to highlight the bug and his discovery of replicating it to try and help Riot stamp it out of existence more definitively than they have so far. But the player's revelation has triggered anxiety that less well-intentioned players will start using the invisible spear bug to give themselves an unfair advantage in games now that someone has broadcast a relatively surefire method to activate it.


    Finding how to repro a bug is often the hardest part. Now that they know how, Riot can work on fixing it. And the fact that now everyone knows how to do it is going to make sure it's fixed fast.

      Yup. 'No repro, no fix' is the fucking bane of my existence in managing our systems.

Join the discussion!

Trending Stories Right Now