Skip to content

Riot Is this intentional?[weird bug(?) involving kills]

Byakuya Kuchiki··1 votes·498 views

Hey riot or anyone else reading this recently in my singed game I was proxying and tryndamere ran up to me and slowed me i was getting away from him so I executed myself to a tower. It gave tryndamere the kill so I'm assuming its because he slowed me (w) I was wondering if a status effect that did no damage was supposed to give the champion the kill if no one else damaged them?

3 Comments

ValyrianBlade1 votes

Yes, a slow will give someone kill credit.

Pretty much anything that gives a measurable impact will give kill credit / assist credit. E.g. if the adc is solo killing someone at full and thresh throws his lantern beside the adc to give the shield even though the adc is full health, thresh will still get the assist (he helped!! lol).

There are very few exceptions to things that will give kill/assist credit. One I can think of is providing vision (e.g. if I jinx ult across the map, the dude who warded the bush the enemy is recalling from isn't getting an assist).

With respect to logic of giving an assist on a slow: let's say you were taking damage during a tower dive but had enough health to escape alive. Then you got slowed under tower. You take an extra tower shot and died. That player just killed you, even if the tower did all the damage.

Frankly, executes have always bothered me. Still don't understand why it isn't just gifted a kill to the last player to have damaged the champion. I guess executes are part of the game though.

El Condor Pasa1 votes

{quoted}

Frankly, executes have always bothered me. Still don't understand why it isn't just gifted a kill to the last player to have damaged the champion. I guess executes are part of the game though.

Suppose champion X damages or CCs champion Y. 10 minutes later, Y dies to a jungle monster with no other interaction between any other champion. Is X awarded the kill?

ValyrianBlade1 votes

Yes (At least in my system).

My point being, there's such a huge discrepancy between early game and late game on what you get out of an enemy dying.

Getting a kill early won't even net you a Tier 1 tower. Your entire team could simultaneously get kills in each Lane for an ace at 4 minutes and you're still not going to get a tower off of it. Meanwhile late game an enemy could get executed and it could end up being the game (force the 5v4 base invade).

So I have no problems with executes late game - there's at least penalty to it. Early game though, an execute could be just as efficient as recalling (6 second cast time then healing in shop as opposed to respawning at full health and mana). It doesn't make sense to be that you can die and suffer no penalty for it (especially when you die to enemy towers or creeps, but even jungle mobs probably shouldn't be killing you. Either you misjudged your ability to fight it and whoever damaged you before put you in that situation, or someone actually killed you by for example shooting Dragon over the wall with a skillshot as you were running by at low health so Dragon would kill you).

I'll note that I also think the way death timers work is silly. They need some sort of scaling with number of deaths. I've always hated how the late game level 14 with dozens of deaths comes back considerably faster than the level 18 who just died for the first or second time. Timers should scale a bit less with levels/time and should incorporate number of deaths up to a maximum death time at each level/time. This alone would make executes more meaningful as any early deaths will cost you later.

More from Report a Bug

More by Byakuya Kuchiki