Untargetability frames.

Seviel Vorose··1 votes·376 views

The untargetability frame "mechanic" (if it can be even called a mechanic at all) is the worst thing League could ever introduce back in the day. Why is it becoming even more popular now? Out of the 10 most recent champions/reworks released, 5 of them have this so called "mechanic" somewhere in their kit.

While it can indeed be a source of potential outplays, randomness also comes to play, and randomness doesn't define skill. A spell with this "mechanic", apart from its actual usefulness, also applies a certain amount of pressure on the enemy and forces them not to use their tools waiting for you to use your untargetability spell. The most frustrating this is that there is no actual punishment for incorrectly using an untargetability frame spell, as it is going to do what it always does anyway. But anyone else is punished for using a spell on that champion at the wrong moment.

I'm not saying to remove the "mechanic" from the champions who have it (even if removing it from the likes of Kled, Xayah and Kayn would be very healthy for the game), but stop abusing it now. Thanks.

P.s Mobility creep isn't a good thing too.

11 Comments

Khristophoros1 votes

Is it actually random when you decide to try and stun somebody when they have their invuln skill off cooldown?

TehNACHO1 votes

Okay so the problem we're dealing with is randomness because the champion used their untargetability at the right time and you happened to fire at that moment?

First of all, comparing Bronze Yis to Diamond Yis, where the former will just spam Alpha Strike whenever and just happen to dodge stuff, vs the latter almost always trying to react and predict to abilities and dodge them. If you have bad players that can't predict invincibility frames against players that aren't even trying to dodge skills intentionally, of course that's where your randomness comes from. Both players are just bad in this example.

Kled Telegraphed. How can you possibly tell me with a straight face there's an element of randomness to his Mount/Dismount mechanic? Xayah Basically Yi. As a carry, her Ultimate is her main defensive tool; she wouldn't blow it out of random especially since it's not actually that powerful. Unless of course you're bad and the Xayahs you are playing against are also bad. Kayn Also Yi. Actually, more Zed. Unless Zed's predictable Ultimate is also treasonous for you.

SEKAI1 votes

The worst part of untargetability frame is that it's literally and technically broken, by that I mean it doesn't function the way it is supposed to where you often you take a bunch of unintended damage over its frame duration even though they aren't supposed to hit by the mechanism's definition; the problem is so deep in the engine Riot has given up on fixing it ages ago, and so provalent literally no one knows wtf untargetability is even supposed to do (with the claim that it only avoids AA and lock-on damage being a popular belief, even though it's completely false).

What puzzles me is that despite the mechanic itself is functionally broken, I have no idea why Riot is still putting it in the champs instead of using modified version of stasis effect instead.

Khristophoros1 votes

{quoted}

The worst part of untargetability frame is that it's literally and technically broken, by that I mean it doesn't function the way it is supposed to where you often you take a bunch of unintended damage over its frame duration even though they aren't supposed to hit by the mechanism's definition; the problem is so deep in the engine Riot has given up on fixing it ages ago, and so provalent literally no one knows wtf untargetability is even supposed to do (with the claim that it only avoids AA and lock-on damage being a popular belief, even though it's completely false).

What puzzles me is that despite the mechanic itself is functionally broken, I have no idea why Riot is still putting it in the champs instead of using modified version of stasis effect instead.

This is not true. Hourglass and Bard ult provide invulnerability. It's possible to add that to Fizz, Yi, Vlad, etc... but they decided not to. So it's a design/balance decision.

SEKAI1 votes

{quoted}

This is not true. Hourglass and Bard ult provide invulnerability. It's possible to add that to Fizz, Yi, Vlad, etc... but they decided not to. So it's a design/balance decision.

While I'm not too sure about Xayah but Kayn has the exact same problem in his ulti as all the other older champs who have untargetability in their kits, that they take a lot of unintended damage during the frames.

I mean, at least do something, use alternative routes and ways to do it or something, instead of keep using the very same functionality that they know and has admitted to be fundamentally/technically broken and unfixable on their end.

Khristophoros1 votes

{quoted}

While I'm not too sure about Xayah but Kayn has the exact same problem in his ulti as all the other older champs who have untargetability in their kits, that they take a lot of unintended damage during the frames.

I mean, at least do something, use alternative routes and ways to do it or something, instead of keep using the very same functionality that they know and has admitted to be fundamentally/technically broken and unfixable on their end.

Riot would change it to work like Hourglass if it was unintended for the champs to be able to take dmg during those skills.

SEKAI1 votes

{quoted}

Riot would change it to work like Hourglass if it was unintended for the champs to be able to take dmg during those skills.

Maybe, but last time I checked, Yi could still take damage and potentially die from AoEs casted over the region Yi is doing Alpha Strike on, and Kayn can still be damaged and potentially die from hiding inside the target if they use their Hydra active.

Riot should get around it already...

Khristophoros1 votes

{quoted}

Maybe, but last time I checked, Yi could still take damage and potentially die from AoEs casted over the region Yi is doing Alpha Strike on, and Kayn can still be damaged and potentially die from hiding inside the target if they use their Hydra active.

Riot should get around it already...

The fact that they haven't done it indicates that they don't want to. It's a design choice that they made.

SEKAI1 votes

{quoted}

The fact that they haven't done it indicates that they don't want to. It's a design choice that they made.

No, they expressed that it's because the problem is unfixable, rather than they intending it to be the case. And this is why the continual usage of a known and admitted broken mechanic without adjustment or any alternative approach is just odd.

You can call it a design decision, I suppose, but it's still a shit one. It's like you continue to use that broken grill to cook burgers while knowing full well that it's not functioning normally and all of the meat cooked by it is barely cooked by the end; it will still be a "design decision" to continue using it anyway, but nonetheless a very bad one.

Khristophoros1 votes

{quoted}

No, they expressed that it's because the problem is unfixable, rather than they intending it to be the case. And this is why the continual usage of a known and admitted broken mechanic without adjustment or any alternative approach is just odd.

You can call it a design decision, I suppose, but it's still a shit one. It's like you continue to use that broken grill to cook burgers while knowing full well that it's not functioning normally and all of the meat cooked by it is barely cooked by the end; it will still be a "design decision" to continue using it anyway, but nonetheless a very bad one.

What they said was bullshit. They can easily apply invuln and immunity to CC to the champ.

SEKAI1 votes

{quoted}

What they said was bullshit. They can easily apply invuln and immunity to CC to the champ.

Hence the point. It's weird to keep using the package they know and has admitted multiple times to be faulty and unfixable while at the same time also don't seem to be using alternative methods to achieve what that package is meant to do, but that's what Riot seems to be doing with untargetability atm and idk what's up. Though it's probably because untargetability can still take damage from sources like DoT that was applied before going into untargetability frames, so you can't just throw in invulnerability, but still... at least try some alternative ways instead of keep using the same broken function that literally is not fixable would be nice.

More from Gameplay

More by Seviel Vorose