Ekko is obnoxious

arc95·Jun 4, 2015·1 votes·614 views

I havent been one to say a champion is op but Ekko is just ridiculous easily the most op champion i ran across since i started playing if he hits his stun its more or less a free kill... or your burning pretty much everything you got to get away... but more so his AoE is over the top he jumps into a fight and just melts everyone

he has more or less level mobility burst and level AoE/CC

holy crap he makes me wanna go uninstall and then install DOTA <--- I never will because League is life Kappa

but still how does Riot think he is fair/balanced i can tell you im dodging if he is picked by the enemy ill take the 10 lp loss and not waste a half hour of my life.

10 Comments

DrNovaJun 4, 20151 votes

If you are just going to run from champs isntead of learning to play against then, you arent going to improve

arc95Jun 4, 20151 votes

i dont have a problem playing against strong champs but... i dont see playing against a Ekko(in ranked, i would never dodge a normal game because of a champion) as worth it i would rather save my lp than just throw it away, more so if im taking my first dodge on it

DrNovaJun 4, 20151 votes

Or you could just learn to play against him.

Pick him up or play furing free week. I've played as him a shitload, and now I know clearly his limitations and weaknesses, and it is pretty easy playing against him.

dodge the Q, keep an eye when he W's, stay back far enough he cant E (unless his Q is down and he cant auto proc passive) And watch where shadow is. I do all these things because I understand the champ, and I havent lost a lane against him yet.

I also chase him when he leaves lane, warn my lane mates when he's mia. Normal things anyways, but ensures he cant feed off other lanes.

Poke poke poke, his heal only gives 4 seconds back, if he's slowly poked down, his heal is garbage.

arc95Jun 4, 20151 votes

i have also laned against him... i dominated him once and i lsot once... but his late game is ridiculous... If i can avoid playing against the Strongest champ(arguably broken) in league especially when i know more than likely he will get fed and carry(bronze)... like i said i'll play him in normal's all the time but in ranked i'll pass

DrNovaJun 4, 20151 votes

His late game isnt ridiculous if you dont feed him.

He's an assasin, who tend to be snowbally, and who tend to do high quick damage is they get late game items. So the norm.

However late game, if the enemy team is staying together and playing reasonable, Ekko will have a hard time assasinating anyone who isnt just horrible at positioning. He has a tiny little dash, and maybe his flash. Tans can take his burst, squishies shouldnt be near frontlines.

disregardableJun 4, 20151 votes

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

Yeah he's having a real "hard" time. That was clearly meticulously planned so I'd be outplayed so hard.

DrNovaJun 4, 20151 votes

lol. That ekko is way fed, jinx chased directly with his shadow, got hit by BOTH shots of his Q so his Ult ASLO procc'd his passive, and again, followed his shadow.

Like I said, he isnt ridiculous if you dont feed him. This Ekko is 16-4 with a full build and jinx was being foolish.

Take your bullshit somewhere else.

disregardableJun 4, 20151 votes

They're both full build, Jinx had a Banshee's, and it lasted a total of 1 second. It's about as foolish as standing anywhere on the map when Leblanc is in the game.

Ekko does not have a hard time assassinating anyone late game.

DrNovaJun 4, 20151 votes

Jinxs full build doesnt matter because it is all offence mainly, and she isnt attacking. You'll notice her Banshee's also is on CD already, so it gives no sheild, which wouldnt matter anyways as she got hit by both parts of his Q.

She followed in his trail, exact same path as the shadow which everyone knows hits hard, and got assasinated, by an assasin. Her own fault. She could have taken a perpendicular path to the shadow instead of following it perfectly, but she chose to ignore his obvious abilities and died because of it. Nothing wrong there.