Quick Answer
Counter-Battery is Mission 4 in Ciudad Real, Castile-La Mancha, central Spain. The mission setup starts with 500 requisition and 0 powder charges, so confirm the live resource display before making any commitment. The observed roster lists five Enemy Artillery, twenty Ally Group members, five Enemy Infantry, and three Ally Spotters. The mission lists HE as the shell, while the mission uses varying charge selection; those are separate decisions, not different ammunition types. Build a target-and-resource ledger, respond to current-run information, and avoid assuming purchase prices, fixed coordinates, timing thresholds, medal thresholds, or one mandatory target order.
Mission Facts
| Field | Checked value |
|---|---|
| Mission number | 4 |
| Location | Ciudad Real — Castile-La Mancha, central Spain |
| Initial funds | 500 requisition |
| Charge quota | 0 powder charges |
| Medal slots | 4 |
| Enemy summary | Enemy Artillery 5; Ally Group 20; Enemy Infantry 5; Ally Spotter 3 |
| Recommended ammunition | HE shell; powder-charge selection remains a separate firing setting |
Step-by-Step Route
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
Detailed Walkthrough
Phase 1: Establish the resource and roster ledger
Objective: Start from the mission setup and leave any value not shown by the current run blank.
Begin with the narrow record: Mission 4, Ciudad Real in Castile-La Mancha, 500 requisition, 0 initial powder charges, four medal slots, and four distinct roster categories. The zero-charge opening deserves special care. It is a mission detail about the initial state, not a license to invent how charges are obtained or what they cost. Give requisition and powder charges independent columns so one cannot be mistaken for the other. Add another section for five Enemy Artillery, twenty Ally Group members, five Enemy Infantry, and three Ally Spotters. Counts support accounting, but they do not form a map, reveal a fixed order, or establish a firing solution. When the current run differs from the mission setup, retain both entries with labels instead of silently rewriting one into the other.
Watch for
- Treating 500 requisition as a known budget for a specific shopping list. Correction: record only the initial total and capture any live purchase price separately if the game displays it.
- Reading 0 initial powder charges as proof of a fixed acquisition step or exact shot allowance. Correction: verify the live state and record subsequent changes without supplying an unsupported rule.
- Combining allied and enemy categories into one roster total. Correction: maintain four named rows and require the current mission display before changing their status.
Phase 2: Separate HE shell selection from varying charge selection
Objective: Maintain two decision fields so shell identity and charge setting never become competing ammunition labels.
The mission notes describe different field shapes. The mission lists HE, which belongs in the shell field. the mission uses varying charge selection, which belongs in a separate setting field. The latter does not introduce new shell types and does not conflict with HE. Before a commitment, write the shell and charge selection in separate cells using only values visible in the current run. This structure prevents a common editorial error: turning a change in propellant charge into a change in ammunition category. The mission information does not establish a particular charge value for any target, so this phase offers no numerical setting, range conversion, or target-specific formula. If the interface supplies a selectable value, preserve it as a run observation rather than a universal recommendation.
Watch for
- Presenting the varying-charge guidance as mission information for another shell type. Correction: keep HE under shell and charge selection under its own heading.
- Assigning one exact charge setting to Enemy Artillery or Enemy Infantry without the current mission display. Correction: let the live interface and observed result inform the run note.
- Assuming an HE listing proves a complete damage rule for every roster class. Correction: preserve the narrow shell observation without adding target effectiveness claims.
Phase 3: Classify contacts and reconcile outcomes
Objective: Use the roster as an accounting aid while avoiding fixed positions and a mandatory sequence.
The roster can guide careful identification without dictating an engagement order. Maintain five lines for Enemy Artillery and five for Enemy Infantry, plus separate allied-group and allied-spotter accounting. Neutral labels are sufficient when names are unavailable. Advance a line only when the current run provides a visible basis. Before every commitment, review whether the contact class is confirmed, whether the HE shell field matches what is selected, whether the charge setting is listed, and whether allied entries remain protected from accidental reclassification. Afterward, note the feedback exactly as seen. The mission information offers no coordinates, no timing threshold, and no single route. A flexible loop of observe, classify, record, commit, and reconcile is therefore more honest than a numbered target script.
Watch for
- Turning roster counts into assumed positions or reveal order. Correction: treat counts as ledger capacity and obtain positional information from the current run only.
- Marking an intended enemy as confirmed before the game reports an interpretable result. Correction: keep intention and observed outcome in different columns.
- Claiming that one enemy class must always precede the other. Correction: select among currently supported opportunities without declaring a universal order.
Phase 4: Review medals and preserve open questions
Objective: Separate completion, all-gold recognition, and unresolved tactical observations at the end of the attempt.
Four medal slots are present in the mission setup, but no medal names, numerical thresholds, timing requirements, or scoring formulas are established. Read each result from the game and transcribe it without reverse-engineering a rule from one attempt. The game separates two achievement outcomes: First Reply is associated with completing Counter-Battery, and Distinguished Conduct is associated with earning gold on all medals in Counter-Battery. These descriptions distinguish two outcomes but do not explain how a medal is earned. Finish the debrief by comparing initial and final resources, every roster line, the HE shell notes, varying charge selections, and the displayed result. Convert mismatches into specific questions for a future run and change one uncertain decision at a time.
Watch for
- Treating completion as proof that all four medals are gold. Correction: record the completion identity and all-gold identity as separate outcomes.
- Inventing a time, score, accuracy, or resource threshold from a successful result. Correction: report only what the result screen explicitly establishes.
- Calling one clean attempt the unique solution. Correction: retain it as one observation and test alternatives before making any broader claim.
Mistakes to Avoid
- Do not replace the ASCII hyphen in Counter-Battery with another dash character; the official mission identity uses Counter-Battery.
- Do not infer a purchase price from the listed starting values of 500 requisition and 0 powder charges.
- Do not turn the initial zero-charge state into a claimed final allowance, exact shot count, or mandatory transaction.
- Do not describe varying charge selection in the mission as a shell type; the HE shell listing is the shell observation.
- Do not merge Enemy Artillery, Enemy Infantry, Ally Group, and Ally Spotter into one undifferentiated count.
- Do not derive a firing coordinate, direction, range, or landmark from the Ciudad Real setting.
- Do not prescribe a fixed time window or timing threshold for any action or medal.
- Do not invent medal names, scores, conditions, or thresholds from the presence of four slots.
- Do not claim that Enemy Artillery or Enemy Infantry has a universally required first position in the target order.
- Do not treat First Reply and Distinguished Conduct as the same outcome; one concerns completion and the other concerns all-gold performance.
Achievements
First Reply
Official recognition associated with completing Counter-Battery. The identity does not establish a route, threshold, or hidden tactical condition.
Distinguished Conduct
Official recognition associated with earning gold on all medals in Counter-Battery. The identity does not reveal individual medal requirements.
Run Checklist
- 01Confirm Counter-Battery and the Mission 4 setup.
- 02Record 500 starting requisition without assuming any purchase price.
- 03Record 0 initial powder charges without treating zero as a final allowance.
- 04Create separate rows for five Enemy Artillery and five Enemy Infantry.
- 05Create separate allied rows for twenty Ally Group members and three Ally Spotters.
- 06Keep the mission's HE shell listing separate in the mission varying charge selection.
- 07Capture shell and charge-setting observations in different fields.
- 08Use the current run for identification and do not add fixed coordinates.
- 09Reconcile resource changes without inferring a general cost formula.
- 10Review four medal slots without supplying conditions or thresholds.
- 11Separate First Reply completion from Distinguished Conduct all-gold recognition.
- 12Preserve unresolved questions without claiming one mandatory target order.
