Desired behavior for above-max-HP units?

Elvish_Pillager · Post by **Elvish_Pillager** » June 20th, 2006, 4:12 pm

Currently, it seems that the following is the case:

- Being healed cuts HP down to the max.
- Taking damage from poison cuts HP down the the max (but doesn't reduce it further.)
- Levelling up (INCLUDING AMLA) cuts HP to the max.
- Taking damage normally leaves HP above the max.

While being in this state is hardly normal, the current behavior is quite ridiculous! I see two simple alternatives which I would prefer:

1) Units can't go about the max, ever.
2) Units above max HP can only lose HP; trying to gain HP (through normal means, like healing) does nothing.

Thoughts?

Website · Post by **Sapient** » June 20th, 2006, 4:36 pm

Currently it's unspecified behavior, so it may change from version to version without notice. However it would be nice to have a consistent behavior for certain abilities designed to allow hp to exceed max hp (for example the 'bloodlust' ability). Alternatively, one could argue that maximum really means maximum, in other words you should design these special units to start with hp(initially) less than max hp, or for their maximum hitpoints to increase as they are surpassed.

Post by **turin** » June 20th, 2006, 6:35 pm

Giving units intended to surpass their max HP less than max HP to start with is flawed. It would allow the unit to just sit in a village for a few turns and get up to its "real" max HP, when the intended behavior is the unit can only surpass the max by (for example) dealing damage in battle.

Post by **Darth Fool** » June 20th, 2006, 7:58 pm

Personally I like the elegance of having max HP mean what it says and not allow the HP to exceed it. An ability such could temporarily increase the max-hp, but I imagine that the WML to reduce it to its original value might be a little hairy, but I would prefer that to having a confused definition in the c++ code.