Due to a sudden burst in spammer activity, account creation has been temporarily disabled. Sorry for the inconvenience to any new potential contributors.

From AGEWiki

In general, these parameters are defined for each Faction in the \GameData\Factions directory.

STACKS

Old Naming conventions

• LandHQsName Name that a stack will use if an HQ stack (= corps in AACW, i.e the subordinate of the highest hierarchy stack). If there is a ¤ in the name, then the leader name will be inserted. If there is no ¤, then a numeric will be put before the name. e.g Jackson's Corps or XV. Corps
• LeaderForce A force with a leader, any size. (DEPRECATED under new naming convention)
• ForceName A leaderless large stack but out of the chain of command (example WIA, there is no CoC)
• DetachName Same, leaderless but a small stack.
• FleetName A fleet of any size with or without a leader.
• GroupNumbering = 0 will use I. II. III.... for new group (= stack) names, = 1 will use 1. 2. 3....
• UnitNumbering = 1 will use 1. 2. 3.... for new unit names when the DB has exhausted all custom names, = 0 will use I. II. III....

New Naming conventions

As of September 14, 2010

• LandHQsName AS ABOVE: Name that a stack will use if an HQ stack (= corps in AACW, i.e the subordinate of the highest hierarchy stack). If there is a ¤ in the name, then the leader name will be inserted. If there is no ¤, then a numeric will be put before the name. e.g Jackson's Corps or XV. Corps
• ForceName AS ABOVE A leaderless large stack but out of the chain of command (example WIA, there is no CoC)
• DetachName AS ABOVE Same, leaderless but a small stack.
• FleetName AS ABOVE A fleet of any size with a leader.
• LeaderFleetName NEW A fleet of any size without a leader.
• Leader3Force NEW A large force, out of CoC with a 3* leader.
• Leader2Force NEW Same, 2* leader
• Leader1Force NEW Same, 1* leader
• Leader3ColoForce NEW A large force, out of CoC with a 3* leader, but if the region is colonial.
• Leader2ColoForce NEW Same, 2* leader
• Leader1ColoForce NEW Same, 1* leader
• ColoName NEW Small, leaderless Stack in colonial region.

• GroupNumbering = 0 will use I. II. III.... for new group (= stack) names, = 1 will use 1. 2. 3....
• UnitNumbering = 1 will use 1. 2. 3.... for new unit names when the DB has exhausted all custom names, = 0 will use I. II. III....

Note:  The parameter LeaderForce must be removed from the .fac files if you wish to use the
newer fields, e.g "Leader3Force", "Leader2Force", "Leader1Force"...

Note: Armies, as 'army HQ part of the CoC, as in AACW and NCP' have their names drawn from the field GHQInfos

Example from VGN local strings

fac_ForceName_GER = German Armee

fac_DetachName_GER = German Force

fac_LeaderFleetName_GER = ¤' Flotte

fac_FleetName_GER = Flotte

fac_Leader3Force_GER = ¤' Armee

fac_Leader2Force_GER = ¤' Korps

fac_Leader1Force_GER = ¤' Force

fac_Leader3ColoForce_GER = ¤' Armee

fac_Leader2ColoForce_GER = ¤' Force

fac_Leader1ColoForce_GER = ¤' Expedition

fac_ColoName_GER = Column

Units in privileged combine mode (an AACW division e.g)

• if LdrNameInHQ = 1, then it will uses strCombinedUnitWithLeader (read from the local strings) and insert the leader name in it. Example, Pickett's Division.

• Otherwise, 2 cases:
  • if the leader has a flavorname (defined in Model), use it (option very rarely used)
  • otherwise, use a free LargeCombiName (see faction file). See USA in AACW for example (as a side note, as the CSA is using LdrNameInHQ = 1, the LargeCombiName list is not used)