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
Basically, there is total unit HP pool which is amount of soldiers x HP entry.
While you cant see it in Rome 2, you should know how it works if you played Warhammer or later games.
When unit is attacked especially by ranged, it does not keep perfect track of how much HP each solder has left, instead it uses total HP and then randomly applies deaths.
The smaller unit size is, the more time it will take for soldiers to start dropping dead. This is why you often can see elephant take no casualties and then in few seconds most of them are dead.
I had a great example in Warhammer, in most extreme scenario, I took 60% of total HP of Greatswords before first one got killed and then next volley dropped like 25 guys.
In terms of double stregth units like First Cohort, they have exactly twice as much total HP as regular versions of them but due to that game has more leasure to distribute deaths.
So does that mean that the HP pool has to deplete before the unit starts taking casualties or are casualties assigned as the pool is depleted?
I've never seen a rule to it, outside of model count. Like in Warhammer, I sometimes see units not dropping until they really lose a lot of HP and sometimes there are people getting killed much sooner.