UNOFFICIAL GUIDE · Evidence reviewed September 1, 2026 · Build baseline 24750322 — Version 1.0 (1622), Patch #5 · Full mission spoilers, low ending spoilers
UNOFFICIAL GUIDE
White Shells is easier to understand when you decide what this attempt is for before firing. A city-directed attempt follows the final order toward a Barcelona result. A betrayal attempt changes the mission into a hostile fight with a timer, repeated incoming impacts, and a build-specific target filter. Those are different mission shapes, not two interchangeable ways to clear the same checklist.
IRON NEST White Shells is main-line Mission 15 in build 24750322. Resolve Barcelona under the final order, or attack High Command and survive the hostile retaliation. This guide covers the mission state and completion check; the four outcome routes stay in the dedicated endings guide.
| Field | Value |
|---|---|
| Mission | White Shells |
| Campaign order | Main-line Mission 15; no main-line successor |
| Operation | Base Campaign |
| Opening decision | Resolve the final order concerning Barcelona |
| Betrayal signal | STATUS: HOSTILE and TRAITOR! |
| Retaliation state | A timer, time additions, a stop event, and scripted impacts |
| Betrayal completion filter | All entities carrying the mission's Artillery role |
| Version | Build 24750322 · Version 1.0 (1622) · Patch #5 |
IN-GAME DATA:
The graph contains four end states and four mission-completed listeners. That supports four structural endings, but it does not by itself prove the player action behind each result. The task graph and the observed outcome footage answer different questions, so this page does not turn node counts into an ending recipe. The same caution applies to the spawn list. Build 24750322 creates civilians, hospitals, allied infantry, tanks, mechanized units, spotters, King, General, and artillery groups. A spawn count describes what the graph creates; it does not promise that every entity is alive or visible at the same moment in every attempt.
Check the mission title and the teleprinter order. White Shells asks you to decide what happens to Barcelona. Before touching the firing controls, decide whether you are following the city-directed order or deliberately turning against High Command. If you are choosing an outcome rather than merely trying to finish the mission, make that choice with the ending information open first; the mission does not give you a harmless preview shot.
Success signal: you can state which mission shape this attempt will follow. If not:pause here. Spending a specialized shell while undecided may narrow your options later, and the current evidence does not establish a universal way to restore every inventory state.
For a city-directed attempt, follow the order and wait for the corresponding mission-complete response. Build data contains three different completion-message meanings for the city: celebration, submission, and destruction. This walkthrough intentionally does not reproduce the shot-to-outcome matrix.
For a betrayal attempt, the decisive change is attacking High Command. In the build data, destroying either King or General satisfies an allied-group trigger that feeds the hostile and timer sequence. Do not begin by clearing unrelated map icons: they are not a substitute for the state change.
Success signal: a city-directed completion response appears, or the betrayal state displays the hostile messages. If not: re-check the target you engaged and the most recent teleprinter line before firing again.
White Shells does not expose a stable, reusable set of bearing, range, elevation, or charge fields in the extracted mission data. Use the target and firing information from your own attempt. A coordinate copied from another run can miss because it has lost the run context that made it meaningful.
Success signal: your next shot is tied to a target and state visible in the current attempt. If not: return to the latest report or teleprinter instruction instead of treating a third-party worked example as a universal solution.
After the High Command trigger, look for STATUS: HOSTILE and TRAITOR!. The mission flow then contains a timed retaliation sequence with time additions and repeated scripted impacts. Those impacts describe incoming mission events. They are pressure to manage, not sixteen artillery pieces waiting to be found.
Success signal: the hostile messages and retaliation sequence are active. If not: confirm that King or General was actually destroyed and that the mission has advanced beyond the original city order.
In build 24750322, the ending event listens for All entities with the Artillery role. The role join matches King, General, three unarmored allied artillery entities, and eight armored allied artillery entities. That is 13 matched entities in this build: two command entities plus 11 allied artillery entities.
Treat that list as a diagnostic for this build, not as a promise of thirteen guns. King and General are part of the filter even though they are not ordinary artillery pieces. The extracted structure does not prescribe a shell type, firing order, or best coordinate for removing the set.
Success signal: the remaining Artillery-role set is gone and the flow reaches stop timer, then end. If not: check King, General, and the 11 allied artillery entities separately rather than counting impact animations or every red icon on the map.
Do not use silence alone as the completion test. The build path connects the All Artillery destroyed condition to a stop-timer state and then to an end state. Give the mission time to deliver that transition and its completion feedback.
Success signal: retaliation stops and the mission-complete state appears. If not: use the completion checklist, then move to the resource and restart checks instead of spending ammunition on unrelated targets.
White Shells combines a final city decision with an optional break from command. That makes intent part of mission preparation.
| Your goal | What this page tells you | What to do next |
|---|---|---|
| Finish a city-directed outcome | Follow the order, make the intended shot, and wait for the matching completion response. | Use the outcome guide before firing if the exact result matters. |
| Betray High Command | Trigger the hostile state, survive retaliation, and clear the build-specific Artillery-role set. | Continue with betrayal combat. |
| See every named outcome | Mission execution alone is not enough; you also need the observed route and replay boundaries. | Use the complete White Shells endings guide. |
The game-data graph supports three city-result message paths and one hostile combat path. It does not justify broad rules such as “any chemical shell gives one outcome” or “any lethal shell gives another.” Observed footage supports narrower actions, and the Endings page owns those details.
The betrayal path is a state machine, not a generic clear-the-map objective:
The practical lesson is to diagnose by role and state. If incoming fire continues, first ask whether the hostile branch actually started. If it did, inspect the command entities and both allied artillery groups. Do not infer that every scripted impact has a corresponding gun, and do not assume that clearing civilians, hospitals, infantry, tanks, mechanized units, or spotters is required by the All Artillery filter.
The extraction identifies what the current build listens for, but it does not rank targets for you. Your safest order depends on the live firing information, available ammunition, and which threats are currently interrupting your work. Any “always fire here first” sequence without that context would be a strategy claim, not a build fact.
Use this checklist in order:
These checks are build-specific. A patch that changes entity roles, spawn composition, or the event filter can change the answer even if the mission name stays the same.
There is not enough current evidence to publish a fixed starting requisition total, a fixed six-charge limit, or an EQKE reward for White Shells. Treat any such number as a run-specific observation unless a future build field or version-shown capture closes the gap.
If you used a specialized shell before deciding on an outcome, stop and check three things: the result you wanted, the shells still available in this attempt, and whether a save or restart can return you to a useful decision point. A player may need to restart an attempt after an inventory mistake, but the available reports do not prove that every such mistake creates an unavoidable soft-lock.
For shell properties and the current catalog, use the build-checked shell reference. It explains what the ammunition does without turning one White Shells route into a universal recommendation.
If the mission state looks wrong, preserve the context before retrying: note the last teleprinter line, which command entity was hit, whether hostile status appeared, and what targets remained. That record is more useful than repeating a rumored sequence with no matching state.
Completing White Shells and collecting every named outcome are different goals. This page owns the execution state: what the final order means, how betrayal begins, what the current build monitors, and how the mission closes. The Endings guide owns the observed action-to-outcome routes, official achievement names, community numbering conflict, replay boundaries, and detailed Pride troubleshooting.
Pride of Castile belongs to that outcome context. Players have reported unlock problems, but the reviewed material does not contain a developer confirmation that the achievement is bugged. For the mission-by-mission achievement boundary, use the White Shells entry in the medals reference.
If you only need to continue or revisit the Campaign sequence, return to the verified mission list and general troubleshooting hub. In build 24750322, White Shells is main-line Mission 15 and has no main-line successor.
This walkthrough's mission order, entity roles, spawn composition, and destroyed-event filters apply to build 24750322, identified as Version 1.0 (1622), Patch #5. The build was extracted on August 17, 2026, and this page's claim set was reviewed on September 1, 2026.
Three page-specific questions remain open: whether 700 requisition, six charges, or EQKE are fixed mission values; whether Pride unlock reports received an official fix; and whether every special-shell inventory mistake has the same restart behavior. Until a build field, official statement, or controlled current-build reproduction answers them, this page keeps those claims out or labels the recovery advice as conditional.
A new build, a White Shells-specific patch note, or a reproducible change to the target filter is the refresh trigger. A search-ranking or metadata change alone does not refresh the game-fact date.
Yes. In build 24750322, the Campaign order lists White Shells as main-line Mission 15 with no main-line successor. That number comes from the extracted build order, not only from a video chapter label.
Read the Barcelona order and decide whether this attempt will follow the city-directed route or betray High Command. If the exact named outcome matters, choose it before spending a specialized shell; otherwise follow the step-by-step walkthrough.
Destroying King or General satisfies the build's allied-group trigger and moves the mission into a hostile, timed retaliation state. Look for `STATUS: HOSTILE` and `TRAITOR!`, then follow the betrayal combat checks.
Build 24750322 matches 13 entities: King, General, and 11 allied artillery entities. That does not mean thirteen guns, and the 16 scripted impacts are not targets. A future patch could change the role join.
A resource mistake may make the current attempt worth restarting, but the reviewed reports do not prove a guaranteed soft-lock. Check your intended outcome, remaining inventory, and available restart point before assuming the save is lost.
Use the endings handoff above for the dedicated guide. It covers the four named outcomes, observed routes, replay boundary, numbering conflict, and Pride context; this page stays focused on completing Mission 15.
Reviewed August 8–September 1, 2026. Evidence types and dates are stated beside each claim above.
Official: The release and patch timeline dates the Version 1.0 / Patch #5 baseline; no mission-specific developer answer was used to settle the open resource or achievement questions.
In-game text: Campaign order, mission graph, flow, localization, node fields, entity roles, and destroyed-event filters support the Mission 15 state and completion analysis.
Observed footage: One continuous full-game run supports the finale position, while two ending captures support only the outcome actions visible on screen.
Reported: Community questions and a third-party mission guide identify resource, restart, target-count, and achievement issues that remain limited where stronger evidence is absent.
Spot an error or a post-patch change? This guide follows correctable public evidence — corrections update the page and its review date.