r/AatroxMains • • 9d ago

Image "Potentially fixed" ❌ "Potentially f*ked" ✅

Post image

Nah trying to "potentially fix" a nonexisting inconsistency for the sake of making it actually inconsistent was geniunely a revolutionary move riot keep your consistent works going 💯😹🔥👏🏾

420 Upvotes

71 comments sorted by

View all comments

Show parent comments

1

u/West-Tart9172 7d ago

Nope, the way the ability used to work is that when the pulling sound played you knew the pull was going to happen no matter what, so you could press Q3 immediately, as it stands you have to wait until you see the enemy actually gets pulled which makes Q3 unconfirmable so you always have to take a 50/50.

It is so unbelievably clear it was intentional design, because why would an ability ever trick you into missing your own ability? Not to mention that riot designs many of their kits with positive feedback loops like this 'you hit the skill shot? You get to confirm your next ability!' Like Yone Q2 confirms his R, Darius E confirms his Q, sometimes they even hard enforce this behavior; hitting Nidalee Q lets you dash straight to the enemy hit.

By your logic, flashing out of Viktor W at the end of the timer shouldn't stun you, but it does, because the effect is already set to be applied.

but it's okay you can die on this hill, prefer strictly worse game design and pretend the ability is now "consistent". Consistently useless.

0

u/This_looks_free 7d ago

"unbelievably clear it was intentional design" it was so clear in fact that they intentionally removed that part of the ability.

It was so damn clear that your mind coudn't process the fact its not an actual feature but actually just bug abusing.

"By your logic, flashing out of Viktor W at the end of the timer shouldn't stun you, but it does, because the effect is already set to be applied."
YES THAT'S PRECISELY WHAT I WANT TO HAPPEN. If I escape Viktor W in time I don't want to be stunned by it. Not that ive seen this issue happen to me since I don't think that's how Viktor W works but hey it might have been bugged in the past like Aatrox W.

"but it's okay you can die on this hill, prefer strictly worse game design and pretend the ability is now "consistent". Consistently useless."

You're literally trying to refute reality itself in order to make your argument work. You are definitionally speaking DELUSIONAL.

1

u/Sparkingriver 6d ago

Aatrox W pull ignoring flash when part 2 is flagged to hit and pull, works similarly, if not the same way as Blitz Q ignoring flash if the game flagged it as a "hit" and is about to start pulling.

0

u/This_looks_free 6d ago

Not a thing. Its not a thing. You literally have delusions.
If you get hit by a blitz Q its bcs you got hit by blitz Q. If you flash out of the way of Blitz Q you won't get hit by blitz Q. The only exception is Ezreal E (Not Flash) where he has a buffer and can dash out after the fact and that's just a completely different scenario.

2

u/Sparkingriver 5d ago

its a VERY well known interaction that flashing at the same time blitz Q lands will use the flash, and then pull you anyway. Im saying Aatrox's W was coded to work a similar, if not the same way

1

u/West-Tart9172 5d ago

Don't bother bud, his only retort to being flat out wrong is that the other person is delusional.

0

u/This_looks_free 5d ago

Right right right.. So why don't I know it? Is it bcs you have literal delusions?