What is a Supply Cache in IRON NEST?
It is an underground target whose current normal instruction is AP. The reviewed Patch #5 evidence directly uses the Supply Cache label in Chill; other modes need their own naming and workflow limits.
UNOFFICIAL GUIDE · Reviewed August 25, 2026 · Version 1.0 build 24750322 · No author gameplay test claimed
UNOFFICIAL GUIDE
This unofficial IRON NEST Supply Cache guide separates the current in-game rules from older footage and conflicting community reports. It explains how to recognise the underground target, why AP is the normal ammunition, how location information changes between modes, what the game actually confirms about requisition, and where the evidence stops.
An IRON NEST Supply Cache is an underground target. In the reviewed Patch #5 text, the normal instruction is to destroy it with AP ammunition. How you obtain its position depends on the mode, so identify the operation before following any location advice.
These labels show what each statement rests on and where its limits begin. The complete Field Data method remains on the evidence-label reference.
| Label | What it means here |
|---|---|
| OFFICIAL | A developer or official source directly supports the statement; here, that label applies to the dated developer explanation of the underground marker. |
| IN-GAME TEXT | The statement comes from localisation, mission briefings, or mission-graph text extracted from build 24750322. |
| OBSERVED | A player run shows an action and result; the observed Liberation material used here predates Patch #4 and is never treated as a current numeric rule. |
| REPORTED | A community post or Tester report raises a possible behavior or problem that the reviewed build does not settle. |
The main baseline is Version 1.0 (1622), Patch #5, build 24750322, reviewed August 25, 2026. The Discord archive used for questions ends on August 22, 2026. No statement on this page represents an unrecorded author playtest.
| Field | Value |
|---|---|
| Display label | Supply Cache |
| Target class | Underground target |
| Normal ammunition | AP required |
| Location rule | Mode-specific information path; no universal coordinates |
| Confirmed reward wording | Additional requisition in the current Chill briefing |
| Current evidence baseline | Version 1.0 (1622), Patch #5, build 24750322 |
IN-GAME TEXT from Version 1.0 (1622), Patch #5, build 24750322, with the underground-marker explanation cross-checked against a developer reply dated June 13, 2026.
The current Chill briefing identifies underground supply caches, requires AP ordnance for their destruction, and says cache destruction yields additional requisition. That wording supports the target class, normal ammunition, and a qualitative reward. It does not establish a fixed reward value, a universal number of caches, or a respawn schedule.
Start with the mode, not with a coordinate copied from another run. Liberation uses reconnaissance to reveal a mission target. Chill can deliver dynamic bearing, distance, or grid information through its event flow. Challenge uses its own triangulation and FDC objective language. Those are different information paths, not interchangeable steps.
A developer explained on June 13, 2026 that the green M-shaped marker indicates an underground target and therefore calls for AP. Treat that as a dated official explanation of the marker. The reviewed Patch #5 text independently confirms the underground and AP labels, but this audit did not recheck the marker shape in current-build footage.
When the target is still unclear:
This page does not provide a map-icon catalogue. It only explains the marker evidence directly tied to this target.
Use AP as the normal solution. Current Chill, Liberation, and Challenge text requires AP for the relevant underground objective in each mode. Historical Liberation footage also shows an HE attempt failing to finish the objective before an AP shot succeeds, but the current-build instruction is the stronger reason to choose AP.
Do not turn that answer into a claim about every shell. The reviewed data does not provide a reliable shell-to-cache compatibility matrix, and the available immuneShells field is empty across the extracted entity rows rather than distinguishing AP from HCHE. For general ammunition roles and target selection, use the shell-types guide to choosing a shell.
After firing AP, confirm that you hit the correct underground objective and then follow the operation's next instruction. A skull marker or destroyed target does not prove that every later mission condition has been completed. If the operation does not advance, move to the mode boundary and troubleshooting sections instead of changing to an unsupported shell rule.
The labels and workflows below are deliberately separated. A term used in one mission does not automatically define a single cross-mode object type. For the wider distinction between operations, use the Campaign, Challenge, and Demo boundary.
Liberation tells you to recon the target region, confirm the ammunition-cache position, and destroy the target with AP. Inside that mission, the current text and graph use terms including ammunition cache, Cache, Ammo Bunker, and ammoCache for the same objective chain. Older pre-Patch #4 footage also uses the visible or spoken label Supply Cache.
That limited alignment belongs to Liberation. It does not prove that every cache, bunker, or FDC label in every mode is the same object. This page stops after the recon → confirm → AP summary; the Liberation ammo-bunker walkthrough owns the complete task sequence and what happens after the bunker is destroyed.
Chill provides the clearest current Supply Cache wording. Its Patch #5 briefing says underground supply caches are present, requires AP, and states that cache destruction yields additional requisition. The mission graph also contains a dynamic event branch that can provide location intelligence.
The extracted graph includes one spawn action with a quantity of one, but that is one action inside an event branch. It does not establish the total number present, a maximum, or whether and how the event repeats. Use the information generated by the current run; do not plan around a published total or respawn timer from this page.
Do not rename the current Challenge objectives to Supply Caches. The Patch #5 briefing calls them three underground Fire Direction Center positions and requires AP. Community commentary and one narrow support exchange have used cache language around Challenge calculations, but the reviewed structure does not support publishing those terms as strict synonyms.
Destroying those FDC positions interacts with the Counter Battery Timer, which is a different objective and evidence domain. Follow the Counter-Battery Challenge mode boundary for the full context rather than importing the Chill or Liberation cache workflow.
The current Chill briefing confirms additional requisition. It does not state a fixed amount. Liberation's current graph contains additional-requisition feedback, but the reviewed structure does not expose a reliable current value that can be published as the reward for every cache.
Older pre-Patch #4 Liberation footage recorded one run with a numeric reward. This page deliberately omits that number from the quick answer and facts table because a single historical run is not a Patch #5, cross-mode constant. The build's star field also does not establish that stars, requisition, and leaderboard points are the same scoring system.
For how credits are earned, spent, lost, or carried between missions, use the requisition credits reference. The Supply Cache page owns only the reward evidence attached to this target.
First confirm the mode and objective label. In Liberation, destroying the cache is one step in a larger mission sequence; use the Liberation boundary above and return to the mission walkthrough if later objectives remain. In Chill, wait for the current event feedback and check that the correct underground target was destroyed. In Challenge, verify that you are solving the FDC objective rather than treating it as a Chill Supply Cache.
The reviewed sources do not establish a universal “hit the center” correction, a fixed second shot, or a shared post-destruction trigger for every mode. Recheck the live order and target state before changing ammunition or copying firing data from another run.
AP remains the supported normal answer. Archived community reports conflict on HCHE: one Tester said it did not destroy the target, while another report described an occasional success that a Tester considered a bug. The affected build and trigger are unknown, and the extracted current-build field does not resolve the disagreement.
That means an HCHE result is not a dependable rule in either direction. If it appears to work or fail differently in your build, record the mode, objective label, ammunition, impact, result, and version before treating it as evidence of a change.
The current evidence does not establish a total, interval, limit, or infinite-respawn algorithm. A community run reported a very high cache count, while the current graph shows an event branch whose filtering and repeat behavior have not been fully decoded. Neither source is enough to publish a respawn rule.
Use the location information generated by the current Chill run. A future current-build reproduction or developer explanation could change this answer; until then, the uncertainty is part of the result.
It is an underground target whose current normal instruction is AP. The reviewed Patch #5 evidence directly uses the Supply Cache label in Chill; other modes need their own naming and workflow limits.
Yes, AP is the supported normal ammunition. Current mission text requires AP for the relevant underground objectives, while the reviewed data does not support a universal compatibility table for every other shell.
Recon the designated target region, confirm the cache position, and then use AP. This is a Liberation-specific information path, not a universal method for Chill or Challenge.
Yes in the current Chill briefing: it confirms additional requisition. The reviewed current evidence does not establish one fixed reward amount that applies across modes.
HCHE is not a supported normal solution in the reviewed evidence; use AP. Community reports about occasional HCHE success conflict, and the affected version or bug condition has not been established.
The current evidence is insufficient to publish a respawn rule. The graph and community report do not establish a total, interval, limit, or infinite behavior for the current build.
Not in the current official wording. Patch #5 calls them three underground FDC positions; community cache language is not enough to make the names strict synonyms.
Reviewed June 13–August 25, 2026. Evidence types and dates are stated beside each claim above.
Official: A developer reply dated June 13, 2026 explains the underground marker and AP requirement.
In-game text: Version 1.0 (1622), Patch #5, build 24750322 supplies the current labels, briefings, and mission-flow wording.
Observed footage: A pre-Patch #4 Liberation player run supports the recon and AP sequence but does not set current numeric rules.
Reported: Archived community reports ending August 22, 2026 identify HCHE and Chill respawn questions without resolving them.
Spot an error or a post-patch change? This guide follows correctable public evidence — corrections update the page and its review date.