Lock the correct threat first
Treat command text as the first filter before touching the map. If multiple hostiles are present, pick one active threat and keep the other reports separate until that shot is resolved. Each target needs its own map marks, calculator result, and correction history.
Build geometry only for the target you can complete in the current cycle. If command context changes and another threat becomes the priority, clear the old target solution and restart with the promoted threat. Mixing two targets creates conflicting geometry and makes misses difficult to diagnose.
Finish prefire setup as one atomic pass
The first enemy impact marks the end of your setup window, so target plotting, final measurement, and card generation should be complete before it lands. Do not carry an unmatched range, shell, or charge into loading. A stable setup is one complete sequence with one clear output.
The final map line, shell, charge, and card must all belong to the same current target. If any part is still ambiguous, clear the unfinished solution and run one fresh pass before touching turret controls. Clean setup keeps the correction path short.
Keep one conversion and one card
Do not preserve an old final line after changing the target marks, and do not keep an old card while loading for a different target. The active line and card must be rebuilt together. If shell or charge changes mid-cycle, draw a new final Nest-to-target measurement before loading again.
A new load must always map to a current card state. When values look close but still miss, compare only within the current cycle. If anything is older than the latest redraw, rebuild instead of patching.
Handle target elimination and state shift
After the first active target is destroyed, the mission can shift to a different threat or timing condition. Do not keep using the same setup if the command state has changed. Before the next cycle, reread the command text and identify the new report focus from scratch.
If the target changed, redraw the map solution and create a new calculation. When another asset reports an urgent threat, discard the previous target assumptions and rebuild from the current order. A clean rebuild is more reliable than correcting from obsolete geometry.
Rebuild when a secondary threat becomes active
Secondary threats often arrive during this challenge, so confirm the new priority from the command and report before touching controls again. Work on one target at a time. Create the final Nest-to-target line and calculator result only after the new threat is confirmed as active.
Never blend an unresolved target with the active target inside one card or turret setup. If the second threat becomes the priority, clear the old candidate lines and start with a clean firing cycle. This prevents values from the first target carrying into the second attempt.
Use a narrow correction order
When a miss happens, correct in one fixed order: target check, conversion redraw, calculation, then turret apply. Do not patch shell, charge, and conversion in parallel. If range drift appears, hold active report anchors and rebuild only the final conversion line first.
This keeps the correction anchored to the same reports and target point. After recomputing, verify that shell and charge still match before loading. A clean correction loop prevents rushed edits from becoming a chain of misses.
Optional route tools and challenge context
Some teams use scouting sweeps, precomputed card notes, or dual-barrel sequencing in advanced runs. Keep those as optional tools, not the default flow. If an optional tool reduces your prefire stability, remove it immediately and return to base sequence.
The same mission state can support multiple methods only after the base loop is stable. Counter-Battery is won by consistency first, optimization second. Build a reliable loop and attach optional methods only where they do not weaken state discipline.
Common mistakes before impact
The biggest timed-loss pattern is partial setup before first impact. This is easy to spot if your candidate, shell, or charge changed after the shell line was treated as fixed. Another common pattern is switching to a secondary threat before clearing the first target solution.
If this happens, restart from the command panel and map scope. Do not ignore the reset cost; a quick reset is cheaper than a multi-shot correction loop with mixed states. Finish the reset before entering a new firing solution.