Guides
IRON NEST How to Move
Treat redeployment as a tactical support action, not ordinary vehicle driving.
Evidence map reviewed: Aug 9, 2026
Official FAQ material confirms redeployment; community discussion explains its counter-battery use without proving exact timings.
It is not normal driving
The IRON NEST can be redeployed through support orders, but movement is not a continuous vehicle-control loop. You issue movement information, then update the tactical problem after the platform reaches its new position.
Planned directional move
A normal Move Direction order uses a heading and distance. Plot that same heading and distance from the old IRON NEST position, then move the large map token to the new point. Because you selected the move, you should be able to preserve your own position without requesting new intelligence.
Normal movement changes tactical geometry. Moving closer can reduce the powder needed and shorten shell flight time; moving farther or sideways can reduce the amount of rotation between prepared targets. Community testing says this ordinary move does not itself reset counter-battery pressure.
Emergency Move
The counter-battery challenge includes a separate Emergency Move. Community reports describe it as a random relocation that pauses the threat and adds time rather than letting you choose an exact destination. Because the destination is not known in advance, the old map token becomes invalid.
Use Position Reports from logistics or field contacts to reconstruct the new location. A single bearing or range may only define a line or circle; combine two or more independent reports to find the intersection, just as you would locate a target.
After redeployment
- Establish the new IRON NEST position.
- Move its map token.
- Redraw every turret-to-target line still needed.
- Recalculate bearing and range.
- Reprint elevation cards when range or powder requirements changed.
A changed origin invalidates old firing solutions even when the target has not moved. The reported emergency-time bonus and exact behavior are community-observed and should be rechecked after gameplay patches.