Boards›Report a Bug

This is how I successfully reproduced the Nidalee spear bug (twice in a row! with VIDEO)

FlashnFuse··113 votes·10,677 views

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.

EDIT: To reiterate, I used these steps to reproduce the bug several times before actually filming it. It is just extremely hard to hit the timing window to do it.

EDIT 2: as pointed out by BlackSunNocturne, it may also have something to do with one small fact: Nidalee's Q and Auto-Attack spears use the same model. It may be a bug with the coding the model. If one disappears, the other one disappears as well.

72 Comments

Deep Terror Nami24 votes

Good work, this might be a lot of help for them to fix it (since reproducing the issue is key in fixing a bug). But Riot doesn't like you to explain how to do an exploit on the forums, because it exposes people to it that wouldn't otherwise know how to do it. You can use a support ticket, or edit the specific info out of your post (Riot can read prior edits).

FlashnFuse10 votes

Honestly this bug is so difficult to reproduce that I'm not to worried people will be able to exploit it (I'm lucky that I got it twice in a row XD) but If a red tells me to get rid of the steps I will :)

Deep Terror Nami5 votes

I went into a custom 1v0 and practiced. It took me a few minutes but I can now do it 100% of the time. It is not hard, and there are jerks who will use your post to ruin games.

Disclaimer: I will never use this in a game with another player. Just saying it was easy to learn.

FlashnFuse2 votes

I stand corrected. Honestly, I'm happy that someone can reproduce the bug with my steps (i was afraid it was a bit too much rambling). Still though, I'll leave this to a Red's discretion.

GaleWinUnleashed3 votes

If you're capable of reproducing it so consistently, then it'll be that much easier for Riot to find the source of the bug and fix it quickly. Slight trade-off until then is possible exploiters, but I don't believe it will be that big of an issue.

Deep Terror Nami3 votes

The point is that he could have brought this to their attention in detail, without exposing the bug to the public... Zero collateral damage is preferable, and easily attained.

Saixos11 votes

Or alternatively, now that it's brought to public eye, there will be even more pressure on riot to fix the bug.

Deep Terror Nami2 votes

Do you honestly think people didn't know about this? It has been a daily report. I am not saying this report is not doing a lot of good; I am saying that he could have omitted the part (to everyone but Riot) that walked the public through how to use the exploit.

Retillin1 votes

Riot tends to move a bit quicker when something happens a LOT. Take the BotRK exploit, it was talked about for months and months. But once it was explained on Reddit, it got fixed in about 2 patches.

Major Sparkles3 votes

Riot has pretty much said that they're OK with bugs being reported this way because it expedites the process.

Pastramka1 votes

U did a great job!

They have a new info in the bug, if they thought that this info will influence the game in intolerable way, they would have removed ur post and explain why they did it. So don't worry.

Riot where is his PBE account now!?

GIVE HIM PBE ACCESS ASAP! :D

FlashnFuse2 votes

I actually have PBE access already XD. (Or I think i do... its been a while since I tried to access it...)

Pastramka1 votes

:D GJ aniway.

Major Sparkles1 votes

The same bug happens with Mundo's cleavers. Except that with Mundo it's so easy a caveman could do it.

BlackSunNocturne12 votes

You just solved the invisible Q spear problem. And by posting a "how to" for it, you also inadvertently made it easier for people to do it, therefor making the invisible spears happen more, which will cause people to bitch about it more, and would cause it to get fixed!

Also, it may also have something to do with one small fact: I was discussing this with a few of my friends who do coding and shit, and Nidalee's Q and Auto-Attack spears use the same model. It may be a bug with the coding the model. If one disappears, the other one disappears as well.

FlashnFuse4 votes

I'm adding that observation to the main post :)

ShadowAlkx1 votes

That would mean thus would apply to all abilities that have the same models as the aa animation. Invisible double up, invisible cleavers, invisible spears. (Maybe teemo blind and invisible vayne condemn too maybe.)

Sir Choingler6 votes

This is really cool! Thanks for putting in the work to figure this out. I don't know if this is the exact same bug everyone is complaining about regarding invisible spears since that bug seems to not be dependent on her auto attacks, but this is definitely a step in the right direction towards fixing the problem.

FlashnFuse2 votes

Thanks! As far as I can tell there is another issue that happens to all projectiles from fog of war sources (especially nid spears and morgana bindings). But I noticed this bug was "easy" to reproduce just by looking at some other youtube videos. I only hope it helps rito find the source of this annoying (and high damage) bug.

