Iron Road is documented by Intercept the Iron Road and the all-gold award Crowned in Brass. Player searches often call it the train mission, but a search label does not establish a fixed coordinate, speed, or universal lead. Treat it as an interception whose target state can become stale.
2950790, Windows public 1.0, checked 2026-08-09. Exact timing and target path require live-run evidence and are not copied from Demo material.Establish the route and state
Read every dispatch for route references, observer positions, time/order, and target description. Plot static reference points first. Mark each target report with its sequence so an older location is not mistaken for the current interception point.
If the map shows movement, distinguish observed position from predicted position. Do not connect unrelated timestamps as if simultaneous.
Build an intercept, not a memory shot
Use current intelligence to select the point the mission intends you to engage. Community moving-target guides can provide experimental methods, but their lead values require matching patch and scenario.
Once the point is chosen, measure from the Nest and create a calculator card. If a later report changes the point, recalculate range/elevation and bearing; proximity does not preserve validity.
Prepare before the window
Requisition the required effect, decide barrel, and stage only after the target plan is credible. Count powder and set bearing/elevation against the same card. Leave enough time for fine adjustment rather than relying on a rushed salvo.
A second gun can hold a deliberate contingency, but separate its shell, charges, elevation, and arming state. Do not cross the two cards.
Read interception feedback
After firing, wait for observer/teleprinter response. Determine whether the shot was early/late along a route, laterally wrong, range-wrong, or effect-wrong. “Missed the train” is not a sufficient diagnosis.
For a controlled follow-up, change the variable supported by the report. If the target continues moving, rebuild from new state instead of applying a static correction to the old point.
When Iron Road will not progress
Check for a new dispatch, another target stage, incorrect shell effect, or unrecognized impact. Confirm the intended barrel fired. If the target seems absent, validate message order and mission start rather than searching for an old coordinate.
If a crash precedes inability to re-enter the operation, update to PATCH 1.0 (1558) or later public content and verify files. Preserve Cloud progress.
Crowned in Brass research
Capture all medal rows on the baseline completion. Test one factor at a time: timing, accuracy, shot count, requisition, assistance, or effect selection. The official achievement title alone does not reveal thresholds.
Record target-report sequence alongside the result. A gold route tied to one generated or patched timing state should be labeled accordingly.
A useful mission report
Include dispatch timestamps/order, selected intercept point, card, actual load, impact relative to route, mission response, patch, and medal result. Coordinates are strong spoilers and need current corroboration.
Continue to Siege of Cartagena after normal completion, and use Shot Corrections for one-variable adjustment.
Test movement without inventing a speed table
To study the target, capture two or more time-labeled observations from the same public run. Record how the game presents time and map position; do not estimate from video editing. A predicted intercept should be marked separately from observed positions and validated by impact or mission response.
Repeat the method only when the route and conditions match. Different phases may change movement or stopping behavior. If a community guide gives a fixed lead, use it as a hypothesis and compare its patch, origin, and target state with yours. A miss ahead or behind the route can refine timing only after lateral bearing and ballistic range are known good. This separation stops an aiming error from becoming a false movement formula and makes any eventual table reproducible.