OK now that it’s gone, I guess we can discuss what we found out from the bug. I’m sure I’m not the only one toying with it to coax secrets from the coding behind the game.
Here’s what I got:
full hp of a plane walker is stored as 0 in the internal life counter. The displayed number is the result of taking that life counter and doing some basic arithmetic.
there is no safety checking in the life counter. It can go above 0.
there is safety checking in the display process. It will display max hp even if the internal counter goes above 0.
the only safety check on the internal life counter occurs when healing is used. After healing, the code checks if life counter is above 0, and will reset it to 0 if so.
creature life counters work as one would expect. They do not start at 0 for max toughness.
the game ends when the internal counter says so. The display is purely cosmetic.
It seems possible that all of the insights here may also be consistent with a “damage counter” implementation for HP tracking, which starts at 0 and increases when damage is taken, rather than a zero/negative “life counter”.
What we learned is D3 knew about this exploit and didn’t close it for a full set cycle. Allowing players to exploit the game during events to gain rewards. And before anyone says anything, I used the exploit once in story mode to take screen shots and show other coalition members when someone asked about it.