PS4 version - latest (2.4.3?)
Burn sometimes increments stack count on creatures after their turn, and sometimes it doesn’t. If it fails to increase stack count, it will on the second turn taken. This only occurs for the transition of Burn to Burn1 (first stack accruement). This is intermittent. Invisibility (unsure if related) also has odd and similar behaviors with when it is removed (sometimes at the start of an enemy’s turn, sometimes at the end, sometimes not at all!).
Also, applying further Burn does not increment stack count.
What’s the intended functionality for this debuff?
Currently, I avoid using Burn because of the intermittent start up, and lack of ability to increase stack count with additional applications. The start up time to truly see damage (2 or 3 stacks) is simply not worth it.
New game, random creatures, castle quests on.
Creature: Pyromancer Efreet (starts with Burn)
Results: Facing two of these creatures, on turn 1 they both healed for 8 damage. When it was my turn, I hovered over the attack on each, one had Burn1, the other had Burn. Upon the second turn, Burn1 healed 16 damage and incremented to Burn2, Burn healed 8 damage and incremented to Burn1.
These should have been equivalent stacks.
This occurs when using an artifact or ability to apply Burn as well. Firewound Angel (Tier 1 creature) is another easy test.
Apply Burn to enemy. Enemy takes turn, takes x damage.
Second turn: enemy takes turn, takes x damage (instead of 2x damage)
Third turn: enemy takes turn, takes 2x damage (instead of 3x damage)
Lastly - the ability of Raging Efreet only uses the current damage of the Burn debuff, rather than the total damage the creature would take, then removes it.
A creature on Burn that takes 8 damage will take 40 from the removal of Burn (5 turns)
The same creature with Burn1 would take 16 damage will take 80 from the removal of Burn1 (again, 5 turns, but shouldn’t it be 4 now?)
It’s actually a bit counter-productive to attack a creature with Burn using Raging Efreet unless you’ll get an immediate kill via the buff removal. The ability states it would deal the full amount of damage of the debuff, but this isn’t the case. It actually deals (current debuff damage) x (debuff time (ceiling 10)). Or it possibly just assumes 5, regardless of actual debuff duration.
In the above example, the maximum damage with no additional input should be:
Sum of -