why do you still get stunned by tibbers if you were out of its range before animation appears??

ForgiveColour·Apr 3, 2015·6 votes·877 views

title

fix it pls, it already have very little counterplay

14 Comments

I Kill CommiesApr 3, 20152 votes

cuz riot logic. Why can blitzcrank knock you up after you've already flashed away? There's no reason for it other than lazy coding.

Sailor MintApr 3, 20154 votes

Didn't you say auto-attacks should never be canceled if they ever complete in another thread?

That's a side effect of your wish and latency.

You can't interrupt Flash. Auto-attacks will always go through if the target is in range at the end of the wind up.

Here are a bunch of skills that have been cast successfully. Play them sequentially.

I Kill CommiesApr 3, 20152 votes

Blitzcrank is a melee attacker. Basically think about it like this: If I pull back my fist to punch something, but die before I swing my fist, will I still punch it? Obviously not. On the other hand, if I fire a bullet at something but die before the bullet hits, will the bullet still hit? Obviously yes. But in league that bullet just disappears into thin air when I die. Makes 0 sense for ranged autos to cancel like that. Makes 0 sense for melee autos to not cancel like that.

Sailor MintApr 3, 20152 votes

Stop trying to apply reason to games.

Real life doesn't have latency, nor do events happen sequentially.

I Kill CommiesApr 3, 20151 votes

Sorry, but what do you mean by that? Yes there's latency, even if you have excellent ping there will be some delay between your inputs and what actually happens. But otherwise, there are things in this game which have 0 cast time.

Sailor MintApr 3, 20152 votes

Nothing is truly instant.

Things can happen in between you successfully casting Flash and the spell effect going through.

I Kill CommiesApr 3, 20152 votes

Yes, obviously that stems from latency. Flash is supposed to be an instant spell, meaning that it has 0 cast time. But there's a delay from the time you press flash and the time it goes off, depending on ping. But if the blitz auto hits me before the flash registers, then I shouldn't be able to flash because I'm knocked up. On the other hand, if I flash before blitz knocks me up then his knock up shouldn't be able to hit because I'm clearly outside his autoattack range.

Sailor MintApr 3, 20152 votes

It's not even latency, it's the nature of how things are processed. We're talking about milliseconds and frames here.

I Kill CommiesApr 3, 20152 votes

Yes, milliseconds and frames. This game's (any any game's) timing is quantized, i.e there is a minimum amount of time that must pass between things happening. I don't know how much you know about this, but in games and simulations these time steps are often referred to as "ticks". If you run 60 ticks/second then that means that the computer/server will update information in the game 60 times/second. (also, note that actual frames on your computer screen have nothing to do with these "ticks". Whether your CPU gets 20fps or 200fps does not matter in how the game runs, only in how you experience it). So when you press flash and the server finally registers it after the signal travels from your CPU to Riot's servers, that flash command happens on a specific tick. If the game is 10 minutes in and runs at 60 ticks/sec (this is just a guess, I don't know how many ticks/second league runs at) then your flash command might happen at tick #36000, or 360034, or whatever. Same with blitz's knock up.

So you see that there can be absolutely 0 ambiguity as to the timing of spells and such. Every spell falls on a specific tick. A spell can't happen on tick 100.5, or 90.8. The timing of a spell is an integer. If blitz knocks you up exactly one tick before your flash command is queued then you should not be able to flash. One the other hand, if you flash exactly one tick before blitz's auto lands then you should get away safe without being hit by it. I guess if there's a perfect tie (highly unlikely) then we can simply make some rule to give the advantage to either blitz or the person who's flashing. Either way, it should never be possible for both your flash and blitz's knockup to go off. in fact, it should never be possible for any melee attack to hit after somebody has blinked away. It's why I said the only excuse is lazy coding.

Sailor MintApr 3, 20154 votes

Once again, you're assuming 0 latency and that spells are made up of a single event on a single tick.

I Kill CommiesApr 3, 20152 votes

I'm not assuming 0 latency, and even for spells that do have a cast time they must start on a specific tick. Blitzcrank's fist hits you on a specific tick, and your flash is first registered on a specific tick.

Sailor MintApr 3, 20151 votes

Because most movement abilities are not interrupted by crowd control.

If you got stunned, you didn't make it out of range in time.

KingsgraveApr 3, 20151 votes

Its a PBAOE ability, so I'm assuming it applies the damage based on where you were on cast and not where you were when it would logically deal damage after the animation. It's essentially like an ability version of a melee autoattack. If Blue Buff is in his windup of autoing and you get out of range he will still deal damage to you even if you are like 200 range away from him because you were in range as he was "casting" the attack.

This happens with cone abilities as well. It only checks where you are on cast. Go test it out on Darius and see what I mean.

crunchymunchysApr 3, 20151 votes

Funny, i remember back in the day when it was still Season 1 and you could flash and not expect someone that is melee to kill you with an auto to where your flashed essence was. Its lazy coding between client and server that is most likely the cause of this, which is kind of understandable considering the growth at which the community felt but its not something you as a game dev just completely ignore to tell your players. I'm starting to be turned off free-to-play games completely because they end up becoming nothing but one giant bugged out content with horrible balanced due to parts of the community deeming a champ strong but not op and will no longer pay for said champion skins (im looking at you Lee sin(they were gonna make Lee sin better late but worse early, but enough mains cried bloody marry and how they wouldn't buy another skin for that champ and it never happened) and Riven). Sad as it sounds, I play Battlefield 4 more and enjoy it a ton more than this game and its not because of just the community or how long ive been playing the game, its playing against a losing system that kills it for me.