UNOFFICIAL GUIDE · Reviewed August 25, 2026 · Version 1.0 (1622) / build 24750322 / Patch #5 · Public evidence, no author gameplay test
UNOFFICIAL GUIDE
To triangulate in IRON NEST, match every bearing or distance to the named point it comes from, plot those constraints together, and keep only positions supported by all available information. Once the target is located, measure a new firing line from the current Iron Nest position.
To triangulate in IRON NEST, match every bearing or distance to the named point it comes from, plot those constraints together, and keep only positions supported by all available information. Once the target is located, measure a new firing line from the current Iron Nest position.
This is the same task behind searches such as “IRON NEST Heavy Turret Simulator how to triangulate”: combine the reports first, then build the firing line from your own position.
Use this order:
Write down three things for each report: the named origin, that origin's grid, and the unknown point the report is meant to constrain. Do not begin from the Iron Nest merely because that is where you are sitting. Version 1.0 mission text names Spotters and previously located reference points as origins for different reports. IN-GAME TEXT · build 24750322
A bearing gives a direction from its origin. A distance gives a radius around its origin. Two bearings therefore compare direction constraints; a bearing and a distance compare a direction with a radius; two distances compare two radii. Version 1.0 text contains all three input structures, including examples with two or three distances. IN-GAME TEXT · build 24750322
The constraints may support one candidate, no clean candidate, or two candidates. A double intersection is not permission to choose whichever point looks closer to a mission area. Keep both until another independent bearing, distance, task clue, or approved mission-specific fact removes one.
The build's text advises requesting additional intelligence when the solution is uncertain, without naming one universal card or selector. IN-GAME TEXT · build 24750322
After locating the target, measure bearing and range again from the current Iron Nest. An official 1.0 FAQ places these tactical-map measurements before calculator work, ammunition and charge selection, turret setup, and fire. OFFICIAL · 1.0 release period
This page stops at the handoff. It does not choose elevation, charges, ammunition, or the correction for a miss.
An origin is the known point from which a bearing or distance is reported. In IRON NEST it may be a Spotter, another named point, or a reference point you had to locate earlier. The unknown may be an enemy target, a later reference point, or the Iron Nest itself.
| Report | Named origin | Origin grid known? | Constraint | Unknown point |
|---|---|---|---|---|
| Bearing from Point A | Point A | Confirm before plotting | Direction from A | Target or reference point |
| Distance from Point B | Point B | Confirm before plotting | Radius around B | Target or reference point |
| Position Report from Point C | Point C | Confirm before plotting | Bearing or distance from C | Current Iron Nest |
The labels in your operation will be dynamic; the table describes the roles, not a reusable set of coordinates.
Three origin mistakes cause many apparently geometric failures:
| Input | Origin | Map shape | Possible candidates | Next check |
|---|---|---|---|---|
| Two bearings | Two independent known points | Two direction constraints | Usually one usable crossing; an uncertain or shallow crossing can be poorly conditioned | Confirm both origins, directions, and the crossing angle |
| Bearing + distance | One bearing origin and one distance origin | Direction constraint plus radius constraint | 0, 1, or 2 | Keep both intersections until another fact removes one |
| Two distances | Two independent known points | Two radius constraints | 0, 1, or 2 | Check both centres and radii; add independent information if two remain |
IN-GAME TEXT · build 24750322: Version 1.0 text supplies all three input structures. The 0 / 1 / 2 language describes their geometry, not a claim about how the UI displays candidates.
For two bearings, “independent” matters. Near-parallel directions magnify uncertainty. Build text warns about near-parallel bearings and chained measurements and describes Spotter accuracy as “within” or “up to” 0.5°, without disclosing the runtime cause. IN-GAME TEXT · build 24750322
Do not turn that boundary into a ritual of drawing exactly three lines for every report. It is a warning about margin and geometry, not a disclosed implementation recipe.
Some operations ask you to locate one point and then use that point as the origin for another report. Treat the result of the first step as an upstream dependency, not as a perfect new truth.
Before drawing the downstream constraint:
Version 1.0 text explicitly warns that error can accumulate across chained measurements. IN-GAME TEXT · build 24750322 That is why a small uncertainty upstream can become a larger search area later. It is also why a later mismatch does not automatically prove that the final report is wrong.
Use this as a diagnostic checklist, not a list of guaranteed causes:
If two candidates remain after those checks, keep both. The reviewed evidence does not establish a universal “nearer point,” “coastal point,” “mission-side point,” or fixed left/right choice. Nor does it establish that a Star Shell or reconnaissance asset will always settle every double intersection. REPORTED boundary · reviewed August 25, 2026
If the constraints do not meet, recheck the data and request additional intelligence rather than bending a line. A large miss is not proof of a drawing error, and a small miss is not proof of observation error.
For a mission-specific example of searching without complete intelligence, use the Counter-Battery artillery search rather than transferring its objective state to every triangulation problem.
A Position Report changes the unknown point. Instead of using known points to find an enemy target, it reports either a bearing or a distance from a named point or grid toward the current Iron Nest. In build 24750322, the card directly binds to a random report flow with both forms; the exact probability is not disclosed. IN-GAME TEXT · direct graph reference · build 24750322
A single bearing constrains direction; a single distance constrains range. Neither supplies a unique coordinate by itself. Two clear, independent constraints can intersect, but that does not mean any two reports will always locate the Iron Nest exactly. Repeated report types, parallel or shallow geometry, uncertain origins, or report margin can leave the result weak.
Emergency Move is an important use case, not a proven universal trigger. Do not assume the report is available only after a move, or that every mode follows the same timing. For the mission sequence that rebuilds position after moving, follow the Phantom Battery position-rebuild walkthrough; this guide retains only the reusable geometry.
Triangulation answers “where is the point?” Firing preparation asks a new question: “what bearing and range connect the current Iron Nest to that point?”
Re-measure from the current Iron Nest even when one of the original reports already contained a bearing. That original bearing belonged to its named origin. It should not be copied into the turret as though it came from the gun.
Your handoff should contain the selected point, the current Iron Nest location, the shot-specific bearing and range, and any remaining uncertainty.
The next process chooses the firing calculation, ammunition, charges, and turret setup. If the shot misses, return to the mission's own state and correction evidence; do not silently replace the triangulated point with a fixed solution from another run.
The examples below show different input structures. They are links to their mission owners, not coordinate recipes:
These pages can corroborate structure and supply mission-specific context. They do not make dynamic coordinates, bearings, ranges, charges, elevations, or timers reusable across operations.
Fact baseline: Version 1.0 (1622), build 24750322, Patch #5. The build was pushed on August 15, 2026; the shared game-data extraction was run on August 17; this page's evidence was reviewed on August 25.
The extracted text and direct graph references support named origins, two bearings, two or three distances, mixed constraints, chained points, stated bearing accuracy limits, requests for additional intelligence, and the Position Report bearing-or-distance output structure. They do not expose a reliable current-build table for pencil colours, map gestures, clipboard behaviour, deletion, or clearing.
Detailed map-tool footage reviewed for this guide is from the Demo. Two release-period videos had no transcript and supplied no factual claims. Community explanations identify problems but do not establish a universal selector.
Later patches may change map tools or report behaviour. This page does not present build 24750322 as the latest version on its publication date; it presents that build as the traceable evidence baseline used for the first edition.
Match each report to its named origin, plot the constraints, and keep only supported candidates. Then measure a new bearing and range from the current Iron Nest; a Spotter bearing is not the firing bearing.
Start at the origin named in the report. A Spotter bearing starts at the Spotter, a chained bearing at its reference point, and an Iron Nest measurement at the gun. IN-GAME TEXT · build 24750322
Two bearings compare directions; bearing plus distance compares a direction and radius; two distances compare radii. The latter methods can leave 0, 1, or 2 candidates.
Check origins, grids, report pairing, direction, and upstream points. Then ask whether the geometry is shallow or the information is insufficient; this is a checklist, not a guaranteed diagnosis.
No universal near/far, coast, mission-area, or left/right rule was established. Preserve both candidates and use an independent bearing, distance, task fact, or additional intelligence.
Not necessarily. One Position Report gives either one direction or one range constraint, not a unique coordinate. Two clear, independent constraints can intersect, but any two reports are not guaranteed to locate the Iron Nest exactly. IN-GAME TEXT plus qualified geometry · direct graph reference · build 24750322
Locating the target and building the firing line are separate. Re-measure from the current Iron Nest, then check mission state and correction evidence; a miss alone proves neither drawing nor observation error.
No three-line hard rule was established. Build text says Spotter bearings are accurate “within” or “up to” 0.5° but does not disclose a fixed offset or runtime distribution.
Reviewed August 17–25, 2026. Evidence types and dates are stated beside each claim above.
Version baseline: Version 1.0 (1622), build 24750322, Patch #5; later changes are not inferred from this snapshot.
Official: A release-period FAQ supports the overall loop; pre-1.0 developer advice retains its historical qualification.
In-game text: The build extract supports named-origin inputs, the stated accuracy boundary, additional intelligence, and Position Report's random bearing-or-distance output.
Observed footage: One reviewed demonstration is explicitly Demo footage and is not used to establish current Version 1.0 tool behaviour.
Reported: Community discussions and third-party guides identify workflows and failure questions, not proven current-build mechanics.
Unresolved: Current-build map-tool gestures, a universal double-intersection selector, Position Report timing across modes, and the runtime meaning of 0.5° remain unverified.
Spot an error or a post-patch change? This guide follows correctable public evidence — corrections update the page and its review date.