-
Notifications
You must be signed in to change notification settings - Fork 2
Naming Conventions
Mike-MF edited this page Jul 16, 2023
·
3 revisions
All Units utilise the same naming convention:
PREFIX_COMPONENT_U_SIDE_SUBTYPE_TYPE
which translates to: TACU_BAF_U_B_Arid_Scout
If there are no subtypes, it can be ignored leaving you with:
TACU_BAF_U_B_Scout
Sides are;
- B = Blufor
- O = Opfor
- I = Independent
PREFIX_COMPONENT_V_SIDE_SUBTYPE_TYPE
which translates to: TACU_BAF_V_B_Arid_Assault_Boat
If there are no subtypes, it can be ignored leaving you with:
TACU_BAF_V_B_Assault_Boat
PREFIX_COMPONENT_G_TYPE
which translates to: TACU_BAF_G_Patrol
IF there are multiple sub-types in the same side then it can be added at the end;
TACU_BAF_G_Patrol_Arid
Groups do not need to mark it's "side" on the name as it will not conflict with others on opposing sides.