Just to throw this out: Please, fix Master Yi's Alpha Strike already

SEKAI·Jul 22, 2017·10 votes·3,851 views

I'm honestly getting a bit sick and tired of the stupid bug on Yi's Alpha Strike. Those who's played Yi or has seen him being played for more than 2 games should know exactly what I'm talking about:

I'm talking about the fact Yi still takes damage (from AoE and skillshots in particular, and other attacks that his Q is supposed to dodge) and die mid-animation during Alpha, and worse, you can actually get CC'ed during Alpha Strike. I'm not even joking with the latter claim, you can be for example hooked during Alpha Strike by say a Thresh, and the thing will be tethered onto you after the completion of animation too as if it was a legit hook to begin with which is just BS; and if you watch a replay on that and fix the camera onto yourself, you will notice the camera would be dragged towards Thresh when he "hooks" onto you during Alpha, confirming you indeed can be CC'ed during Alpha Strike. I mean, what in the bloody name is that shit?

Can we just fix this years-long bug now already? Sure, it's not as bad as someone like say, Morde with his what, 180+ laundry list of bugs because misery loves company amiright, but honestly.... Considering how split-second timing critical Yi's gameplay is and how fast he dies, and now with him dying all the time to random crap he is not supposed to get hit by thanks to the bug..

Again, can we just fix it already?

Thank you.

63 Comments

Just Blame JennyJul 23, 20174 votes

Not so long ago, while chasing a Master Yi as Warwick, I elected to ult to catch up to him.

Being the clever fellow that he was, he used his Alpha Strike on a minion wave to dodge the ult.

...

Whereupon he blinked out of existence, and I collided with nothing and proceeded with the usual ult animation in apparent mid-air.

Then Master Yi reappeared and dropped dead.

???

Not buggy at all.

SEKAIJul 23, 20171 votes

{quoted}

Not so long ago, while chasing a Master Yi as Warwick, I elected to ult to catch up to him.

Being the clever fellow that he was, he used his Alpha Strike on a minion wave to dodge the ult.

...

Whereupon he blinked out of existence, and I collided with nothing and proceeded with the usual ult animation in apparent mid-air.

Then Master Yi reappeared and dropped dead.

???

Not buggy at all.

Indeed.

But as explained by another person, a lot of it are technically not bugs due to Riot's coding which are well.... But yeah still, that needs to get fixed or at least get reduced.

Riot could use a reminder that it's still very much present in the game and it's ruing the experience quite a bit for anybody playing Yi.

DJMason88Jul 22, 20173 votes

bUt I wAs In AlPhA

Pie CubedJul 22, 20172 votes

Isn't he only untargetable? He's not invincible.

SEKAIJul 22, 20172 votes

[{quoted}](name=Pie Cubed,realm=NA,application-id=3ErqAdtq,discussion-id=Gtxzzygn,comment-id=0000,timestamp=2017-07-22T19:37:59.814+0000)

Isn't he only untargetable? He's not invincible.

It isn't invincibility.

But Alpha Strike is not working as intended either.

LoLWiki: Untagetability

Untargetability refers to units in a state where they are no longer valid targets for auras (e.g. Sunfire Cape), unit-targeted (e.g. Disintegrate), auto-targeted (e.g. Requiem), direction-targeted (e.g. Mystic Shot) and ground-targeted effects (e.g. Pillar of Flame), including attacks, abilities, items and summoner spells. Becoming untargetable is not a form of invulnerability, and units will still suffer the effects of active applied damage over times (e.g. Ignite), delayed detonations (e.g. Time Bomb) and tethers (e.g. Drain).

The act of becoming untargetable will also interrupt any effects that have already acquired the unit as a target (e.g. an oncoming basic attack will fizzle) as well as causing AI-controlled units (e.g. turrets and minions) to acquire a new target (also known as "dropping aggro").

The telegraph from Karthus's Requiem will be placed on untargetable enemies, although the damage itself is classified as auto-targeted effect that occurs at the end of the channel time.

Concerning the bit on DoT, delayed detonations and tethers, it refers to when they're already applied before going into untargetability.

The point of untargetability is that once you're in that state, you're literally not a part of the game and pretty much everything coming into your direction after achieving that state will just phase through you (fumble/miss/dodge).

.................

Not Yi though, because going into Alpha means he'll take everything and anything regardless of what the rule says and die. May be exaggerating a bit but you get the idea.

Dani El PezgloboJul 22, 20171 votes

