Shiv doesn't get back Killing Blow charge on Victor Kills

[BoschyBee]

If you have Shiv ult at max level it is supposed to reset after a "finishing off an enemy" with the ultimate. I know if we want to get pedantic Victor technically wasn't killed, but this feels more like an oversight.

View attachment 2025-11-10 08-21-39 (online-video-cutter.com).mp4


Again I know technically you haven't killed Victor, but you have done lethal damage. I would argue that should be considered a "Killing Blow" (ha)


Current behavior:
Using Max Level Killing Blow on Victor (who has Shocking Reanimation up) doesn't reward or reset Shiv's Killing Blow. It currently acts as if you used it on an enemy outside the instakill threshold or didn't instakill them — despite technically insta-killing Victor by inflicting lethal damage.

Expected behavior:
Using Max Level Killing Blow on Victor (who has Shocking Reanimation up) should reset Shiv's Killing Blow like any other kill. Alternatively it could be reset with more charge for the kill. (It currently resets back to 0%)

 

[BoschyBee]

Also yes I know stuff like Trophy Hunter also doesn't proc on Victor kills if he reanimates, but that specifies "Score a Kill or Assist". Shiv's Ultimate suddenly not working in a teamfight because the targeting switched to Victor at the last second and then punishing the Shiv player for successfully landing the instakill (again it still is proc-ing the instakill effect as if it should count) by putting Killing Blow on max cooldown seems like unintended behavior.

 

[pep]

Also yes I know stuff like Trophy Hunter also doesn't proc on Victor kills if he reanimates, but that specifies "Score a Kill or Assist". Shiv's Ultimate suddenly not working in a teamfight because the targeting switched to Victor at the last second and then punishing the Shiv player for successfully landing the instakill (again it still is proc-ing the instakill effect as if it should count) by putting Killing Blow on max cooldown seems like unintended behavior.

as you mentioned im pretty sure its coded so that abilities/items like TC and talon owl on t3 dont give stacks on vic kill, for TC it does make sense since you would be able to get 2 stacks easily

 

[daavimachaado]

intended