Missions

IRON NEST Fire on Call

Answer Fire on Call by managing successive requests as independent firing cards, matching effects, and preventing stale dual-gun states.

Fire on Call is anchored by Answer Fire on Call and the gold award Iron Discipline. The operation rewards treating each request as a new state. Fast service comes from prepared workflow, not reusing a stale solution because the next call sounds similar.

Game: IRON NEST: Heavy Turret Simulator. Mission scope: AppID 2950790, Windows public 1.0, checked 2026-08-09. Request order, coordinates, target effects, and medal limits require current-run evidence.

Number incoming calls

For every dispatch, write sequence, caller/observer, target, measurement origins, effect, restrictions, and current priority. Mark it closed only when mission feedback confirms success.

If two calls overlap, keep separate cards and map layers. Do not combine a bearing from one with a range from another.

Build a rapid but complete card

Plot target, measure from the Nest, select shell and powder, calculate elevation, choose barrel, and verify arming. The compact pre-fire callout prevents a rushed cross-state error.

Preparation can shorten movement: keep notebook/map clean and know station locations. It cannot remove calculator/load dependencies.

Use two guns with explicit roles

A second barrel can support successive calls only when its target/effect is already confirmed. Label both rows with request number. Check individual shell, charges, elevation, and arming.

Shared rotation or linkage must be observed in the current state; do not assume every control synchronizes. Arm only what the active request needs.

Wait for call closure

After impact, read observer response. A correct shot may close the request or trigger another. If no progress occurs, decide between inaccurate impact, wrong effect, wrong target stage, or unread message.

Do not immediately consume a prepared contingency. A new call may invalidate it.

Recover discipline after a miss

Preserve the failed card and impact. Review direction separately from range and effect. Make one supported correction or rebuild completely if intelligence changed.

If the wrong barrel fired, reset the card/arming workflow before continuing. Crossed states can compound across multiple calls.

Research Iron Discipline

Capture the live medal rows after baseline completion. Possible themes—accuracy, time, expenditure, response order, assistance—must be isolated rather than inferred from the title.

Run the same call sequence when comparing results if possible. Record patch and all requisitions. Confirm the in-game gold before relying on the Steam notification.

Finish and report

Read the final newspaper and complete the transition. PATCH 1.0 (1558) fixed stale elevation/linkage after leaving a mission following a shot, so current public content is important for multi-call state reports.

For a bug report, include request numbers, exact last recognized call, two barrel cards, impacts, response, patch, and whether a crash occurred. This makes a “mission stuck” report actionable.

Continue to High Tide and update first because its end record received a dedicated launch patch fix.

Use a call-status board

Keep three columns: received, firing, and confirmed. Move a request to firing only when its card and barrel match; move it to confirmed only after the mission responds. If a new call arrives, place it in received without displacing the active one unless the dispatch explicitly changes priority.

This board exposes why a run stalls. A request left in firing may have a wrong effect or missed impact; one left in received may never have been plotted. It also makes dual-gun preparation safer because each load retains an owner. After completion, compare status transitions with the medal result. If a speed criterion exists, streamline travel and recordkeeping while preserving those gates—skipping confirmation can create a faster-looking but invalid run.

When practicing, speak the request number at each station. “Call three, right gun” is enough to stop a notebook entry, calculator result, or load from drifting to another objective. If an interruption occurs, return to the board and restart at the last verified gate instead of guessing where the physical mechanism was left. This protocol becomes more valuable as calls and prepared barrels accumulate.

Sources

Continue with another focused IRON NEST guide.

Missions

IRON NEST Blind Fire

Endure Blind Fire by making uncertainty visible, separating estimated target position from calculator precision, and using impact evidence methodically.

Missions

IRON NEST Calibration Fire

Complete Calibration Fire by learning the teleprinter-to-newspaper loop, checking one coherent firing card, and diagnosing first-mission stalls.

Missions

IRON NEST Counter-Battery

Solve Counter-Battery by separating hostile-fire evidence from the Nest firing solution, managing pressure, and verifying each battery response.