Designer note

[michaelm75au]

When setting up unit type and suffix in the location file, please ensure that they are related.
I have comes across some units (Soviet Eng-Sapper I think) where the suffix is 72 (infantry) but the type is 10 (engineer).

In some corrective code, it looks like the unit has been corrupted and it changes the type to Infantry as that what the first part of the suffix says.

[JeffroK]

michael,

In a similar vein, what exactly do siffix's do?

Being a pedant I hate the incorrect naming due to use of suffixes.

[Mac Linehan]

Michael -

Your comments are always greatly appreciated.

Mac

[inqistor]

Is this even possible to set incorrect suffix in editor? That probably only could be done with text files.

ORIGINAL: JeffK

In a similar vein, what exactly do siffix's do?

Being a pedant I hate the incorrect naming due to use of suffixes.

It seems they add unit type, at the end of name (like Construction Regiment). Sometimes they also can change LCU icon (for example for SNLF)

[JeffroK]

To make myself clearerer.

We get 7th Hussars Regiment, maybe technically correct.

But it is a Bn sized unit and would normally be shown as 7th Hussars.

2/9th Jats Regiment, again a Bn sized unit as 2/9th Jats.

22nd Marine Regiment, blasphemy, should be 22nd Marines.

If I take out the Suffix, and it allows a blank entry, does it make any difference?

[michaelm75au]

It can. The code does look at some specific suffix entries for certain things.

Somethings which use suffix
un/pack times
combat/movement modes
changing opMode

[JeffroK]

Thanks Michael,

It wou;d be nice if the suffixes affecting those items were hidden, otherwise the British/Insian Army will suffer penalties sue to their different nonclementure.