Mother's Embrace + Coruscating Elixir doesnt trigger Minion Instability
This should work, The Belt states 'minions use your flasks when summoned' but they seem to have the flasks applied to them before they are summoned denying the low life trigger check to ever happen.
Last bumped on Mar 9, 2020, 10:28:33 AM
This thread has been automatically archived. Replies are disabled.
|
![]() |
I had the same bug occur. It seems like the minions are spawning with low life and not being lowered after the fact. The proper interaction should be more in line with Umbilicus Immortalis but it isn't for some reason.
|
![]() |
Not sure if this is getting addressed, and I know you guys have a million bugs to deal with, but I was so looking forward to making a build with this. If I could at least get confirmation that this is a bug that would be great.
|
![]() |
Steps to reproduce:
1.) Equip Mother's Embrace, and Coruscating Elixir. 2.) Summon ANY minion 3.) Double check you have allocated minion instability. 4.) Summon another minion. 5.) Watch as nothing explodes. Side note: I noticed that flask effects that are the same also don't stack. For example the degen from Forbidden Taste. Is this also intended? |
![]() |
Just bumping as I just built a character to test the interaction.
Null's inclincation Stone golem Mother's Embrace Coruscating Elixir Minion instability Minion is summoned correctly by on kill trigger, raises with 1 HP due to coruscating, but does not explode. |
![]() |
Ya Im trying to kill my skeletons more quickly with this and its sadly not working. Even if they spawn with 1hp and then die, they do not explode and just disappear. Honestly really disappointing the interaction doesn't work.
|
![]() |
Ya Im trying to kill my skeletons more quickly with this and its sadly not working. Even if they spawn with 1hp and then die, they do not explode and just disappear. Honestly really disappointing the interaction doesn't work.
|
![]() |
Noticed the same when trying to build around the new belt.
Really disappointing if this is the intended behaviour, hoping it's just a bug that will get adressed soon. |
![]() |
I'm surprised there's still been no comment on this officially. I would like to think this is an easy thing to fix, let alone confirm it's a bug.
|
![]() |
Does this interaction work now or is it still not fixed?
|
![]() |