Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This makes sense. This mechanic makes sense. From Roman legions to household men-at-arms and modern infantry regiments, order of battle is an administrative decision, not a battlefield decision.
At the scale where our decisions happen, a legion, battalion, what have you stays together and moves together, and has largely defined roles.
Example. The 23rd Infantry Regiment might break off little detachments during a battle for maneuvering, but such things are too small for the scope of Ara's simulation.
The 23rd Infantry Regiment might march and fight in a larger element with the 56th Infantry Regiment for a time or an operation, but ultimately they're two different components of the order of battle whose internal structure stays more or less the same throughout the operation.
Thus, the system as it stands makes sense. You shouldn't be able to just "mix and match" on the fly, as they say. I'm all for refactoring, but it should be a weighted decision that at the VERY least takes a couple turns of re-mustering and has to happen inside a city center. You shouldn't be able to make such decisions on a whim.
Yes. Correct. And of course you must make a decision - make fewer larger divisions or more smaller battalions and squads - which you may stack/unstack any moment.