watch video again, syndra e when yi was q (look it apper canalitation time for 0'1 s, so thats the reason why he got hit , because he wasnt still on q , notice it always are when q starts.

SEKAIJul 22, 20171 votes

{quoted}

watch video again, syndra e when yi was q (look it apper canalitation time for 0'1 s, so thats the reason why he got hit , because he wasnt still on q , notice it always are when q starts.

Reply to the relevant comment chain? Why make a reply on another comment I have instead of the one I was replying to you with?

Anyway, I did say that some of the examples in that video is (possibly) wrong. But it still doesn't change the fact the majority, or vast majority, of the examples shown are not.

Yi's Alpha bug is also nothing new. It's been here for a long time and well documented as well. Riot just hasn't got around fixing it, which pressuring them into doing it is the point of this thread and something I hope can be realisable.

There is nothing to prove or disprove here when it comes to the bug itself really, the Alpha bug is a very widely known bug, which has been in this game for at least a full year already.

Dani El PezgloboJul 22, 20171 votes

soz, but it isnt a bug, is how game is done, this is more ez to watch on skillshots, when u q with lux, u have a time in which q is appearing , what u call bug is actually the ssame, casting time, when u are q with yi , u have cast time , on that time u can get hit.

I ll like riot fix this , but is literally change how the whole game is programmed, so dont expect this happen.

Same pass with aa + f, someone aa u f , then aa hit (i mean melee) u and u die, thats because the same problem , because there is a delay btw the rude boi aa u , and u get hit by the aa. Bad english , soz

SEKAIJul 22, 20171 votes

{quoted}

soz, but it isnt a bug, is how game is done, this is more ez to watch on skillshots, when u q with lux, u have a time in which q is appearing , what u call bug is actually the ssame, casting time, when u are q with yi , u have cast time , on that time u can get hit.

I ll like riot fix this , but is literally change how the whole game is programmed, so dont expect this happen.

Same pass with aa + f, someone aa u f , then aa hit (i mean melee) u and u die, thats because the same problem , because there is a delay btw the rude boi aa u , and u get hit by the aa. Bad english , soz

Except that's not how it works, at all.

Since you're replying to this comment chain, this means I should assume you've read the definition of "untargetability" in this game provided above. But this reply only shows you've not read it, nor do you understand how that works.

Making it so Yi will not take damage from AoE and whatnot, as well as preventing Yi from getting CC'ed during his Alpha's animation is just making it work as intended, ie BUG FIXING. Currently, Yi's Q is not working as intended, fixing that will not "change how the game is programmed".

And even if it would, then by all means change it, because obviously the current coding doesn't work as how it's meant to anyways.

............

And no, Yi doesn't have a cast time on his Q. This isn't Season 1 anymore. In fact, though I may be wrong on this, but I don't think there was a cast time back on Q in S1 either.

Dani El PezgloboJul 22, 20171 votes

its not aoe , watch ur video , vayne a a him (that isnt aoe) What u dont get is that 0'1 s , he isnt using q , he is casting it , so he doesnt have yet Untagetability , u need end dat delay to being Untagetability. Since all skills on the game have cast time, delete that ll change the whole game. Yi isnt hit by aoe , he is hit because he isnt still on the q.

im not saying if riot should or not changing it , im just answering why this happen and if this can be fixed.

SEKAIJul 22, 20171 votes

{quoted}

its not aoe , watch ur video , vayne a a him (that isnt aoe) What u dont get is that 0'1 s , he isnt using q , he is casting it , so he doesnt have yet Untagetability , u need end dat delay to being Untagetability. Since all skills on the game have cast time, delete that ll change the whole game. Yi isnt hit by aoe , he is hit because he isnt still on the q.

im not saying if riot should or not changing it , im just answering why this happen and if this can be fixed.

Can you just read the definition of Untargetability, I even quoted it out for you. Just go and read it. Then look at Yi still taking damage and CC during his untargetability frames after the activation of the spell and tell me how that's working as intended.

Also, unless there is a channel bar, otherwise there is no casting time. Yi's Q has no cast time.

And EVEN IF Alpha does have a cast-time, which it doesn't, but let's assume it does, the issue at hand is that Yi can still be damaged and CC'ed during the animation of Alpha Strike after a successful activation while he's not supposed to. So the issue is AFTER the casting hence it doesn't matter whether or not it has a cast-time anyway. But then again, Alpha Strike does not have a cast-time to begin with.

Either way, you do not need to change up the entire game or something to fix that bug. All it takes is fixing Yi's exclusively broken untargetability of his own that's clearly not working as intended.

Dani El PezgloboJul 22, 20171 votes

watch ur video m, syndra e him , he q so he disapear , then when he appear all the damage and cc he takes on that times appear, because u cant cancel yi q, thats why he takes the damage/ cc one he appear, same reason why when u kill him first q animation end. all the cahmps can be damage during cast time , kayn ult works on the same way, so yes u need change how game works , because u ll have to delete cast time (that he have ,m watch ur video a blue lane appear 0'1 s thats him cast time, and thats why this 'bug' alñways happen at the beginning. U ll have to delete cast time of the game, and right now , skills are programmed to have cast time . When he is casting he isnt on q yet, thats the same reason u can e with ahri , f on cast time , and e appear when u f, because abilitie appear one u end cast time, not before. dude , im just explaining u why this 0bug happen' thats the reason, u dont need argue with me.

Yi isnt damage during alpha, if on him cast time he gets damage , he ll be recieve it when alpha strike animation ends (it didnt cancel q , because u cant cancel yi q, i think u should go private game with a friend and test the same with fizz , u ll see same happen to him.

Definitely BaitJul 22, 20172 votes

Btw Kayn has a ult that suffers from the exact same problems as Yi's alpha strike.

EvilMerodachJul 22, 20171 votes

I remember a Red talking to Cowsep on forums about Alpha bug, and that even though it's only been highly noticeable for 2-3 seasons, it's been there since beta. And to fix it, they'd need to rewrite it from the ground up. And possible it still wouldn't fix it. And it would 100% feel different/exact timing for how the animation plays out would change. Which would basically require relearning Yi from the start.

So, would it be worthwhile to completely break Yi's current feel to maybe fix him? Possibly. But it's also a difficult and lengthy process to recode it. Like mini-rework level.

So, would you rather Yi get a mini-rework, and possibly just be a different champion than before, or keep him the same and keep the bug? There isn't a middle ground (keeping him the same and getting rid of the bug, it's just not possible). Just the way things are.

I think, Riot feels leaving it would cause less disruption to Yi players in general to just leave him be, cause they also have no real direction to rework him in anyway.

SEKAIJul 22, 20171 votes

They do realise in the current stage of Yi's Alpha and his kit, he may as well have 2 self-roots in his system right? 1 he can cancel out of (W) and one he can not (Q).

Not to mention, Yi is not the only champion with untargetability, so why is Yi the only one with this problem, or at least the only one with it so bad like this?

Last but not least, it's been highly theorised that the issue is only this bad because of the updated monster aggro system, and shadow changes to Q in attempt to accommodate the change that causes the problem to be this bad to begin with. The issue may have been there since beta, but it's only gotten this bad due to recent errors; I mean, why else would this problem only becoming noticeable in the last year or 2, when it has supposedly been there since the beginning nor was it anywhere as noticeable with his rework?

It obviously CAN be fixed, or at least heavily marginalised. Riot is just not doing it.

..............

And really, Yi lives and dies on his Q, and it's utterly broken and doesn't even work half the time. Idk about anybody, but isn't that already an urgent call to fix?

EvilMerodachJul 22, 20171 votes

Any bug on any computer system can theoretically be fixed. Problem is how complicated it is, and if there is someone smart enough to fix it.

Theory on agro system was said by the Rioter to not be related. Just incidental correlation.

Basically everyone who played Yi back then were just pubstomper nubs compared to modern Yi players. They got gud over the years. Using q to dodge stuff more exactly, so more and more noticeable when it fails to do what it's supposed to do.

Also some weird shit like Annie w+passive, and, formerly, Cho w, have/had some strange coding of their own, where the target was acquired at beginning of cast, not when it actually went off. (Which is why you can flash away and still get hit by it.) Those look weird as hell, and look like you should be able to dodge with Alpha, and is logical that Alpha would dodge them, but in truth, they are actually intended to work that way.

So, several cases of 'I should have dodged that' are actually just weird coding that isn't intuitive, but isn't actually a bug. But there is also a bug too. And an insanely hard one to fix. Rioter did say they spent 12 hours just working on it. At my payrate (which is a good bit less than any Rioter I'm guessing), that's around $150 worth of time.

And continued to work on it after, unsure how much time of hard coding. Plus all the testers, and skin team also has to work with each code 'fix'... I'm guessing they spent min. of $500 attempting to fix that bug. Probably a lot more than that.

There's just a point where it has to be benched. Sad but true.

SEKAIJul 22, 20171 votes

{quoted}

There's just a point where it has to be benched. Sad but true.

I'm thinking why they can't just code it as an invulnerability with some exceptions, wouldn't that be far easier to deal with than the current situation?

If it's coded as invulnerability, it won't matter whether or not Yi's gonna take damage or be CC'ed mid-alpha because he'll just negate everything anyway due to invulnerability. And then you can add exceptions to it one by one, which there aren't many of them to begin with since Q is meant to dodge almost everything.

Dunno why they didn't do that instead.

EvilMerodachJul 22, 20171 votes

{quoted}

I'm thinking why they can't just code it as an invulnerability with some exceptions, wouldn't that be far easier to deal with than the current situation?

If it's coded as invulnerability, it won't matter whether or not Yi's gonna take damage or be CC'ed mid-alpha because he'll just negate everything anyway due to invulnerability. And then you can add exceptions to it one by one, which there aren't many of them to begin with since Q is meant to dodge almost everything.

Dunno why they didn't do that instead.

I think you mean 'unstoppable' not 'invulnerable.' Kayle can still be CC'd in her ulti. Though either would be a big buff to him.

Can't answer for sure why they don't make him unstoppable for it. It might be too big of a buff for him?

Fairly sure there would be just as many cases where Yi would get a hard advantage vs him getting a hard disadvantage now in current state.

And considering how hard he is to stop in bronze elo already....making him easier in any way could break him to the point of him needing a major stat nerf to make up for it.

Which would make him horrible anywhere above bronze, cause he's not OP, just hard for noobs to deal with. Can't make him even harder to deal with for noob vs noob matches...

SEKAIJul 22, 20171 votes

{quoted}

I think you mean 'unstoppable' not 'invulnerable.' can still be CC'd in her ulti. Though either would be a big buff to him.

Can't answer for sure why they don't make him unstoppable for it. It might be too big of a buff for him?

Fairly sure there would be just as many cases where Yi would get a hard advantage vs him getting a hard disadvantage now in current state.

And considering how hard he is to stop in bronze elo already....making him easier in any way could break him to the point of him needing a major stat nerf to make up for it.

Which would make him horrible anywhere above bronze, cause he's not OP, just hard for noobs to deal with. Can't make him even harder to deal with for noob vs noob matches...

No. I meant "invulnerable". Because Yi is not supposed to get CC'ed mid-animation during Alpha.

Also bugs and broken interactions still need to be fixed. You really can't just leave it hanging there.

But what do I know.

EvilMerodachJul 22, 20172 votes

{quoted}

No. I meant "invulnerable". Because Yi is not supposed to get CC'ed mid-animation during Alpha.

Also bugs and broken interactions still need to be fixed. You really can't just leave it hanging there.

But what do I know.

But that's what I'm saying, even if Yi was invuln during Alpha, CC would still apply, where applicable. Because invuln doesn't stop CC. It just stops damage.

I think there's a few invuln abilities that also have 'immune to CC' attached to them, but just 'invulnerable' in itself is not CC immunity.

You could also mean stasis, like item 3157 active.

SEKAIJul 22, 20171 votes

{quoted}

But that's what I'm saying, even if Yi was invuln during Alpha, CC would still apply, where applicable. Because invuln doesn't stop CC. It just stops damage.

I think there's a few invuln abilities that also have 'immune to CC' attached to them, but just 'invulnerable' in itself is not CC immunity.

You could also mean stasis, like active.

Oh yeah, thanks for the correct there. But yeah, Yi's Q probably can work as a variant of stasis. They should try that.

rtbf221651412Jul 22, 20171 votes

Someone talked about how Alpha stage doesn't occur right when he is invisible and just because someone is untargetable doesn't mean you can't skill shot them. Just can't point and click. Untargetable =/=- invincible.

SEKAIJul 22, 20174 votes

{quoted}

Someone talked about how Alpha stage doesn't occur right when he is invisible

Maybe.

and just because someone is untargetable doesn't mean you can't skill shot them. Just can't point and click.

False. Untargetable means you literally don't exist in the game, in a way.

The only things that will affect an untargetable unit are DoT, delayed-damage/spell and tethers that are applied onto the said unit before they'd even gone into untargetability. Otherwise they should dodge everything else: AoE, skill shots, AA, lock-on, doesn't matter.

rtbf221651412Jul 22, 20171 votes

{quoted}

Maybe.

False. Untargetable means you literally don't exist in the game, or at least it's meant to.

In every single game I played, untargetable just means you can't point and click. In some RTS games I played I could still destroy a structure with other means. Again, untargetable doesn't mean invincible nor Invulnerable.

He has 4 stages.

One in which alpha occurs for a short time.

SEKAIJul 22, 20171 votes

{quoted}

In every single game I played, untargetable just means you can't point and click. In some RTS games I played I could still destroy a structure with other means. Again, untargetable doesn't mean invincible nor Invulnerable.

He has 4 stages.

One in which alpha occurs for a short time.

Or you can, you know, read League's definition of Untargetability.

LoLWiki: Untagetability

Untargetability refers to units in a state where they are no longer valid targets for auras (e.g. Sunfire Cape), unit-targeted (e.g. Disintegrate), auto-targeted (e.g. Requiem), direction-targeted (e.g. Mystic Shot) and ground-targeted effects (e.g. Pillar of Flame), including attacks, abilities, items and summoner spells. Becoming untargetable is not a form of invulnerability, and units will still suffer the effects of active applied damage over times (e.g. Ignite), delayed detonations (e.g. Time Bomb) and tethers (e.g. Drain).

The act of becoming untargetable will also interrupt any effects that have already acquired the unit as a target (e.g. an oncoming basic attack will fizzle) as well as causing AI-controlled units (e.g. turrets and minions) to acquire a new target (also known as "dropping aggro").

The telegraph from Karthus's Requiem will be placed on untargetable enemies, although the damage itself is classified as auto-targeted effect that occurs at the end of the channel time.

rtbf221651412Jul 22, 20171 votes

{quoted}

Or you can, you know, read League's definition of Untargetability.

LoLWiki: Untagetability

Just because rito or wiki says something doesn't make it true, infallible, and logical.

But hey, support Ashe since season 1 right?

Meanwhile you cannot click target Evelynn as Caitlyn KogMaw with item 3094 in camo even if she is in range because..

YOU CANT SEE HER YET.

But hey did you forget the fact it "Becoming untargetable is not a form of invulnerability"?

SEKAIJul 22, 20171 votes

{quoted}

Just because rito or wiki says something doesn't make it true, infallible, and logical.

But hey, support Ashe since season 1 right?

Meanwhile you cannot click target Evelynn as with in camo even if she is in range because..

YOU CANT SEE HER YET.

Huh?

So what you think something is based on your personal opinion, is more credible than what the wiki people digs up (they also test statements in-game) and even what the game maker says about their own game?

Wow, what a god you must be.

rtbf221651412Jul 22, 20171 votes

{quoted}

Huh?

So what you think something is based on your personal opinion, is more credible than what the wiki people digs up and even what the maker says about their own game?

Wow, what a god you must be.

Even if they said that, it wouldn't explain the evelynn 810 range Kog'maw interaction, so hush up.

I'm not the one who posted a link that completely counters your own argument.

"Becoming untargetable is not a form of invulnerability"

SEKAIJul 22, 20171 votes

{quoted}

Even if they said that, it wouldn't explain the evelynn 810 range Kog'maw interaction, so hush up.

I'm not the one who posted a link that completely counters your own argument.

"Becoming untargetable is not a form of invulnerability"

You're not making any sense at all.

So B has issues means A having issue is intended, or both are intended?

So A is not equal to C means A must work the way you think it works?

What??

rtbf221651412Jul 22, 20171 votes

{quoted}

You're not making any sense at all.

So B has issues means A having issue is intended?

So A is not equal to C means A must work the way you think it works?

What??

You said Yi cannot be damaged in alpha because he is untargetable. Meanwhile your 'source' says he can be AoE'd by a time bomb and etc.

Don't play dumb. You know exactly what you said.

The one who isn't making sense is you. You say he is invulnerable and doesn't exist in the game. Meanwhile he can be damaged. He can't be both.

SEKAIJul 22, 20171 votes

{quoted}

You said Yi cannot be damaged in alpha because he is untargetable. Meanwhile your 'source' says he can be AoE'd by a time bomb and etc.

Don't play dumb. You know exactly what you said.

"units will still suffer the effects of active applied damage over times (e.g. Ignite), delayed detonations (e.g. Time Bomb) and tethers (e.g. Drain)." Where does it say it applies because it's AoE?

And this section is dedicated to effects applied onto untargetable units PRIOR to going into untargetability rather than DURING it.

Please just stop.

rtbf221651412Jul 22, 20171 votes

{quoted}

"units will still suffer the effects of active applied damage over times (e.g. Ignite), delayed detonations (e.g. Time Bomb) and tethers (e.g. Drain)." Where does it say it applies because it's AoE?

And this section is dedicated to effects applied onto untargetable units PRIOR to going into untargetability rather than DURING it.

Please just stop.

Have you played video games before?

SEKAIJul 22, 20172 votes

{quoted}

Have you played video games before?

Is that even relevant? Because Riot says "mechanics A works a certain way here", it means it works a certain way here.

Nobody cares if Diablo's legendary weapon is colour coded with green or brown fonts, or this other game coded with gold fonts. It doesn't matter, now does it?

In League, if untargetability works in a certain fashion. It means it works that way here in League, and you just get used to it.

I mean seriously, wtf on you on about?

rtbf221651412Jul 22, 20171 votes

{quoted}

Is that even relevant? Because Riot says "mechanics A works a certain way here", it means it works a certain way here.

Nobody cares if Diablo's legendary weapon is colour coded with green or brown fonts, or this other game coded with gold fonts. It doesn't matter.

In League, if untargetability works in a certain fashion. It means it works that way here in League, and you just get used to it.

I mean seriously, wtf on you on about?

KARMA Tether isn't a targetable ability that lasts during the untargetability confirmed

rtbf221651412Jul 22, 20171 votes

{quoted}

You can't? You can only tether before they go on untargetability, which then it will hold for the duration unless you somehow leave the max range?

Stop.

Everything you say is contradictory.

Also you are saying stop and replying. Your actions and words are not lining up now.

The fact is I can still hit you with a tether and snare you as Karma even if you go invisible after.

I can Brand W you even if you go invisible as Shaco and Twitch.

EvilMerodachJul 22, 20174 votes

{quoted}

The only things that will affect an untargetable unit are DoT, delayed-damage/spell and tethers that are applied onto the said unit before they'd even gone into untargetability. Otherwise they should dodge everything else.

That's a false, false.

Weird shit like blitz e knockup will still apply, and it's not a bug. As long as he's already expended the buff (meaning he's already started to autoattack you), the knockup will go off, even if you go in Alpha and even if blitz dies mid-aa, as the buff is passed to you as a debuff (knockup charge~airborne debuff).

I know, it's weird as fk, but that's how it works.

Think of it like the q buff/DoT dmg Udyr does to you on AA. Would be weird if his q didn't deal dmg as long as he started windup on his AA, right? So, Blitzcrank E is coded exactly the same. Except his is a knockup other than a DoT dmg, but it's still applied to you as a DoT. But it feels TONS more painful for it to land than Udyr q to land, cause CC...

SEKAIJul 22, 20171 votes

{quoted}

That's a false, false.

Weird shit like blitz e knockup will still apply, and it's not a bug. As long as he's already expended the buff (meaning he's already started to autoattack you), the knockup will go off, even if you go in Alpha and even if blitz dies mid-aa, as the buff is passed to you as a debuff (knockup charge~airborne debuff).

I know, it's weird as fk, but that's how it works.

Think of it like the q buff/DoT dmg does to you on AA. Would be weird if his q didn't deal dmg as long as he started windup on his AA, right? So, E is coded exactly the same. Except his is a knockup other than a DoT dmg, but it's still applied to you as a DoT. But it feels TONS more painful for it to land than Udyr q to land, cause CC...

If that happens then it's a bug, as the untargetability is not working as intended. Because going untargetable also means incoming AA will miss, and Blitz's E is an AA mod.

Weird coding aside, I don't think it's how it suppose to work in the first place.

EvilMerodachJul 22, 20172 votes

{quoted}

If that happens then it's a bug, as the untargetability is not working as intended. Because going untargetable also means incoming AA will miss, and Blitz's E is an AA mod.

Weird coding aside, I don't think it's how it suppose to work in the first place.

Eh, well, I know it's weird coding, but it is how it's 'supposed to be.'

Stuff like Zilean bomb will still damage you, cause it's a 'debuff'. Blitz E is tec. a 'debuff' (as he has the knockup charge in his buff bar, and when AA'd you get a debuff from him).

But then Udyr E is not a debuff, so, yeah, it's confusing. (You actually get a 'buff' after getting AA'd by Udyr, which is the thing where he can't stun you again for a set time after).

Also most AA's won't fail after windup ends Kalista being an exception to pretty much every rule ever about AA's..but ignoring her...), even if you exit ability/range to be AA'd (AA's can follow you through recall...even some melee ones). Just untargetable gets a special buff where it 'pops' AA's, even melee ones..

But again, Blitz E isn't an AA, it's just an ability/debuff that replaces his AA for 1 attack.

SEKAIJul 22, 20171 votes

{quoted}

Eh, well, I know it's weird coding, but it is how it's 'supposed to be.'

Stuff like bomb will still damage you, cause it's a 'debuff'. Blitz E is tec. a 'debuff' (as he has the knockup charge in his buff bar, and when AA'd you get a debuff from him).

But then Udyr E is not a debuff, so, yeah, it's confusing. (You actually get a 'buff' after getting AA'd by Udyr, which is the thing where he can't stun you again for a set time after).

Also most AA's won't fail after windup ends being an exception to pretty much every rule ever about AA's..but ignoring her...), even if you exit ability/range to be AA'd (AA's can follow you through recall...even some melee ones). Just untargetable gets a special buff where it 'pops' AA's, even melee ones..

But again, Blitz E isn't an AA, it's just an ability/debuff that replaces his AA for 1 attack.

Fuck this game's coding then....

Like seriously, that means it's just a giant bug just sitting there because they're all clearly not working as intended/envisioned and/or defined (where they may look similar in practice but coded/treated as entirely a different thing).

Urgh

EvilMerodachJul 22, 20172 votes

{quoted}

Fuck this game's coding then....

Like seriously, that means it's just a giant bug just sitting there because they're all clearly not working as intended/envisioned and/or defined (where they may look similar in practice but coded/treated as entirely a different thing).

Urgh

lol, well, yeah...there's that.

https://www.youtube.com/watch?v=SW-BU6keEUw

Just shows how complex it really gets to squash a super old bug though. Fix one and either it breaks somehow else, or breaks 5 other abilities.

Though, that last Red post was 10 months ago, so...Riot could probably use a reminder that it's still there... Cause I'm not really sure if someone is actively working/thinking on how to fixing it anymore.

SEKAIJul 22, 20171 votes

{quoted}

lol, well, yeah...there's that.

https://www.youtube.com/watch?v=SW-BU6keEUw

Just shows how complex it really gets to squash a super old bug though. Fix one and either it breaks somehow else, or breaks 5 other abilities.

Though, that last Red post was 10 months ago, so...Riot could probably use a reminder that it's still there... Cause I'm not really sure if someone is actively working/thinking on how to fixing it anymore.

I definitely agree.

rtbf221651412Jul 22, 20171 votes

{quoted}

I'm telling you to stop, not me.

We call this double standards.

{quoted}

Invisibility is not untargetability.

Well yes it. Click where a teemo went invisible. Yeah, you can't auto attack that. If you say you can AoE Teemo, you'd be lying because you just said.

{quoted}

False. Untargetable means you literally don't exist in the game, in a way.

{quoted} 4. You can not land tether during untargetability frames, only before or after it. Yes it will last if landed before, but that's something I've said to you and not the other way around.

NO WAY. You don't say?

But if my Tether can hurt you, then my skillshots obviously can as well.

But you did say

{quoted}

False. Untargetable means you literally don't exist in the game, in a way.

Again, untargetability is NOT invisibility. And Twitch's is camouflage, which works different to invisibility, and neither is it a part of the untargetability.

You are right. You think it is:

{quoted}

you literally don't exist in the game, in a way.

Meanwhile, still waiting for you to click an invisible teemo without vision.

Auto attacks are clearly targeting based. Skill shots you can use to peel. You don't need to hit someone to use those.

SEKAIJul 23, 20171 votes

You don't have to waste server storage by continuing an utterly pointless drivel that we have before. But I'll bite.

Untargetability is not invisibility. I have no idea why you still have issues warping your head around this simple concept of A!=B, or A=/=B, where A is not equal to B and B is not equal to A. Like, it's like apples and oranges, it's really that simple. And because they are not the same thing, they have different in-game interactions defined for them. An invisible unit can still be hit (by for example AoE) while in invisibility, but an untargetable unit IN THIS GAME is not supposed to be hit DURING the untargetability frames.

You seem to be arguing purely on the literal basis that "because it said "untargetable", it must just meant that you can't be clicked on" or something like that. I mean what? It's almost like a game can have its own definitions and rules, what a shocker. There are other things in this game that is defined differently to other generic or typical definitions, are you gonna have issues with them too (such as idk, "lethality" that is just arm pen, "invulnerability" that isn't actually 'invulnerable', or things like "pure" damage being more powerful than "true" damage etc)?

Seriously, how is it that hard to understand. I don't get it.

Untargetability is on Fizz's trollpole or Vlad's pool or Mao's flying-thingy. Now recall how those work, or at least how they're supposed to work, and apply that onto Alpha Strike, because they're from the same mechanic category. Now that's a comparison.

Seriously, being untargetable is NOT being invisible. Those are completely different and unrelated mechanics in the game. Apples and oranges (seriously it's more like apples and hamburgers) are not comparable. That's it, end of your argument.

What, are you gonna be comparing stuns with roots, stasis with invulnerability, lasers with projectiles DIRECTLY? Because, yeah why not, they look similar to me so they must be the same, never mind the fact they are defined, played, treated and coded differently amiright?

..................

Though as elaborated upon, there are many bad codes in this game and things a lot of times don't really work as intended where many things while not technically bugs but they actually are as they are not doing what they're intended to do; but fixing the issue may be far harder than fixing the issue that come after the said fix hence things like Yi's Q is put on hold indefinitely for that reason (or excuse).

But that's another thing, for your comments, you're just flat-out wrong, unfortunately.

ParoeJul 23, 20171 votes

{quoted}

You don't have to waste server storage by continuing an utterly pointless drivel that we have before. But I'll bite.

Untargetability is not invisibility. I have no idea why you still have issues warping your head around this simple concept of A!=B, or A=/=B, where A is not equal to B and B is not equal to A.

And because they are not the same thing, they have different in-game interactions defined for them. An invisible unit can be hit while in invisibility, but an untargetable unit IN THIS GAME is not supposed to be hit DURING the untargetability frames.

You seem to be arguing purely on the literal basis that "because it said "untargetable", is it must just meant that you can't be clicked on". I mean what? It's almost like a game can have its own definitions and rules, what a shocker.

How is it that hard to understand? Seriously. It's almost like you've never played the damn game.

Untargetability is on Fizz's trollpole or Vlad's pool or Mao's flying-thingy. Now recall how those work and apply that onto Alpha Strike, because they're from the same mechanic category.

..................

Yi's Q has issues, this is the bottom line. There is no reason to contest it.

Though as elaborated upon, there are many bad codes in this game and things a lot of times don't really work as intended where many things while not technically bugs but they actually are as they are not doing what they're intended to do; but fixing the issue may be far harder than fixing the issue that come after the said fix hence things like Yi's Q is put on hold indefinitely for that reason (or excuse).

But that's another thing, for your comments, you're just flat-out wrong, unfortunately.

You know in the cosmic Yi skin how he leaves behind those after images? Yeah. Thats actually him coming OUT of untargetability.

Whenever he deals damage in alpha strike, he becomes targetable again.

SEKAIJul 23, 20171 votes

{quoted}

You know in the cosmic Yi skin how he leaves behind those after images? Yeah. Thats actually him coming OUT of untargetability.

Whenever he deals damage in alpha strike, he becomes targetable again.

No, he doesn't enter and exit untargetability frames 4 times each Q. He only does that once. And idk about after images, I thought only Project Yi does that as opposed to Cosmic Reaver, and no, it's just cosmetic.

He enters untargetability, he may as well be removed from the game for the time being (not exactly, but close to), and 4 units get struck during the time according to an algorithm, and Yi reappears back into the game (exit untargetability) next to his lock-on target (or if they die during the untargetability frame before it's completed, he appears at his casting position).

ParoeJul 23, 20172 votes

{quoted}

No, he doesn't enter and exit untargetability frames 4 times each Q. He only does that once. And idk about after images, I thought only Project Yi does that as opposed to Cosmic Reaver, and no, it's just cosmetic.

He enters untargetability, he may as well be removed from the game for the time being (not exactly, but close to), and 4 units get struck during the time according to an algorithm, and Yi reappears back into the game (exit untargetability) next to his lock-on target (or if they die during the untargetability frame before it's completed, he appears at his casting position).

Its not because the "bug" is repeatable with proper timing. When master yi "attacks" one of the targets, hes able to be hit.

... i should also be very clear. I agree this is unintended and needs to be fixed, however its just how the ability is coded. Its rather old.

rtbf221651412Jul 25, 20171 votes

{quoted}

You don't have to waste server storage by continuing an utterly pointless drivel that we have before. But I'll bite.

Untargetability is not invisibility.

Never said it was the same thing.

But you can't target someone invisible WITHOUT A WARD. That is how the game works naturally without warding. You can still AoE them. Targeting means point and click. Untargetable means not being able to do such a thing.

Of course you refuse to admit this because you want his bug fixed so bad you are willing to lie.

It's not about getting him fixed no matter what. It's about being factual while trying to get him fixed.

The word you are looking for is NOT untargetable. It's something more along the lines of dodging everything. Maybe damage immunity or even invincibility while invisible. Yes, both can exist at the same time. Or maybe damage immunity while dodging while invisible. Who knew?

SEKAIJul 25, 20171 votes

{quoted}

Never said it was the same thing.

But you can't target someone invisible WITHOUT A WARD. That is how the game works naturally without warding. You can still AoE them. Targeting means point and click. Untargetable means not being able to do such a thing.

Of course you refuse to admit this because you want his bug fixed so bad you are willing to lie.

It's not about getting him fixed no matter what. It's about being factual while trying to get him fixed.

The word you are looking for is NOT untargetable. It's something more along the lines of dodging everything. Maybe damage immunity or even invincibility while invisible. Yes, both can exist at the same time. Or maybe damage immunity while dodging while invisible. Who knew?

Can you just once for the love of god, read up how untargetability is defined and what it is supposed to do in this game, instead of conjuring shit up in the way you think it works and arguing to the death of you with it no matter what is actually on the table? We're going in circles because of you, come on.

Do you remember how Fizz's trollpole works or how Vlad's pool works, or Maokai's flying-root thingy? Those 3 are both untargetability just like Yi's alpha. "Untargetability" IN THIS GAME means exactly that, you can't be targeted. HOWEVER, it also includes ALL kinds of targetting methods, be it locational (such as AoE), directional (skill shots), lock on (AA and lock-on spells) etc. Being untargetable means all damage sources will be unable to locate you for the duration of that status, which is why I said "it's as if you don't exist in the game", because that's EXACTLY how it is meant to work. The only exceptions are effects that are ALREADY on the champion before they go into untargetability, as those spells won't have issues locating where the champ is, as they are already applied to begin with. How many times do I need to explain it to you, in full detail?

What even makes you think that "untargetability" only means you can't be right clicked or lock-on'ed in this game? Because you think so, as that's how you personally interpret the term nevermind the fact Riot is the one doing the definition here because it's their game? Again, can you PLEASE, just read up how a mechanic works in a game before you run into debates on it? But oh, you said: "The word you are looking for is NOT untargetable. It's something more along the lines of dodging everything." Yeah, except that's what untargetability is supposed to do here, for the very most part. I don't fucking even. Are you kidding me? Or are you trolling me?

This is why taking damage from AoE, skillshots etc during untargetability frames, are obviously not right and should be addressed. Hence why thread is born. This isn't even something new, it's just a reinforcement and a reminder on a well recognised problem that's been addressed by both players and Rioters many times already. This is just a "daily reminder" kind of thread. Even those (by that I mean the ones who actually know what they're talking about) who came in disagreeing with this thread only did so because of technicalities as that it is not really a technical bug in the code, hence it's working as "intended" in a sense, but rather it's a design and logical oversight/flaw at a fundamental level given how many things are weirdly coded and thus causing the mismatch between high level design and practice; so it's still wrong and need to be fixed, just not in the way I preached that it is wrong in.

Nevertheless, Riot still needs a reminder saying that a few issues like that is still there waiting to be fixed one day. Though given how badly this thread is doing, I guess someone else will do the reminder better than I do.

...............

You on the other hand, clearly have absolutely no idea what untargetability is even supposed to do, and no amount of explanations can convince you of the fact that you're just completely wrong in that regard. Why are you even here? I mean, look at me, I was corrected on a few minor flaws, and I accepted those corrections. What about you? Hell, this thread has been dead anyway, big props to you (and me). But why come back just to continue this shit?

rtbf221651412Jul 25, 20171 votes