Devourer/Rageblade Bug

A Time Wizard·1/14/2016, 5:11:55 PM·1 votes·850 views

When using Sated Devourer and Rageblade, Devourer does not make Rageblade stack faster. I imagine because the second hit of devourer should proc onhit effects twice (including things like the cooldown for master yi's alphastrike going down by 2 seconds for the second auto) it should make the rageblade count 2 stacks, 6 stacks, 8 stacks for melee champions, but instead counts 2 stacks, 4 stacks, 6 stacks, 8 stacks. Is this intended as a nerf to devourer champions that use rageblade or just devourer not working?

3 Comments

Mundo1/14/2016, 5:47:04 PM1 votes

I dont think it should simply because the fact it stacks 2x faster as melee, so this would make it get 8 stacks in 2 auto attacks.

If Rageblade took 16 to fully stack, half for melee.. then it would be fine to proc on Sate imo. Its pretty much a 4 stack currently for melee and half that with Sated would be nuts.

Zombiemaster1/15/2016, 12:32:38 AM1 votes

It's intended. Generating stacks for Guinsoo's Rageblade is considered an "on-attack" effect rather than an "on-hit" effect, and Sated Devourer only works with "on-hit" effects. The difference between the two is that an "on-attack" effect will trigger whenever the champion attacks but before the attack deals damage, whereas an "on-hit" effect will only trigger when the attack actually lands and deals damage.

It can be confusing, but I think of it as similar to the extra bolts from Runaan's Hurricane. The phantom hit from Sated Devourer won't give you more bolts for Runaan's Hurricane, and stacking Guinsoo's Rageblade is coded just the same.