From Erfwiki
Revision as of 15:31, 20 May 2009 by (Talk)

Jump to: navigation, search

Proposed Canon

Move is a Unit statistic. For each point of Move, the Unit may enter an additional hex per Turn. For more details, see Movement.

Known Moves & Comparisons


Siege engines and other slow units would take "five or more" turns to reach Gobwin KnobErf-b1-p021aSame-site.PNG as of Gobwin Knob's Turn 3. If the distance to Gobwin Knob from the Coalition's starting point was in the realm of 25 hexes, that would put their movement in the 4-6 range, which seems about right when compared to Jack Snipe's move.

According to the RCC's map, the column stretched at least 18 hexes, possibly more. That would mean, for a speed 6 engine, 3 whole turns to catch up to the front of the column. This helps explain why, after Parson destroyed 40% of the seige, mostly from the front, that Ansom indicated waiting a day would increase the usable siege by ~ 600% - if, say, 5% of the original number were available during the first day of the siege, and another 30% were within range of Gobwin Knob for the next turn, that would explain the numbers and leave an additional 25% siege another day's travel behind.