junglerboy165 votes

I think the fact that this is no longer an "it happens randomly out of player control" bug, but is now proven to at least be semi-exploitable (in that you can recreate it relatively well with practice without any special circumstances), Riot will have to look at this, since there is now a known way to take advantage of it (even if it is very unreliable).

GaleWinUnleashed2 votes

It's more like this video will greatly help Riot narrow down the source of the bug, which has apparently been a pretty serious roadblock in fixing it. Give Riot some credit, they're not just ignoring it because it was "random".

junglerboy161 votes

I never said that, I was just saying that while it was difficult to single out and seemingly rare enough to not warrant further exploration before, this video has given both a way to track it down and remove it as well as a pressing need to do so (at least, more so than "occasionally it is invisible").

GaleWinUnleashed2 votes

Wooo, extra motivation for Riot!

Though in all seriousness, I believe the slightly increased potential for exploitation is more than balanced out by finally having a solid way to reproduce this elusive bug.

FlashnFuse1 votes

I'm hopeful that more good will come of this than bad. I love Nidalee, but I hate dodging a skill shot I can't see.

Nucleophilic atk5 votes

Riot knows she is bugged. They chose not to fix her cuz they like her.

FlashnFuse7 votes

No, its annoying and difficult as hell to reproduce it. I managed to successfully reproduce it enough times that I think I can at least help them find the timing where it occurs which will give them a good direction to fix it.

Nucleophilic atk1 votes

Yes, you have given them significant help. My point, however, is that they don't care lol.

I'll put it this way. If Nid had a bug where her spears did no damage, they would completly shut down the servers. Since Nid has a bug that allows her to throw invisa spears, thus making her better, they don't even disable her.

junglerboy168 votes

They actually do care, they just keep thinking they've fixed it (they've said as much in 3 separate sets of patch notes that I can think of), like they used to think the kept fixing the Shen ult bug, but never could fully figure it out until about 4-5 months ago.

Knowing a persistent way to reproduce it (even if it isn't the only way to reproduce it) gives Riot a TON of information on what kind of bug it might be and where they should look to fix it.

Nucleophilic atk2 votes

Again, if it were making Nid WORSE, they would disable her or the servers. Since it is making her better, they will take their jolly ole time, not caring the people that it screws over :D

qetzel2 votes

Do you have any evidence to back this up? The only time they disable champions is if they have a truly gamebreaking bug, for example Maokai remaining untargetabe after his W or Pantheon going invisible when he uses his ultimate.

Nucleophilic atk1 votes

Hey all,

We're currently aware of a bug where cone targeted abilities (e.g.: Annie's Incinerate, Nidalee's Swipe, Kassadin's Force Pulse, etc) are reversing their direction when cast immediately after using another ability (e.g.: the Flash Summoner Spell, Nidalee's Pounce, Kassadin's Rift Walk).

Champions who rely on cone targeted spells to finish their combos are most impacted by this, like: Nidalee, Kassadin, Pantheon, Annie (Flash + W), Darius (Flash + E), Singed (Flash + E), Riven (2nd cast of R), among others. http://forums.euw.leagueoflegends.com/board/showthread.php?p=17530731 .

Network Operations – Last Thursday at 01:35 While we are aware of the bug involving cone spells being mis-aimed when used immediately after a different ability, there are two champions more severely affected than others: Nidalee and Kassadin. Due to the highly negative impact (and frequency of occurrence) of this bug on these champion's core gameplay patterns, we decided it would be better to disable both as we work on a fix. http://www.reddit.com/r/leagueoflegends/comments/2jsiz0/is_nidalee_disabled/

So yes, there was a bug NEGATIVELY effecting Nid, and she was disabled. This bug effected many champs, but only Kass and Nid were disabled.

Now, there is a bug POSITIVELY effecting Nid, and she gets to stay.

Seems like pretty solid evidence to me.

qetzel2 votes

Based on the frequency of reproduction that was a far worse problem than the current one. Truly gamebreaking for every Nidalee player and their team for every game that Nidalee was played. It was shit...

junglerboy167 votes

Please go troll some other thread, we honestly could care less about your bitching about Nidalee being a favorite, because sadly, IT JUST ISN'T TRUE.

Nucleophilic atk1 votes

Hey all,

