IRON NESTField Notes

Troubleshooting

How do I find my Nest after Emergency Move?

Emergency Move changed the Nest's position, and the new location is not immediately known.

Quick answer

After an Emergency Move, use multiple Position Reports from known map references and combine them to rebuild or narrow down your Nest position. Start with two independent reports and keep each one paired with its reference location. If the result is still ambiguous, get another independent report rather than assuming exactly two always produce one exact point.

Recovery workflow corroboratedCorroborated scopeChecked Aug 14, 2026

Multiple independent reports from known references are supported for recovering the Nest position. Two are a useful starting point, not a guaranteed exact solution; exact current semantics and costs are not confirmed.

Version context: Broad workflow corroborated in current post-Patch #4 discussion; exact version 1.0 (1618) report contract unresolved

Still uncertain

  • Exact version 1.0 (1618) report format, precision, and requisition cost
  • Exact bearing/range branch distribution in version 1.0 (1618)
  • Deterministic solver inputs, units, angles, precision, and edge cases

Evidence and verification context

  • Historical developer and community discussions: Demo-era explanations support relocation, known reference locations, and combining reports. They are historical support, not proof of the exact 1.0 (1618) contract.
  • Full-release pre-Patch #4 Phantom Battery material: Historically corroborates the broad relocation-and-report workflow. Its balance-sensitive mission details are not promoted to the current build.
  • Official Patch #4 notes: Establish version 1.0 (1618) as the current research baseline and record a Phantom Battery balance change, without locking down the exact Position Report contract.
  • Current post-Patch #4 community discussion: Research reviewed on Aug 14, 2026 corroborates the broad Emergency Move to multiple Position Reports recovery workflow without establishing exact report costs, formats, or balance values.

The broad workflow is supported, but the exact version 1.0 (1618) Position Report format, precision, requisition cost, bearing/range branch distribution, and deterministic solver contract are not independently locked down.

Recommended approach

  1. Request a Position Report

    Keep the complete report together with the known map location used as its reference.

  2. Get a second independent report

    Use a different known reference as a useful starting pair instead of forcing one observation into an exact position.

  3. Combine the observations

    Plot the reports together from their known reference locations and use their overlap or intersection to narrow down the Nest position. Add another independent report if the result remains ambiguous.

  4. Recalculate firing solutions

    Once the Nest position changes, do not reuse a firing solution calculated from the pre-move position.

Still stuck?

I only have one report

Keep it, then obtain another report from a different known reference. A single relative observation may not identify one exact position.

Two reports still leave an ambiguous position

Do not force one exact result. Obtain another independent Position Report and use the added constraint to narrow the remaining candidates.

I do not understand the report format

Do not convert it using an assumed unit or angle convention. The exact current-build format still needs a targeted in-game check.

An older source gives an exact requisition cost

Do not hardcode that value as current. The exact Position Report cost for version 1.0 (1618) has not been independently locked down.

Common mistakes

  • Losing track of which known location belongs to each report.
  • Treating one relative observation as an exact position.
  • Reusing a firing solution calculated before the Nest moved.
Why this works

Position Reports provide relative observations from known map references, so combining independent reports can reduce the possible Nest locations. Historical material supports the design, and current post-Patch #4 Phantom Battery discussion corroborates the broad Emergency Move to multiple Position Reports recovery workflow. This does not establish an exact solver contract or guarantee that two reports always resolve one position.