Developer map rules were compared with independent full-release player reports. Exact interface values and formulas remain unresolved.
A spotter report narrows down a target. It does not always give you one exact point. A developer explanation confirms that a range and bearing can produce two possible intersections, old information stays tied to the spotter's earlier position, and reported bearings include a 0.5 degree margin that can grow across several lines.
That explanation was written during the demo period. Full-release discussions describe the same basic routine, but old screenshots and exact UI values should not be assumed to match the current build.
Put every clue in the right place
- Copy the report before changing screens. Keep the target name, reporting spotter, clue type, and any note about movement together.
- Place the reporting spotter carefully. Use a sub-grid position when the report gives one. The centre of a large grid square is rarely precise enough.
- Draw the clue from the spotter. A bearing becomes a line. A distance becomes a circle. Both describe where the target can be from that observer.
- Look at the geometry before loading. Two bearings normally give one approximate crossing. A bearing and distance can give two candidates, and the developer confirmed that both may be valid.
- Check the age of the information. A report does not move on the map just because the spotter later moves.
- Confirm an uncertain point. The developer lists star shells, forward observers, and a recon plane as ways to resolve a derived location.
- Build the firing solution from the current Nest position. Full-release players repeatedly identify an old Nest marker as the reason a good triangulation still produces a bad shot.
Three limits that explain most bad intersections
A range and bearing may cross twice. When that happens, the map has given you two candidates rather than one answer. Use another report or a reconnaissance tool before spending the shell.
Old reports keep their original context. Record when the clue was received and where the spotter was at that time. Moving the marker later can corrupt otherwise useful information.
Bearings are rounded. The developer gives a 0.5 degree margin, which can turn a clean theoretical crossing into a small area on the map. A near miss does not automatically mean the whole method is wrong.
When the lines do not agree
Work through the smallest correction first.
- Confirm that every line starts at the reporting spotter.
- Check whether one clue is a distance. It should be drawn as a circle and may leave two candidates.
- Check whether the spotter moved after the report.
- Recalculate the firing solution from the current Nest position.
- Use reconnaissance to resolve the remaining uncertainty instead of inventing a centre point.
This same routine matters in Phantom Battery, where emergency relocation can leave the old Nest position on the map.
Sources
- Developer explanation of ambiguous reports. It covers two intersections, old intelligence, bearing rounding, and confirmation tools during the demo period.
- Steam discussion covering triangulation. A separate player walkthrough describes placing spotters and drawing bearing lines.
- Steam discussion covering the old Nest position. A full-release example connects a bad shot with an outdated Nest marker.
- Official Steam store page. Current product and release context.
The map rules and full-release reports were compared on August 22, 2026. Exact interface values, grid offsets, and a universal manual formula remain outside what the sources establish.