The IRON method
From report to impact
IRON NEST: Heavy Turret Simulator is built around a deliberate operator loop. The official store describes reading reports, plotting a target on the tactical map, solving firing data, operating the turret, firing, and reviewing reconnaissance. IRON NEST Wiki turns that broad loop into a set of short, inspectable procedures. Every IRON procedure keeps the source report, map result, calculator result, turret state, and impact note separate. That separation lets you find the earliest wrong value instead of guessing at the final control.
Start every IRON solution with the order. Identify the required effect and the target evidence actually present. If a spotter provides a bearing and distance, those values begin at the spotter. Project the target first. Then calculate a new IRON bearing and range beginning at the Nest. The two vectors may be very different. The planner makes this geometry visible, but it does not pretend to calculate game elevation from a disputed community formula.
Keep every IRON origin visible
An IRON map problem becomes fragile when a number loses its origin. Write 'spotter bearing' and 'spotter distance' beside observer values. Write 'Nest bearing' and 'Nest range' beside the firing values. Label target coordinates separately. This IRON naming rule catches the most common Mission 2 confusion before ammunition is committed. A bearing is not just a direction number; it is a direction from a named point.
Use clockwise bearings from north on this site. Zero points north, ninety east, one hundred eighty south, and two hundred seventy west. Check the cardinal direction before accepting a decimal IRON result. If the plotted target appears opposite the expected direction, inspect axis orientation, X and Y order, signs, and angle convention. Do not rotate the IRON narrative to excuse a calculation that fails a simple cardinal check.
- Mark the current IRON Nest position and map north.
- Mark the report origin before copying any bearing.
- Project the target and label the resulting coordinates.
- Measure the final IRON firing vector from the Nest.
Build one IRON firing card
Once target bearing and range are known, use the current in-game interface for shell, charge, and elevation. Keep all five firing fields on one IRON row: bearing, range, shell, charge, and elevation. The current official description confirms a combined total of thirty ammunition types and abilities, but it does not publish a verified split. IRON NEST Wiki therefore does not present a competitor shell count as official or invent a complete table from conflicting sources.
At the IRON turret, transfer one field at a time and verify the visible control after each change. An interruption should send you back to the start of the card, not forward from memory. Before firing, ask whether the direction makes sense, whether the range came from the Nest, whether the shell matches the ordered effect, and whether charge and elevation came from the same calculator pass. This short IRON check costs less time than diagnosing a contaminated result.
Correct the IRON chain, not the feeling
After impact, freeze the IRON firing state. Record the result as short, long, left, right, centered with wrong effect, or not observed. A huge miss suggests an early report, coordinate, convention, or gross transfer problem. A small consistent miss supports a narrower correction only after the earlier layers pass. A correct location with the wrong effect points toward shell role. An unobserved IRON result does not support a numeric correction.
Change one category per diagnostic IRON shot. Preserve the old row, state the reason, and predict how the next impact should move. If the shot moves as predicted, continue carefully. If it moves unexpectedly, return to the earliest assumption that was not directly checked. The dedicated missed-shot page expands this IRON ladder from source through turret and separates a normal operator error from a possible current-build issue.
Evidence before IRON certainty
Every material IRON claim on this site carries a source status. Official means the exact claim is supported by the current Steam store, official news, or a developer statement within scope. Community means a player guide or discussion identifies a useful technique or recurring problem, not an official rule. Unverified means evidence conflicts or current-client proof is missing. Stale is reserved for an older IRON fact that should not guide current play without rechecking.
The sources ledger exposes these labels, URLs, check dates, version context, and conflicts. Competitor pages informed private product research but do not serve as the game-fact source for public IRON content. This policy produces a smaller launch library, yet each IRON page is complete enough to use. It is better to publish eight finished routes than hundreds of thin URLs that create false confidence and waste search discovery.
Your private IRON planner
The firing planner calculates only deterministic map geometry. Enter Nest coordinates, spotter coordinates, spotter bearing, and spotter distance. The IRON planner returns target coordinates, Nest bearing, Nest range, and a plotted diagram. Optional shell, charge, and elevation fields create a copyable IRON firing card. All entries remain in the browser and are never sent to GA4 or a server.
Core IRON pages use a minimal page-view measurement so the site owner can see which completed guides are useful. The measurement excludes query strings, search input, planner values, form values, email, and user identifiers. The privacy page offers a persistent local opt-out. The IRON content and planner continue working if analytics is blocked or disabled. Open the planner for a spotter problem, the first-shot guide for the full workflow, or mission files for task-specific context.