Bug: Reassigning units

[Mobhack]

Units don't have a "number" - they are numbered in the sequence they appear in the list of 500 units. Formations are also listed in order of the master list. The list is basically an ordinary C++ array.

Sometimes there may also be a gap in the list - due to removal of a formation, or deletion of units. The insertion of a new unit into a vacant slot way up the list sometimes will do odd things to numbering as well.

It is structural with the way the original SSI code was written.

Also - the formation command unit is not always the 0th unit, in a campaign, if the command unit was killed and another of the formation took over.

Cheers
Andy

[scJazz]

Originally Posted by Mobhack

Units don't have a "number" - they are numbered in the sequence they appear in the list of 500 units. Formations are also listed in order of the master list. The list is basically an ordinary C++ array.

Sometimes there may also be a gap in the list - due to removal of a formation, or deletion of units. The insertion of a new unit into a vacant slot way up the list sometimes will do odd things to numbering as well.

It is structural with the way the original SSI code was written.

Also - the formation command unit is not always the 0th unit, in a campaign, if the command unit was killed and another of the formation took over.

Cheers
Andy

I understand what your saying. Still, if a unit knows that it has been reassigned to the "D" formation then it is possible to know that before the assignment there were X units in that formation. You would have to walk the Unit Arrays "Name" field to determine what X happens to be. Doesn't seem to be that big a deal. Doable?

And yes I know about the command unit not always being 0th in a campaign I have this handy sticky note on my monitor to inform me of each instance where this is now the case in this campaign. Handy thing to have when I do stupid stuff and get my platoon and company commanders killed