We're currently aware of a bug where cone targeted abilities (e.g.: Annie's Incinerate, Nidalee's Swipe, Kassadin's Force Pulse, etc) are reversing their direction when cast immediately after using another ability (e.g.: the Flash Summoner Spell, Nidalee's Pounce, Kassadin's Rift Walk).

Champions who rely on cone targeted spells to finish their combos are most impacted by this, like: Nidalee, Kassadin, Pantheon, Annie (Flash + W), Darius (Flash + E), Singed (Flash + E), Riven (2nd cast of R), among others. http://forums.euw.leagueoflegends.com/board/showthread.php?p=17530731

Network Operations – Last Thursday at 01:35 While we are aware of the bug involving cone spells being mis-aimed when used immediately after a different ability, there are two champions more severely affected than others: Nidalee and Kassadin. Due to the highly negative impact (and frequency of occurrence) of this bug on these champion's core gameplay patterns, we decided it would be better to disable both as we work on a fix. http://www.reddit.com/r/leagueoflegends/comments/2jsiz0/is_nidalee_disabled/

So yes, there was a bug NEGATIVELY effecting Nid, and she was disabled. This bug effected many champs, but only Kass and Nid were disabled.

Now, there is a bug POSITIVELY effecting Nid, and she gets to stay.

Shit just got real.

junglerboy163 votes

There is a major difference between A: an easily reproduced and isolated bug common to several champions related to a single patch. and B: A very rare, hard to recreate bug that has been evading the bug team for several years, on a single champion.

S@#% just got real? eat your own words.

Fredart3 votes

Are you sure its not her hidden power?

Ariel the Cruel1 votes

Her hidden power is being toxic as sin.

oh... and...

...when she succeeds, generates more hate posts on forums around the world than most other champions combined.

X Frady3 votes

Great job. I really hope Rito disables her now

4nth0l0gy2 votes

Wow. Thanks man.

Serenity2 votes

I feel like we need to urge Riot to disable her..

Meep Man1 votes

This seems pretty hard to do at random. I wonder how it seems to show up so much unless people know how to do it.

FlashnFuse3 votes

basically you spear at the end of a cancelled auto attack. Its understandable that it can happen completely on accident.

Ariel the Cruel2 votes

I'm fairly certain it happens less often than people claim. It's also considered to be most common on Nid's head hunter skin, though Riot has acknowledged those spear are harder to see (and banned it from tournament play). For reference, look up how often people complain about invisible Ez Q's and Mundo Cleavers. I'd imagine they suffer from the same bug.

The biggest difference is A) the projectile speed (Mundo's and Ezreal's are a lot faster) B) Impact (A slightly fed Nid can potentially 1-shot a carry).

Urdnot Entar1 votes

Doing the work Riot doesn't, good job. Now to see if they actually do anything about it.

FlashnFuse1 votes

still eagerly awaiting a red post....

Urdnot Entar1 votes

Yeah, but this is in the "Report a Bug" forum, and it's about a functional game issue (not the store or something cosmetic). Chances are slim at best.

Poptart Evelynn1 votes

Well since it's in the open. There is a few of us who know how to do it 100% of the time without auto attack canceling. It involves pressing S and using taunt while throwing a spear.

Rip trick. Wont say how to do it exactly but you might be able to figure it out :D

weeaboomer1 votes

Wow

Banana Nations1 votes

Id love to try it out in customs vs friends just to mess with them XD but its definintely going to be annoying to go into games where people have learned how to exploit it to the point where its a bad play enviroment

More from Report a Bug

Can't hover over friends
Report a Bug236 comments
663
votes
Infinite Loop Client Restart
Report a Bug886 comments
626
votes
patch 5.18 unexpected platform error
Report a Bug425 comments
445
votes
Origin of Master Yi Alpha Bug
Report a Bug176 comments
330
votes
Elise Can Only Rappel to Wolves on Blue Side
Report a Bug47 comments
277
votes
Loading bug
Report a Bug426 comments
274
votes

More by FlashnFuse

Petition to add Demon Vi's Wings to her sprinting (homeguards) animation!
Story, Art, & Sound16 comments
136
votes
If you are dissatisfied with the state of the game, stop buying skins.
Gameplay107 comments
128
votes
[GAMEPLAY] Easily exploitable Kindred passive stacking bug
Report a Bug46 comments
122
votes
A non-numbers nerf to Illaoi
Gameplay78 comments
100
votes
Quinn's auto attack animation needs to be fixed (with video!)
Gameplay43 comments
80
votes
New Sorcery keystone idea: Supernova
Gameplay69 comments
33
votes