IRON NESTUnofficial Field Manual

Before you begin

Open the checklist when you need a stable sequence, not an answer. Mission information belongs to the current operation. Read what the teleprinter and mission materials provide before checking a box. A completed item means that you personally reviewed that stage; it does not mean the site validated your value or setup.

Keep Campaign and Challenge context in mind. Campaign provides the story route, while Challenge may vary targets. The same reminder can support both, but no stored checkmark should be carried forward as proof that the next run uses the same target, bearing, distance, charge, or elevation.

The seven-step mission checklist

Mission Checklist

0 / 19 complete

Before the Mission

Map and Fire-Control Preparation

Loading and Firing

After the Shot or Mission

  1. 1. Read the orderReceive the teleprinter order and identify the current objective before changing another station.
  2. 2. Review notes and intelKeep the relevant mission information together and separate stated facts from assumptions.
  3. 3. Work the tactical mapObtain the bearing, distance, coordinate, target, impact, or reconnaissance information required by the current task.
  4. 4. Transfer fire-control inputsCarry only the confirmed map measurements needed by the ballistic-calculator stage and read its required elevation output.
  5. 5. Prepare the gunComplete the developer-described ammunition, powder-charge, elevation, rotation, and arming stages for the current operation.
  6. 6. Fire and observeFire only after your own setup review, then use the mission's presented result or impact information for the next decision.
  7. 7. Complete and reviewConfirm the objective result, review the newspaper, and move to the next assignment or run.

These labels summarize the confirmed conceptual flow. They are not a complete control list and do not assert the exact layout of every station or button.

How to use the checklist

  1. Start a fresh checklist for the operation you are currently running.
  2. Mark an item only after you have reviewed that stage yourself.
  3. If a later value looks wrong, return to the preceding handoff rather than checking everything complete.
  4. Reset the checklist before a new mission or variable Challenge run when old completion state could mislead you.
  5. Open the relevant guide when you need concept help; do not expect the checkbox to supply a value.

The checklist is most useful as a pause point. It helps answer “Which stage did I skip?” It cannot answer “What number should I enter?” because that number depends on the current operation and evidence available in the game.

Browser-local state and privacy

Checklist completion is browser-local. There is no Field Manual account, server-side mission record, shared profile, or cross-device synchronization behind it. Another browser, device, profile, or private window can have a separate state. Clearing site data may remove saved progress.

Do not use the checklist as archival proof of a run. A checkmark records a local interface choice, not the underlying mission value, score, completion result, or game save. If persistence matters, keep your own notes outside the tool.

What the checklist cannot do

  • It does not read the game, save file, Steam account, or leaderboard.
  • It does not know the current mission target or whether your inputs are correct.
  • It does not recommend ammunition, powder charge, range, bearing, or elevation.
  • It does not calculate trajectories or replace the in-game ballistic-calculator stage.
  • It does not reveal mission walkthroughs, endings, controls, or variable Challenge answers.

Those limits are intentional. A simple local workflow aid remains useful without pretending to possess current-build mission data that the reviewed sources do not supply.

Frequently Asked Questions

It stays in the current browser. No account or cross-device synchronization is provided, and clearing browser site data may remove the state.

No. It does not access the game, save files, Steam account, mission state, or leaderboards.

No. It only organizes workflow stages. Bearings, distances, charges, elevations, and other values must come from the current operation and its confirmed interfaces.

Yes when old checkmarks could cause confusion. Challenge targets may vary, so a fresh local sequence is safer than treating a prior run as the current answer.

Continue in the Field Manual

Sources & verification

Frequently Asked QuestionsUpdated August 1, 2026 · Checked 2026-08-10Direct source