Chance to not Destroy corpses not applying to Warcaller's Bellow

Bug Report Reference number: 2,495,274,964

Bug: Warbringer's "Warcaller's Bellow" along with spirit gem "Sacrifice" and "X% Chance to not destroy Corpses when Consuming Corpses"

When you use a warcry to blow up your minions by using the Sacrifice gem, they always get blown up. With the passive skill "Meat Recycling".

Harder to test if it doesn't work versus regular corpses but anecdotally I've not noticed being able to blow up regular corpses twice.

Adding on to this: Minions you use Warcaller's Bellow on will still instantly die even if you have the minions linked to Last Gasp support, which prevents supported minions from dying for 4 seconds after their life is reduced to 0.

Bump the original post/problem.

I do not think Last Gasp is a "bug", I just think warcry explode applies "death" effect on minions, hence their life never reduces to 0 in truth game wise.

But there is most definitely a "bug" (or labeling matter) with the corpse consume. It is very easy to test out, in case devs cannot test it, I am happy to put video up on reddit.

All you need to do is put 10+ skele warriors on and equip wand with 25% chance to not consume corpse and take another 25% chance from tree, none of your warriors will ever stay up, even with 50% chance. (Also, it is impossible to socket 25% chance to not consume corpses support gem into warcries when ascendancy is allocated, which would be pointing into the direction, that this "bug" is just a labeling issue, in game labeling tags, warcry is not considered "corpse consumer skill", even when you have ascendancy/deidbell on your head.)

I was waiting for the most recent patch notes to pop to see if devs find this bug out from other sources, but after combing trough the list of fixes, I see there is zero mention about fixing this.

It would be neat if it would be still possible to get fix for this for the upcoming patch, as I take it, that it would not be a big thing, as warcries are only missing that label, nothing else seems to be wrong.

Anyone with same problem, pls bumb this up so devs would note it in time. Thanks for it and to devs for their hard work, hoping you could do this one still, if you only have time.

With appreciation,
TheSperg