A repeatable mission method

Every IRON NEST mission presents a different tactical problem, but a stable mission routine keeps the work manageable. Begin by reading the complete mission order and every frontline report. Separate objectives from observations, and separate each observer origin from the Nest. A mission can feel like a turret challenge while the real difficulty is often information control. If you keep report values, plotted values, calculator values, and turret values in separate rows, the mission becomes a chain of checkable decisions instead of a memory test.

This mission hub does not pretend that a community database is a current game manual. It organizes verified official scope, clearly labelled community problems, and practical operator procedure. The official store describes a loop of reading reports, plotting on a tactical map, solving firing data, operating the turret, and reviewing reconnaissance. That loop is the backbone of every mission note here. A focused mission page is published only when it can explain a real task without inventing target coordinates or copying another site's table.

Before a mission starts

Prepare a clean mission record before opening controls. Write the mission name, objective language, map orientation, and current Nest position. Leave distinct rows for each source report and each target. A blank mission template may feel slower than immediate action, but it prevents values from one target entering the next solution. Confirm that north is visually clear and that your coordinate transcription uses the same decimal precision shown in the mission interface.

Review what is official and what is only an operator assumption. The current listing confirms fifteen regions and a combined total of thirty ammunition types and abilities, yet it does not provide a verified split. A mission guide should therefore describe shell selection by observable role and current interface labels, not by an invented master count. The same rule applies to formulas. When community formulas conflict, the mission procedure defers charge and elevation to the current in-game calculator while using transparent geometry for map plotting.

  1. Copy the mission objective exactly enough to preserve the required effect.
  2. Mark the Nest position and verify the map's north direction.
  3. Create one report row and one firing row for each target.
  4. Keep unverified assumptions outside the mission solution.

When a mission report arrives

Read the mission report twice. On the first pass, understand the tactical request. On the second pass, extract coordinates, bearing, distance, target description, priority, and timing. If a bearing and distance come from a spotter, they describe a vector from that spotter, not a firing bearing from the Nest. Plot the target from the report origin, then measure the final mission bearing and range from the Nest. This distinction is especially important in Mission 2, where players publicly report confusion about converting spotter data into target location.

Check the direction with cardinal logic before trusting decimal output. A mission bearing near zero should point north, near ninety east, near one hundred eighty south, and near two hundred seventy west. If the plotted mission target contradicts the narrative or sits beyond a reasonable map area, inspect copied signs, axis direction, and origin. Do not bend the mission narrative to fit an accidental result. The planner is useful because it performs only the geometry, shows the plotted relationship, and leaves the game-specific firing calculation to the current client.

The mission firing loop

A mission firing loop has five checkpoints: target plot, firing card, turret transfer, observed result, and correction. At the plot checkpoint, confirm target coordinates, bearing, and range. At the firing card checkpoint, confirm shell, charge, and elevation were taken from one current calculator pass. At the turret checkpoint, compare every control with the card. After firing, wait for mission reconnaissance and record the outcome before changing values. At correction, change the smallest category supported by the result.

Keep mission corrections conservative. A shot far from the intended area suggests a source, coordinate, convention, or gross transfer error. A small consistent miss suggests a narrower bearing, elevation, or range correction. An ineffective hit can indicate shell role rather than location. A mission timeout creates pressure, but repeated undocumented shots consume time and make diagnosis harder. One recorded loop provides a baseline. The next mission loop should state exactly what changed and why the expected impact should move toward the target.

  • Plot checkpoint: origin, target, bearing, and range agree.
  • Card checkpoint: shell, charge, and elevation share one calculation.
  • Turret checkpoint: displayed controls match the mission card.
  • Result checkpoint: reconnaissance is recorded before correction.
  • Correction checkpoint: one reason supports each changed value.

Write mission notes that survive pressure

Mission notes must be short enough to scan while operating. Use labels rather than prose: source, origin, vector, target, Nest bearing, Nest range, shell, charge, elevation, result, next change. Add target letters when a mission includes several batteries or waves. Never overwrite the first mission solution after a miss. Preserve it and create a corrected row so you can compare direction and magnitude. This makes the record useful even if an interruption causes you to forget the last control change.

Use explicit uncertainty. If a target label comes from a player discussion, mark it as a community note. If the current game interface confirms a coordinate, it can become a session fact for your private mission record, but the public guide still needs reproducible evidence before publishing that value. This separation lets the mission guide stay useful without presenting a single player's memory as universal. It also makes patch review easier because official scope, community demand, and current-client details are not mixed together.

Available focused mission guide

The first focused mission guide covers Mission 2 spotter bearing because public Steam discussion shows a specific recurring problem: players struggle to turn two spotter bearings into a target location. The guide explains origin selection, clockwise bearing from north, distance projection, target coordinates, and the final firing vector from the Nest. It provides an example that is explicitly labelled as an example rather than a real mission answer. You can enter current values into the private planner without sending them to analytics.

For any other mission, use the same mission worksheet and the first firing procedure. If a shot lands incorrectly, move to the missed shot diagnostic instead of searching for a magic coordinate. The site will not fill this hub with thin mission pages that repeat a title and guess at objectives. Thirteen finished routes are more useful than a large mission sitemap containing unsupported or empty pages. Each future mission guide requires a clear demand signal, direct evidence, and a complete operator procedure before it can be indexed.

  • Calibration Fire: community source status. Opening calibration mission and gunnery qualification.
  • Fire and Light: community source status. Early mission involving spotter bearings and target plotting.
  • Liberation: community source status. Campaign mission listed in the community medal guide.
  • Counter-Battery: community source status. Counter-battery mission with a time-pressure objective.
  • Iron Road: community source status. Campaign mission listed in the community medal guide.
  • Siege of Cartagena: community source status. Campaign mission listed in the community medal guide.
  • The Gorge: community source status. Campaign mission listed in the community medal guide.
  • Rock of Gibraltar: community source status. Campaign mission listed in the community medal guide.
  • Dead Reckoning: community source status. Campaign mission listed in the community medal guide.
  • Fire on Call: community source status. Campaign mission listed in the community medal guide.
  • High Tide: community source status. Campaign mission listed in the community medal guide.
  • Blind Fire: community source status. Campaign mission listed in the community medal guide.
  • Phantom Battery: community source status. Campaign mission listed in the community medal guide.
  • Final Harvest: community source status. Campaign mission listed in the community medal guide.
  • White Shells: community source status. Campaign mission listed in the community medal guide.
  • Skirmish - Challenge - Counter Battery Timer: community source status. Challenge Skirmish variant listed in the community medal guide.
  • Skirmish - Chill - Uncontested Front: community source status. Chill Skirmish variant listed in the community medal guide.

Start with the Mission 2 spotter guide when a report gives an observer position, bearing, and distance. Start with the firing guide when you already know the target coordinates.

After-action mission review

At the end of a mission, keep only the notes that explain a repeatable decision. Record which report field caused confusion, which plotting check caught an error, which shell role matched the ordered effect, and which correction moved the impact as expected. Do not turn a successful result into a universal rule if it depended on one map state or unverified assumption. The goal is a cleaner mission procedure next time, not a larger pile of numbers.

Before reusing a mission note after a patch, verify the parts that depend on the current client. Patch 1.0 build 1558 already changed several systems and corrected save and turret-related issues. A mission coordinate, interface label, or behavior may drift even when the general map method remains sound. Evidence dates on this site show when a public claim was checked. Your private mission record should likewise distinguish stable geometry from game values that may need a fresh reading.