Start from one current target
Read the active mission text first, then lock one target. All icon checks and final measurements must stay tied to that target until the firing solution is ready. If the objective changes mid-cycle, clear the marks and rebuild for the new target.
This workflow depends on the current objective, so it is not a permanent icon encyclopedia. The same marker can be useful for one target and irrelevant for another after the command context changes. Recheck the current symbols after every update, even when one looks familiar.
Read marker legends before assigning meaning
Open the map key whenever a symbol is unclear, newly drawn, or appears after a fast report update. The in-game key is the active authority for meaning in this moment. Do not treat icon shape or color as fact until the key label is confirmed on-screen.
Pair each key label with clipboard text and the same report line in the same second. A color may stay constant while meaning shifts with mission context, so label and report must agree before the icon enters geometry planning. If a marker has no clear label, hold it in scouting and keep it out of load-ready use.
Anchor map reading with report text
Tie each active report to a map marker only when their labels match in the same cycle. If a marker is unlabeled or conflicts with the report, leave it for scouting and avoid using it to build the target. This prevents an uncertain symbol from driving the firing measurement.
When report text updates, immediately remove anchors that no longer have matching labels on the map. Rebuild that symbol chain from the latest report before continuing to any geometry conversion. This is where most icon confusion is introduced, and also where most quick recoveries start.
Keep spotter symbols tied to their own origin
Keep each spotter marker tied to the exact marker position that generated the current report. If that marker shifts or is replaced, rebuild all bearings and arcs from the new marker before any conversion. This avoids stale lines that look valid but belong to the previous anchor.
Do not reuse old geometries from a replaced marker, even when they are near the same location. Recreate geometry from the updated anchor and verify it with the current report list before moving forward. Once rebuilt, keep old and new markers separate so you can audit both paths cleanly.
Read Nest position and target candidate together
Any fire conversion starts from the live Nest position and must end at one confirmed candidate point. If an icon suggests a target, confirm that the icon, report, and candidate trace to the same active context before creating measurements. The icon is a cue, while the candidate proof is the control condition.
If that proof is weak, keep the icon in scouting and do not convert the same cycle. Build candidate lines from confirmed report markers until the chain is stable. Then draw the one red line for compute with both target and Nest link verified.
Use current-game labels to choose priority icons
Confirm labels before drawing geometry for every target, then build the candidate only if those labels remain stable. If a label and map line disagree, set the symbol aside and repair the target solution before changing the turret. This keeps icon use tied to the present objective rather than prior memory.
Do not infer shell or charge purely from icon familiarity, even when the marker appears clear. Geometry, labels, and candidate alignment must all agree before you touch values that affect a shot. This prevents false confidence from static icon familiarity.
Verify every icon with live impact behavior
After any shot, compare impact behavior with the same marker and candidate context before changing settings. If impact aligns near the marker but not the intended objective, trace the gap through active report lines and key labels before any turret edit. This finds state errors earlier than adjusting shell, charge, or elevation first.
If a marker repeatedly fails this check, remove it from the active target solution. Rebuild the candidate with updated labels, then run the read-check loop again before the next correction. That gives you a clean baseline instead of carrying a misleading symbol forward.
Avoid a full icon encyclopedia
Do not rely on a fixed icon encyclopedia for this game. A symbol used in one operation may not provide enough context in another operation or after a command change. Use the active map key as authority, not memory or static tables.
Use a clean read-check loop
Before any fire conversion, run a fixed loop: map key label, active report line, candidate validation, then red-line conversion. Any fail in that loop means you stop and restart from the first failed point before drawing again. Keeping this loop stable gives you repeatability under pressure.
If the loop fails, do not adjust shell, charge, or bearing first because the problem is usually interpretation drift. Fix symbol meaning with live labels, then resume geometry and conversion. This is faster than guessing values after a missed shot.
If any step is skipped, treat the output as stale and rebuild the full solution before drawing the next line. The rebuild also refreshes the candidate and current objective. Keep this sequence for every shot and every target update.