Terrain details provide a certain level of asymetry to the movement costs that are required to enter or leave a hex. Often they apply just to the border of a hex, but they don't always have too. Movement costs are nearly always added to the cost that are created from moving from one terrain type to another - the exceptions are when an unit is running along a road or ferry where it will then be only required to pay the cost of moving along the road or ferry without any consideration of the surrounding terrain.
Detail Type: | Detail Graphic: | Movement Costs: |
---|---|---|
![]() |
Downhill: 5 |
|
![]() |
||
![]() |
Down Cliff: 32 |
|
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
||
![]() |
After all the terrain contributions are considered, if the movement order is for a walking style movement then the movement costs are multipled by two. Of course depending on the climate and terrain, this can mean that an unit might not have enough movement points to make a single legal move - in this case the unit is always allowed to make at least one move during each execution phase.