Berserker, just to make sure we are on the same page - we have a full set of stack exp management with HE:C commander by using the #4/#5 parameters. The discussion is about the scenarios when these two parameters aren't presented.

Quote:wog native behavior was if you add some creatures to a stack, the exp per creature should be dropped.

Yes, this is correct and expected.

Quote:As I understand, it's the simplest solution to keep int32 stack exp value unchanged by default; otherwise, any change should involve whole stack exp recalculation.

So, keeping the total exp of a slot is coding-wise easier?
Well, wog team implemented tools to keep the stack exp for each unit. For example, the line for taking out one creature for henchmen is:
It can be changed to
in order to keep the same stack exp for each unit.

My idea is, it would be better to have "keeping same stack exp for each unit" as the method for HE:C without #4 and #5 parameters. The current implementation is quite unexpected and multiple scripts have used it in a wrong way.