"If you decide to block Urgots chains with Braum Wall, you die"

StigtriX·7/26/2017, 8:23:26 PM·7 votes·2,780 views

https://twitter.com/RiotMEMEMEMEME/status/890253269712355328

I feel this is a bit too overpowerd in teamfights. I would be fine with Urgot raging and getting half the cooldown refunded if it was blocked by a wall (Braum/Yasuo), but this is a bit too much.

https://twitter.com/RiotMEMEMEMEME/status/890255795153059840

It makes sense on your paper, but in-game, I think a lot of players will be baffled by the interaction. It feels unjustified that Braum just goes down from 100% to 0% just like that.

62 Comments

TehNACHO7/26/2017, 8:32:47 PM8 votes

When was it ever OK to one-shot a champion without any effort?

Urgot had to ult somebody that low. Expending your Ultimate ability as well as (most likely) fighting a guy to low health is not the same as "one-shot a champion without any effort".

The counterplay is to either dodge or bodyblock his Ultimate's FIRST shot, or don't pick dumb fights that will leave you low and executed.

EDIT: Good to see the post rewritten.

koshkyra7/26/2017, 8:58:16 PM6 votes

So this has to happen to Braum but not Yasuo? Wtf?

I get that yasuo blocks it in a different way but i think 95% of us would love to see this the other way around.

Funkin Dunkin7/26/2017, 8:34:04 PM5 votes

There's actually a TON of ways to avoid his chains, for many champions. Be lucky his initial hit isn't a suppression

Joxcab7/26/2017, 8:30:12 PM4 votes

Because that only happens if he intercepts the second projectile.

Urgot's R2 executes whoever it kills instantly. However, that's balanced by the fact he can only activate it in the first place at a certain health threshold.

However, you can consider Urgot's R2 to do 100% maximum health true damage. By intercepting R2 and being the one to be dragged instead, Braum bypasses the health restriction (since R2 was reactivated on the low health target) and thus takes the damage himself of said full 100% maximum health.

SEKAI7/26/2017, 10:08:13 PM4 votes

I am not too sure why everyone is saying that's okay.

Because the problem is that you can simply use a dying character as an excuse to execute another high-HP frontline character in the middle of a teamfight. Because to prevent 1 shotting after R is landed, someone HAS TO die, it's just a matter of who, and if the dying character happens to be behind an ally, that ally has to avoid their dying teammate or else they will be the one to die instead.

This is a really bad interaction. Because not only does it encourage the players to abandon their teammates, but that's minor, the biggest problem is that it makes teamfighting incapable to be stalled and worse, Urgot can kill your entire team as long as he lands a single valid R. It is not just a ranged execution, it's that once it's valid and due to its 2 stage mechanic, you have to disrupt your own team formation to prevent further damage done by potentially sending another full HP teammate to die as opposed to the one that's already on the brink of dying; and what do you get for being disrupted, enemy team can just rush you for being out of position.

It's a single-target execution that can very well be an execution of an entire team if landed correctly, purely because of the fact "anybody can take the guy's place", and its difficulty is about the same as landing Lee's Q or Biltz's Q, which let's face it, is not very high.

It's like Blitz's Q doesn't actually pull the target after contact, but it's a tag, and pulling only happens 2 seconds after the tag and it autopulls any champ in the line between himself and the tag, the first champ would be grabbed and insta killed regardless of whether or not they were even the ones initially tagged or how much HP they have. Just on a higher CD.

So it creates these dynamics: Yeah let's just land it on their dying player and voila, we insta killed their frontline because they can't get out of the teamfight too so we win as they now have no frontline. OR Yeah let's just land it on their dying player and voila, they are all out of position now because nobody wants to take the dying player's place, so it's clean up time.

A spell that's doing way more than it's actually intended to do is a problem, don't you think?