Righteous Fire of Arcane Devotion Turning off when hitting 1 life even with ES.
Issue: Righteous Fire of Arcane Devotion Turning off when hitting 1 life even with ES.
Replication: While running a hybrid build, turn on Righteous Fire of Arcane Devotion then use a Coruscating Elixer to remove all but 1 life. Observe that Righteous Fire of Arcane Devotion gets turned off and you cannot turn it back on. Even after the flask effect has ended. You have to zone and rezone in order to turn it back on. Expected Outcome: While running a hybrid build, turn on Righteous Fire of Arcane Devotion, activate the Coruscating Elixer and it shouldn't do anything accept give you the bonus' that applied to the flask. Righteous Fire of Arcane Devotion Note: I believe that the issue is that anytime you are on 1 life it is turning off the Righteous Fire of Arcane Devotion. I also tested this by just taking CI and it will not let you turn on Righteous Fire of Arcane Devotion at all. I believe this does need to get resolved for it to be usable outside of a life build. This also I believe is an issue while running Zealot's Oath and using a Coruscating Elixer. Last bumped on Nov 28, 2024, 11:55:04 PM
|
|
Read the description.
Engulfs you in magical fire that rapidly burns you and nearby enemies. The effect ends when you have 1 life remaining. "That's one of the old weird RF features, should be intended considering GGG never addressed it. Last edited by MonaHuna#6449 on Nov 27, 2024, 10:02:06 PM
|
|
rf turns off and will not turn back on if u have 1 life no matter how much es u have its intended to be that way "The effect ends when you have 1 life remaining." the line dosent imply anything about es
|
|
I understand that but I feel like the transfigured version should work a bit differently to make it something unique and different. Either that or it should be when you hit 1 life and have no ES. Idk it's just kinda janky.
My major issue is that even when I did get my life back I wasn't able to turn it back on. I had to rezone in order to turn it back on. That's primarily what bug I was referring to. Last edited by Crymsix#0760 on Nov 28, 2024, 11:56:13 PM
|
|