Quick Answer
Sound the war horn to begin Fire on Call, then treat each support request as a short request card: identify whether it is offensive HE, a concealed strongpoint requiring TEAR before HE, or defensive SMK, and answer in that order before the request expires. HE fired first at a hidden strongpoint leaves it active, while late or incorrect support can let allied positions be overrun. The mission starts with 300 requisition, 10 powder charges, and four medal slots. Most enemies are soft targets, but ally movement and invisible building positions make sequence discipline more important than rapid indiscriminate fire.
Mission Facts
| Field | Checked value |
|---|---|
| Mission number | 10 |
| Location | Guadalquivir valley, inland Andalusia |
| Initial funds | 300 requisition |
| Charge quota | 10 powder charges |
| Medal slots | 4 |
| Enemy summary | Enemy Field 6; Enemy Infantry 18; Enemy Mech 6 |
| Recommended ammunition | HE, TEAR, SMK |
Step-by-Step Route
- Before starting, divide the run note into three request lanes: direct offensive HE, concealed-position TEAR then HE, and defensive SMK. Give each lane a distinct shorthand.
- Record 300 requisition, 10 powder charges, four medal slots, and the soft-target roster of six Enemy Fields, 18 Enemy Infantry, and six Enemy Mech.
- Prepare to identify requests by purpose rather than by target name alone. Offensive destruction and allied repositioning demand different shells even when they occur in the same area.
- Sound the war horn when ready; this begins the assault and changes the mission from preparation to timed call handling.
- On each incoming call, pause only long enough to classify it as direct HE, hidden strongpoint, or defensive movement. Write the request before selecting the shell.
- For a direct offensive call against exposed soft opposition, answer with HE and then check whether the requested support result is confirmed.
- For a concealed building position, fire TEAR first to reveal the strongpoint. Only after the reveal should HE be used to attack it.
- For a defensive call, use SMK to cause allied units to reposition out of danger. Do not replace this movement response with an offensive HE shot.
- After every response, mark the call as answered, late, incorrect, or unresolved. This preserves the causal link between request, shell, and battlefield result.
- Reconcile remaining charges while the battlefield is quiet enough to do so. A 10-charge allowance makes an accidental duplicate or reversed sequence costly.
- Watch allied positions after support. If a request result is unclear, keep the record unresolved instead of assuming the allies are safe.
- Continue the receive-confirm-answer cycle until the city falls. Street resistance left after primary completion is optional.
- At the result screen, compare ally kills, total enemy kills, kills per shot, and reconnaissance use with the four gold-medal conditions.
- Record the PCLM Shell unlock, The Gun Answers completion outcome, and Iron Discipline only if all four medal slots report gold.
Detailed Walkthrough
Set the call board
Objective: Prepare three visually distinct response patterns and a compact resource view before the horn starts the timed assault.
Fire on Call supplies three support languages. A direct offensive request calls for HE against soft targets. A concealed strongpoint requires TEAR first and HE second. A defensive request calls for SMK, whose impact causes allied units to reposition. Put these patterns on separate lines before the first call. The mission roster—six Enemy Fields, 18 Enemy Infantry, and six Enemy Mech—consists of soft targets under the mission-specific recommendation, but that does not make HE the answer to every event. Purpose controls the response. Record the 300-requisition starting pool and 10 powder charges beside the board, then reserve space for call time, class, requested sequence, action, and observed result. The horn starts the assault, so preparation belongs before that transition. No fixed coordinates or call order are established here; the board is designed to interpret whatever valid request the current run presents.
Watch for
- Writing a single “fire HE” rule for all request types.
- Starting the horn before the three response patterns are prepared.
- Treating roster counts as a prediction of call order.
Receive and classify
Objective: Translate each incoming field request into one of the three response classes without adding an unsupported target solution.
A timed call creates pressure, but the first decision remains classification. Listen for whether allies are asking for direct offensive fire, help exposing a hidden building position, or defensive displacement. Record that purpose in a few words. Then match the purpose to the prepared pattern. This reduces wrong-shell errors caused by reaching for whatever was loaded during the previous call. Some building positions are initially invisible. That fact matters only when the request concerns a concealed strongpoint; it is not a reason to fire TEAR before every HE task. Likewise, SMK belongs to moving allied units out of danger, not to a generic concealment routine. Keep the current call isolated until it is answered or marked missed. Late or incorrect fire can allow allied positions to be overrun, so the classification pause must be brief, consistent, and tied to the language of the live request rather than an imagined battlefield script.
Watch for
- Repeating the previous shell because two calls arrive close together.
- Using TEAR for every offensive request whether the position is hidden or not.
- Choosing SMK for an enemy-destruction task rather than an allied movement request.
Answer in the requested grammar
Objective: Execute HE, TEAR-then-HE, or SMK exactly as the classified support task requires, then verify the allied result.
The response patterns are small but order-sensitive. Direct HE is a one-step offensive answer for exposed soft targets. The hidden-strongpoint answer is a two-step grammar: TEAR reveals the building position, and HE follows against the now-exposed strongpoint. Reversing that order leaves the concealed position active. Defensive SMK is different again: its effect is to make allied units reposition, so observe their movement rather than grading it as a destruction shot. After each impact, update the request record with the visible outcome. If the strongpoint remains hidden after TEAR, the sequence is not ready for HE. If allies do not appear safe after SMK, do not mark the defensive call complete merely because smoke was fired. Reconcile powder charges after each complete request, not halfway through a two-shell chain, so the note accurately reflects both the sequence and its total cost.
Watch for
- Firing HE before TEAR at a concealed strongpoint.
- Marking a defensive call complete from shell launch rather than allied repositioning.
- Losing track of the second action in a two-shell request.
City-fall debrief
Objective: Recognize primary completion at the city’s fall, stop treating residual resistance as mandatory, and evaluate the efficiency medals from recorded calls.
The primary objective completes when the city falls. Remaining resistance in the streets is optional afterward, which creates a clean stopping point for an already successful support run. Before continuing, ask whether extra fire advances a specific medal and whether it threatens allies. Begin the result audit with Measured Fire Star: its gold grade permits no ally deaths. For No Quarter Cross, the total must reach 30 enemy kills. Ordnance Efficiency Cross combines a minimum ratio of two enemy kills for each shot with a 10-kill floor. The unaided distinction instead pairs zero reconnaissance use with an enemy total above 18. These thresholds reward accurate call handling but should be read from the result screen, not inferred from the city animation. Completion unlocks the PCLM Shell and corresponds to The Gun Answers. Iron Discipline is the all-gold outcome. Review late, incorrect, and unresolved call records to identify one response habit for the next attempt.
Watch for
- Continuing to fire at optional street resistance without checking ally risk.
- Assuming 30 kills automatically satisfies the kills-per-shot medal.
- Awarding Iron Discipline mentally before all four medal grades are visible.
Mistakes to Avoid
- Starting the assault before preparing the three request-response patterns.
- Treating every soft-target event as a direct HE request.
- Failing to classify a call before selecting ammunition.
- Firing HE before TEAR at an initially invisible strongpoint.
- Using TEAR without following with HE after a confirmed reveal.
- Using SMK as an offensive substitute rather than to reposition allies.
- Assuming a launched shell means the support request succeeded.
- Letting a late response record disappear instead of diagnosing it.
- Continuing optional street fire after the city falls without a medal purpose.
- Confusing The Gun Answers completion with the all-gold Iron Discipline achievement.
Achievements
The Gun Answers
This completion achievement identifies a successful Fire on Call operation. Start the assault, answer the field’s support needs, and confirm the city-fall result rather than treating any single request as the whole mission.
Iron Discipline
This all-gold achievement requires every Fire on Call medal to reach gold. Check ally safety, enemy totals, shot efficiency, and unaided-fire performance separately at debrief.
Run Checklist
- 01Confirm Fire on Call and Mission 10.
- 02Prepare separate HE, TEAR-then-HE, and SMK lanes.
- 03Record 300 requisition and 10 powder charges.
- 04Record six Enemy Fields, 18 Infantry, and six Mech.
- 05Sound the horn only when the call board is ready.
- 06Classify every request before loading a response.
- 07Use HE for exposed soft-target offensive calls.
- 08Use TEAR before HE on concealed strongpoints.
- 09Use SMK for defensive allied repositioning.
- 10Verify the result of each support response.
- 11Track late, incorrect, and unresolved calls.
- 12Reconcile charges after each completed request.
- 13Stop treating street resistance as mandatory after the city falls.
- 14Review all medal thresholds and the PCLM Shell unlock.
