User Tools

Site Tools


army-management

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
army-management [2022/01/26 15:05]
dude Some more rewriting
army-management [2022/12/25 00:19] (current)
dude simpler example
Line 9: Line 9:
   * Rear to retreat: 10 tiles   * Rear to retreat: 10 tiles
   * Rear to enemy rear: 60 tiles   * Rear to enemy rear: 60 tiles
-  * Rear to enemy front((and Front to enemy rear)): ~43 tiles+  * Rear to enemy front: ~43 tiles 
 +  * Front to enemy rear: ~43 tiles
   * Front to enemy front: ~26 tiles   * Front to enemy front: ~26 tiles
-  * Province defence will always spawn at the middle of the placement area as a blob. With command to attack((or fire)) immediately.+  * Province defence will always spawn at the middle of the defender placement area as a blob. 
 +  * Sieges use the same size map, but there are walls in the middle of the map, equal distance from attacker and defender, that limit the battlefield width to units. Ethereal units can pass through the walls, however. 
 + 
 +From simple observation, it can be seen that combat speeds translates to around 3/4 tiles moved per point. For example, in one combat turn heavy cavalry (speed 20moves about 15 tiles (20*3/4=15).
  
 The Table below shows the layout, with the X's indicating the corners of the deployment zone. The Table below shows the layout, with the X's indicating the corners of the deployment zone.
army-management.1643209551.txt.gz · Last modified: 2022/01/26 15:05 by dude