Dude... no one in this thread has provided a single argument that that turret "bug" was a bug except for saying Riot said so or by giving vague statements, so still appeals to authority. And what I'm saying is not voodoo science, it's quite literally testable: go into customs with a friend, play in practice mode, or play KJ for a while and you'll realize these are just the regular mechanics of the turret. It's just that, in this instance, 2 unreliable features of the turret triggered simulatenously which gave a "bug-like" response, but it's not a bug.
If this were a bug, you quite literally can't jiggle peek a turret that's standing adjecent to you since it will continue to replicate what happened in the tourney. And for Riot to blame FPX for that is EXTREMELY foolish since it's what they coded.
that replay was bs.
Bro doesn't know how coding works LMFAO. You don't code a bug you fix bugs.
Just cause something happens regularly doesn't mean it's not a bug.
Superdashing is a bug abusing the physics engine behind Jett, and yet riot hasn't fixed all the issues.
You have no proof that it isn't a bug. They didn't blame FPX for that which is WHY they REPLAYED the round.
Just because a bug is reproducible doesn't make it not a bug.
Your entire argument this thread is that "Oh kj players should know it happens" that doesn't make it not a bug. Just because something happens frequently doesn't make it not a bug.
I'm not saying the bug was coded? Wtf are you on about?
I'm saying the features of the turret is what Riot coded, and the supposed "bug" is a natural manifestation of the coding. I already said, jiggle peeking the turrent when it stands adjacent to you after it shoots its first shot will quite literally replicate what happened. So, anytime a player jiggle peeks a turret, he or she risks abusing a "bug?" That's laughable in so many levels. It's not even analogous to the Jett dash because you need to be methodical on where and how you dash, unlike jiggle peeking a firing turret, which is a natural response...
They held FPX responsible by having the match replayed after winning. Despite the fact that everyone knew this was a possibility.
I'm saying unless u can show that they explicitly put in the game for this purpose you can't say it isn't a bug.
"Natural manifestation of the coding" is the same vague language that u were bitching abt "not intended functionality" or whatever.
It wasn't purposefully abused, it was just a bug that popped up and due to that THEY WEREN'T PENALIZED.
FAZE LITERALLY DCED MID ROUND DUE TO A POWEROUTAGE IN A STAGE 2 NA MATCH AND THEY LOST THE ROUND
FPX literally just had to play out one more round because of an error on riots part.
My favorite part of this is how you choose to push conspiracy theories on "omg riot rigging for storylines" instead of trying to use any brainpower on why riot might have redone one round.
So you're just going to ignore the fact of how ridiculous it is to claim players are abusing a bug for jiggle peeking a turret?
How many times must I repeat myself? I wrote down MULTIPLE TIMES how the turret acted is a natural manifestation of its coding. Istg, this will be my final time.
Is it a natural mechanism for the turret to always shoot 3 burst shots if it fires its first shot - even if the enemies are out its sight in between shots? Yes.
Is it a natural mechanism for the turret to miss its shots if the enemy finds cover? Yes.
Is it a natural mechanism for the turret to reposition if the enemies get out of sight when the turret is looking too left or too right from its initial position? Yes.
Then how the fuck is it NOT a natural manifestation for the turret to reposition as it is missing its shots (from the enemy), given how it was coded???
edit:grammar
Discord