Dissolution of the flesh + eternal youth no longer working.
|
When using Dissolution of the flesh and Eternal youth combo no damage should be able to stop your energy shield recharge since you are reserving life not actually taking damage. This combination is used in order to cast life costing spells with quick recovery.
However it seems sometimes when I take a hit my energy shield recharge is interrupted for no reason. This only happens on some hits and not every hit. This happens in maps and ancestry arena and on any random source of damage. It feels like hits have something like a 10% chance to just stop life recharge. Last bumped on Aug 24, 2023, 1:26:12 AM
This thread has been automatically archived. Replies are disabled.
|
|
|
Bumping this as it is really problematic and is hurting my build a lot.
Any suggestions would be useful. |
|
"This is not and has never been true. You are taking damage, and the result of taking that damage is changed from losing life to reserving life. But reserving life can still make you lose life - if your maximum unreserved life drops below your current life value, you inherently lose life equal to the difference, because the current value obviously can't be higher than your max unreserved life. When this happens, you are losing life from taking damage, which is the condition that inhibits Recharge. | |
" I see what you are saying, this is not reflected in the community understanding of the mechanic. Usually losing life does not cause recharge rate to be interrupted which is why you can sacrifice and lose life though other effects without interrupting the recharge rate. The wiki itself states A character with Dissolution of the Flesh doesn't lose life from taking damage, but reserves life equal to damage taken instead. This means that the Life Recharge that Eternal Youth provides is never interrupted, and the player recovers a significant amount of Life per second (33.3% by default). I am shocked that to hear that it has always worked this way and I am a little bit confused as to way I am unable to find anything in the community about it. Thank you Mark I appreciate your response! |
|
|
I feel like the part of this that might be missing is whether or not you have Petrified Blood. Since Mark's reply indicates your maximum unreserved life dropping below you *current* life value, and Petrified Blood causes your current life value to not be your maximum life value, then you might not have your ES Recharge break if reserving life from your maximum does not put you below your current health.
| |
|
While petrified blood would make the issue less obvious. since you would normally be low life and thus not losing life when life gets reserved.
If I step into a map with a floor degen stepping on this normally stops energy shield recharge rate right? lets say I step on it without petrified blood and with full life the degen reserves my life and I lose life equal to the difference but my energy shield recharge from eternal youth is not interrupted. I am losing life to taking damage but energy shield is not interrupted? It is not quite as simple as reserving life below your current life causes you to take damage because we can test it and see that that is not the case. |
|
"I tested in-game and this behaviour with damage-over-time specifically is as you describe currently. This is a bug. The reason for the bug is that internally, taking damage from a hit and taking damage over time are handled separately, and the changes they make to life are similarly made separately. The code checking when life is removed instantly is only interrupting recharge if the source of the change is a hit, because normally that's the only kind of damage which can call that function. Similarly the code for checking when life changes over time is only checking whether that change is caused by damage-over-time, because hits can't cause that. However, the because reservations can't be fractional amounts, reserving life from damage-over-time is just tracked internally without changing anything until a full 1 damage has been accumulated and this is then used to change the reservation, and if your current life was already at the unreserved maximum, that is an instant loss of 1 life, but caused by damage over time. The loss of life is correctly marked as coming from damage over time, but because damage over time usually can't cause instant life loss, the code for instant life loss doesn't currently check for that cause as one of the ones that should interrupt recharge. This will be fixed at some point in the future, I don't know when. | |
" Thank you for all your help Mark! Even if it works in a way different then I thought I am glad I now understand what is happening. |
|
