Intel begins before calculation
IRON NEST intel arrives as command intent and frontline observation before it becomes a firing value. The official gameplay description centers reading High Command and frontline reports, plotting on a tactical map, solving firing data, operating the turret, and reviewing reconnaissance. Treat intel as the first control surface in that chain. If the intel is copied incorrectly, perfect geometry and perfect turret transfer will still produce the wrong action.
A reliable intel workflow separates what must happen from what was observed. High Command intel usually frames the objective, priority, or required effect. Frontline intel may provide a position, bearing, distance, target description, or result report. Keep those categories in separate rows. Do not let a tactical request become a coordinate, and do not let an observer description become an official mechanic. Intel remains useful when each field keeps its source and scope.
Work two information streams
Think of the two teleprinter streams as order intel and observation intel, even if the current interface presents them with different labels. Read both before moving to the map. Order intel answers which target matters, what effect is requested, and whether timing changes priority. Observation intel answers where evidence points and which report origin produced it. A firing card needs both streams, but it must not merge them into one untraceable sentence.
Create an intel header with mission, target label, time received, source, and status. Under order intel, capture objective language and effect. Under observation intel, capture origin coordinates, target coordinates when present, bearing, distance, direction convention, and descriptive cues. Unknown fields stay marked unknown. This intel structure prevents a previous target, old report, or remembered guide from silently filling a blank in the current mission.
Use clipboard discipline
Copy intel in short labelled groups rather than one long block. Preserve the source label beside every numeric value. Write 'observer A bearing' instead of 'bearing,' and write 'Nest range' instead of 'range.' If the game requires manual transcription, point to one intel field, enter it, then compare the visible destination before moving on. This method is slower for a few seconds and much faster than tracing an unlabeled number after a miss.
Never overwrite the original intel row. Create a derived map row for calculated target coordinates and a firing row for Nest bearing, Nest range, shell, charge, and elevation. If intel changes, start a new row with a timestamp or sequence label. The old intel remains evidence for why the previous shot was taken. This separation supports correction without pretending that a changed report confirms the original one.
Keep coordinate origins attached
Origin control is the central intel rule. A bearing from a spotter begins at that spotter. A bearing from a second observer begins at the second observer. A firing bearing begins at the Nest. Intel that includes direction but omits origin is incomplete for calculation. Before plotting, circle or label every origin and connect only the fields that share that source. The map triangulation guide shows how those intel fields become stable geometry.
Run a cardinal intel check before accepting any decimal result. Zero points north, 90 east, 180 south, and 270 west in the Console convention. If intel says a target lies east but the plot moves west, inspect axis direction, signs, and angle convention. Do not assume the report is wrong until transcription is checked. Do not assume the tool is right if the entered intel came from the wrong row.
Move intel across the map table
The map table converts source intel into derived positions. Direct coordinates can move straight to the target row. A spotter bearing and distance require projection from the spotter. Two observer bearings require a forward-ray intersection. Keep pencil colors or line styles consistent if the current game provides them, but treat color as a visual aid rather than intel truth. The written source label remains the durable reference when lines overlap.
Use the Operator Console to reproduce the map math when a report fits one of its three modes. The Console processes intel locally and displays target X, target Y, Nest bearing, Nest range, and a diagram. It does not send intel to analytics or a server. It also does not infer missing distance, choose a shell, or calculate disputed elevation. Those boundaries prevent the tool from turning incomplete intel into precise-looking fiction.
Transfer intel into one firing card
A firing card is the controlled output of the intel chain. Include mode, mission, target label, target coordinates, Nest bearing, Nest range, shell, charge, elevation, and observation. The first five derived fields should trace back to the current intel and map calculation. Shell, charge, and elevation should come from the current game interface in one calculator pass. If any field is unknown, keep it visibly unknown instead of borrowing an older value.
Read the card aloud or point field by field during turret transfer. Verify each displayed control before moving to the next. An interruption resets the transfer check to the first field because memory cannot prove which intel value reached the turret. After firing, preserve the card and attach reconnaissance as new intel. The result may support a correction, an effect change, or no change. It never changes the original report retroactively.
- Read all command and frontline intel before plotting.
- Label each origin, target, priority, and requested effect.
- Create derived map and firing rows without overwriting source intel.
- Transfer the complete card and verify visible controls.
- Attach reconnaissance as a new intel record after impact.
Detect stale intel
Intel becomes stale when a newer report supersedes it, a target moves, the Nest position changes, a patch alters an interface, or a community guide no longer matches the current client. Mark superseded intel rather than deleting it. A clear stale label prevents old coordinates from reentering a new firing card while preserving the history needed to understand a previous shot. Search results on this site use the same stale concept for source records.
Current-client intel outranks a remembered community value for the active session. Official patch and store sources can establish broad scope, but they rarely provide every mission coordinate. Community intel can identify a recurring problem or technique, yet it remains attributed. Interaction counts and repeated comments can increase priority for investigation, not convert a mechanic into fact. This evidence ladder lets maintenance automation publish safe context without asking for constant human review.
Verify intel before and after fire
Before firing, verify intel against three independent checks: source label, map direction, and current interface. The source label proves where a value began. The map direction proves the geometry is plausible. The current interface proves the selected shell, charge, and elevation are visible now. If one check fails, stop the intel chain at that layer. More calculations cannot repair a missing source or a misread control.
After firing, reconnaissance becomes result intel. Record hit, short, long, left, right, wrong effect, or unobserved in the Console. A large miss should reopen source and coordinate intel before a fine correction. A centered impact with wrong effect should reopen shell choice. An unobserved result should not produce a numeric change. This closed intel loop makes every next action explainable and keeps private records useful across interruptions.