title says it all Heres the proof for people who don't believe me https://youtu.be/TAd73WGQnRI Lol, the fizz mains are literally downvoting every comment I make on this because they don't want this dash issue to be addressed...
Joseraph16 votesThere's a weird interaction with dashes and displacements where a dash will override a displacement when the displacement hits during the dash's startup frames. It sparked a giant controversy 2 months or so ago when the boards found out, and they blamed it on Riven(All the while acting like it was brain dead easy to pull off, and that it could be preformed against any CC, even though it has to be frame-perfect, and only ignores displacement), because Boards hates Riven.
Tl;Dr: Unlucky.
Xavanic4 votesStill should be addressed, because fizz is already insanely strong, letting him have this displacement immunity is gamebreaking
YoungSirJ0ey5 votesIt's not immunity. It's luck. No one on Earth can perform it consistently, not even on characters with dashes with extremely long startups, let alone Fizz.
Joseraph7 votesThis isn't a Fizz problem, its a dash problem. Riot would probably be better off nerfing Fizz than attempting to fix this, as they'd have to recode all dashes. Additionally, this displacement immunity again has to be frame perfect. It's quite literally impossible to pull this off consistently.
lofi n chillhop1 votesif they have to recode all dashes just to address how dashes get handled, they need to fix their coding strategy. because such a thing should be as easy as fixing a parent class, or something similar.
Fondling Gems3 votesPosted a longer piece elsewhere but it is literally a case of the command input and displacement have to hit on a single specific tick while there are 30 ticks a second in League.
Humans can only detect about 60 frames of vision per second, and our brains take roughly .25 seconds to react to an input. That means that it is going to be pretty much impossible for someone to actually react and purposefully cancel.
Also note that all dashes can do this, it is just how code works and the heaviest abuse case to exist (Riven) wasn't even consistently reproducible by people with reaction speeds that are under half the time of the average person.
Then of course we have to add ping into the mix and it isn't realistically possible unless the ability has a long windup/travel item or you actually predict it, all cases of which still require sending a tick at the exact right time, which can change due to ping.
YoungSirJ0ey1 votesI mean, it kinda can be done vs. all CC. Due to the way displacements work, non-displacement CC can't stop dashes, and as such you can cancel sufficiently short CC with a sufficiently long dash, but if the CC is longer than the dash you'll be CC at the end of it. This should also be how cancelled displacements work, though, as the movement portion would be overridden, but the stun portion wouldn't, so you'd be stunned at the end of your dash if you dashed out of, say, a Lee Sin kick.
If I'm wrong, then Riot needs to fix their spaghetti.
On another note, how would this be Riven's fault? I didn't think her dashes even had cast times.
Joseraph2 votesI'm not 100% sure on how most dashes react with CC, sorry.
This isn't Riven's fault at all, but Gameplay pegged it on her because they have a hate boner for Everything Riven. Her cast time is apparantly really unnoticeable short, but still there.
Jmman1 votesFiddle's fear is the same thing. Any animation takes my fear. Its sucks because it doesn't stop them. My fear is gone and they were never feared. Sometimes the fear is longer than the animation. But they don't seem to be feared. Now some like ez and ahri are feared after the dash.
They have poop as coding and do not what to fix it due to the cost
Metallmeister14 votes[deleted]
Xavanic1 votesObviously
Ben Sharpio14 votesan 8 second clip? you're supposed to make it 10 minutes (not including the 5 min "hey guys dont forget to like and subscribe" intro)
Xavanic3 votesLol yeah totally I will go edit in 10 minutes worth of extra un-needed crap and put the clip somewhere in between brb
Auz the Ripper13 votesit's the timing that got you you ulted during the millisecond of cast time that urchin strike has, then once urchin strike actually started it overrode the knockback
Xavanic4 votesSeems kinda dumb, considering fizz is already hard enough to peel off with his E, plus I've done this with syndra and cancelled out his q, whats different about sols ult other then its got a longer CD
Fondling Gems4 votesUnfortunately that is just how code works. Fizz received the trigger to his Q, the abilities is about to be activated once the computer ticks to check it. However before then a knockback effect is applied, beginning to knock him back, his Q then goes off as the computer reaches the command (before being able to loop through again to check if he is being CC'd) so his Q activates and sets his force in a new direction, overriding any other force effects that were on him before.
It is one of those things that you can kinda clean up, but it requires checking every effect on him (and thus checking for each possible effect on him) closer to 10 times per tick as opposed to once per tick. For the incredibly low chances of it happening it generally isn't worth it.
Plus very specific conditions have to be met (Example being when Riven could do this she just had a much larger window so it had a higher chance of going off)
League updates 30 times a second, and multiplying a value that is being checked 30 times a second on every champion with a dash can very quickly get out of hand for how small of a problem it usually is.
Xavanic2 votesWell if this is gonna cause problems at some point (most likely in the LCS) if fizz keeps gaining more popularity
Anidan3 votesI mean, has it before? Because it's always been like this and nobody has said anything about it. It tends to be extremely rare for things like that to happen and pulling it off on purpose outside of a controlled environment is usually exceedingly hard.
Steelflame4 votesEven pros can't time that shit. It won't be a problem, you just managed to get fucked by an infinitesimally small chance of timing. Pros will never try to use that "trick" because if the A-sol ult landed at literally any other point of the time it would have not just knocked fizz back, but also completely eaten his Q CD to boot, leaving Fizz without his primary gap closer. Unlike Riven who has 3 Q charges and an E, Fizz has exactly 1 shot during 1-2 frames to get it to go through. That he has to plan through latency to boot.
yay nibbers4 votesLiterally anyone with a dash can do this, but it's actually practically impossible to time because the window to do this is microscopic. You just got really unlucky this one time.
Fondling Gems6 votesThis bug has been around since League was created. Every single champion with a dash can do it, and they have been able to do it since knockbacks and dashes existed.
How many times has it popped up since then? Not much. I think you overestimate the actual chances of this happening.
Ariel the Cruel6 votesCast time buffering OP.
underscores2224 votesThe issue is that the game allows movement commands to be overwritten. So what happened here is that Sol's knockback move was canceled by Fizz's urchin strike. Similar things can be done with Ezreal or Trist jumping out of a blitz hook. It is not the code misbehaving, but rather a limitation of the way move commands and spell movements are processed by the game engine.
Xavanic2 votesReally hoping this gets addressed or fizz gets nerfed, because the inability to peel him off you because of this is actually devestating, nearly lost the game because he snowballed out of control after this (thank god our jinx snowballed harder)
underscores2226 votesThis isn't a fizz problem - theoretically any champion with a dash can do it. It's just much easier with some than with others, due to cast times and ranges.
However, unlike many things, you can actually flash away from an urchin strike to avoid taking the damage.
Xavanic2 votesyeah, but once you do that, he just throws his retardedly op ult as you wont be able to dodge it
underscores2224 votesI mean, they did make it significantly easier to dodge now. Also I note your flash wasn't up at the time anyway.
Xavanic2 votesyeah, i had used it to dodge his ult combo previously, his ult is too fucking easy to land and essentially guarantees him the kill
MissingKayo2 votesIt seems like his Q dash canceled it out. Probably just an unintended interaction.
Xavanic2 votesEither way, this is bringing attention to it so it can be fixed
MissingKayo1 votesYeah, just clarifying a bit more specifically.
Snowplosion2 votesI think that might be Sol's R having a bad hitbox rather than Fizz being immune to knockbacks.
Xavanic1 votesHe got hit by the ult, but didn't take the knockback (the particles for the after-slow are on fizz)
Snowplosion2 votesIt seems like that, but it could very well be an A. Sol bug rather than a Fizz bug. I'll try to do some testing on my own to see if it is Fizz or A. Sol.
MunchCrunchLunch1 votesthis is a bug that was fixed on riven. it should be fixed. basically queuing movement ability cancels displacements