Mission scope and phase checks
Keep the current mission objective text open and confirm whether you are in HE or STAR phase before changing shell strategy. Treat phase switch as mission-driven, not timer-driven, and wait for the command state to change before shell changes. Do not change shell plan until it is unambiguous.
Place the map, report feed, and command panel together. Only proceed when these three views are consistent and you are not mixing old and current data. If they disagree, pause and resolve the mismatch before placing the next map line.
Use one active target at a time. This mission is a repeating cycle: one target candidate, one measurement, one compute, one impact check, then the next cycle. Do not open a second candidate while the first target is still active.
Read and sort spotter reports
Read each report fully before drawing on the map. For every report, place it at the spotter source and keep the same source identity attached while drawing geometry. Do not trust partial data because missing bearing or range often changes a candidate later.
Use the report geometry to build a fresh candidate only for the current hostile target. If one report is replaced or re-sent, update that target candidate before adding more marks. That keeps the candidate aligned to this target cycle and prevents stale geometry.
Hide or ignore older reports not part of the current task so the map layout stays aligned to mission command. If map clutter remains, clear it after you write down the current candidate and shell choice. This avoids reusing old context after a report refresh.
Triangulate the first target point
Build the first candidate at the intersection of the active report lines and circles. Verify each line starts from the correct source and intersects with the expected hostile area before compute. Confirm the originating marker is still visible for each source line. If a source marker is unclear, pause and redraw that source contribution before you continue.
Use a current candidate as your first aim point. Do not compute fire setup from a report-bearing while the candidate is still report-based. If a source line is uncertain, rebuild the candidate first instead of running compute early.
Once target point is stable, prepare to convert it into a final firing measurement from IRON NEST before moving to any load action. Do not skip this conversion step even if mission rhythm is fast. Skipping it risks using report geometry as firing geometry.
Convert the target into an IRON NEST firing line
Measure the final firing line using a single red line from IRON NEST to the confirmed target point. This is the bearing and range you feed into the ballistic process. Make this draw after all report-level geometry is complete for this target.
Treat this as the only active geometry for this shot. Any map line from earlier report sources can remain for audit, but the fire solution must come from the IRON NEST-to-target measurement. Treat report lines as context only in this loop.
Keep useful correction marks visible through the next decision point. Replace them only after a new valid firing solution is established and ready to use. This keeps the current correction path clear while you resolve the next shot.
Compute, load, and fire HE
Select HE shell, then enter the red IRON NEST measurement and your current charge choice. Compute the setup, and only then match the output card before loading. Do this only while command still places you in the HE objective.
Load after compute and maintain one-cycle flow: if shell or charge differs from the card, go back to compute and do not proceed. After the load steps are complete, fire and track the map impact immediately. Keep this sequence tight so stale data does not carry into the shot.
If the first HE shot misses the same target, keep that target active and correct it before moving on. Verify reports, redraw the Nest-to-target line, compute again, match the card, then load and fire again. Continue on this target until impact behavior is acceptable.
Repeat for remaining hostile targets
For each additional hostile target, restart at the report stage with the current reports. Do not keep using an old target candidate unless the command explicitly confirms it remains current. Use the same station workflow, but build new target geometry.
Measure each new target from its own reconstructed reports, convert it to an IRON NEST line, compute, load, fire, and then correct before advancing to the next target. This keeps your cycle traceable and avoids stale data across targets. Do not leave a target unresolved while adding more marks.
Recompute whenever any of these changes: target point, measured range, shell type, or charge. This applies even if only one field has shifted. If the change is unclear, treat it as a full reset before loading.
Switch to STAR and use STAR correction marks
Only move to STAR when command text requests illumination. Do not apply STAR before the mission switches, and do not treat STAR as a general HE replacement for all remaining targets. STAR begins only when the phase text changes.
For the first STAR shot, measure again from IRON NEST, compute, load, and fire. After the first impact, read the first correction marks: yellow numbers show distance from impact to the required position, and yellow arrows show correction direction. Use those two values together before your next correction pass.
Keep useful correction marks visible until you establish the next valid firing solution. Then run the same measure-load-fire loop and continue correction steps until command confirms the burst position is satisfactory. Do not mark mission complete until that command signal appears and matches your current corrections.