Zed getting a damage buff?
Zed Shadow Slash (E) damage increased to 80/130/180/230/280 from 60/90/120/150/180
lol, okay.
Zed Shadow Slash (E) damage increased to 80/130/180/230/280 from 60/90/120/150/180
lol, okay.
gotta sell them project zed skins
seems very true and well timed... a little too well timed.........
inb4 after the initial rush of project skins are sold that they re nerf him
They'll changes it back 100%.
Sad but true.
NO, Riot Exgeniar has confirmed it is a bug Source: https://twitter.com/Exgeniar/status/634462130289246208
That's almost a double damage buff, however, on a thread in this same area, there is a Rioter post saying that it is a bug.
I think it's sad. Riot is not even hiding anything anymore when it involves big moneyz and LC$ Big PlayZZZ. RIP squishy mid laners.
Armor just got massively nerfed? Better buff the AD assassin with an AD deathcap on his W. ;~;
Zed isn't that bad, but does he really need these buffs?
Worlds coming up hmmm I wonder why they are buffing him.
I can see a reason for late game buff, but early game? the hell is that shit.
He doesn't really need a damage buff for late game though lol.
He needs nerfs before even considering buffing him even at his weakest point of the game or his strongest point of the game.
Anybody find (factual) context for this buff?
Surrender@20 is a very reliable website, also u can go on pbe and check if u have a pbe account.
I never thought zed needed dmg to kill people, even tanks once he gets bork and lw. Also he had once of the best waveclear's for an assasin, like wtf rito, any context for the buff?
i was coming to post this but good threads have already started. I mean i know new skin is coming out and worlds are coming up. Muh LC$ big PLAY$. but dang this is just disheartening along with armor nerfs
That is a surprisingly large late game buff.
Laughing my fucking ass off that sure was some "bug" they had there
A red already posted in another thread, it's a bug.
Riot confirmed it is a bug no zed buffs put your put your pitchforks away/ or find something else!!!
Was confirmed a bug