The Requisition Console connects planning to limited operational resources. Use it after understanding the dispatch and before committing a load. The right request is the smallest verified package that completes the current objective while preserving options for later intelligence or correction.
2950790, Windows public 1.0, checked 2026-08-09. Exact prices, unlock levels, and inventories must be read in the live run; Demo or community tables are not frozen here.Start from objective effect
Translate the order into a need: target destruction, armor penetration, illumination, concealment, area control, messaging, reconnaissance, or repositioning. Then select an available shell or ability whose current description matches that need. “Most powerful” is not a useful category when friendlies, timing, and medal conditions matter.
Write the intended shell, number of shots, powder plan, and one contingency. Do not requisition every attractive item before seeing whether the first report changes the operation.
Separate ammunition from abilities
The official Store wording combines ammunition and abilities in a pool of more than thirty unlockables. It must not be rewritten as thirty shell types. The developer FAQ names several ammunition examples and also describes reconnaissance and battlefield-control abilities.
Read which console category owns an item. A map icon or recon effect does not become a shell because it helps targeting; a star shell remains ammunition even when it provides light. This distinction improves load planning and prevents misleading databases.
Budget for the complete shot
A shell without adequate powder and a calculator-compatible plan is not a complete requisition. Confirm current stock first, then request the exact missing parts. If the planned charge count changes, recalculate before loading.
Keep a reserve only when the operation plausibly needs correction or a later phase. Hoarding can be as harmful as overspending if the mission expects a timely effect. Use the teleprinter and current objective state to decide, not a universal shopping list.
Use reconnaissance at decision points
Recon is most valuable when it resolves a real ambiguity: two target candidates, uncertain impact, or a changed battlefield state. Plot what you already know before spending it. That makes the resulting information interpretable and exposes which assumption it confirms.
Record the icon, time, and purpose of the request. Do not assume every map symbol has the same meaning across missions; consult the current legend and Tactical Map guide.
Plan around medals without guessing thresholds
Some medal or achievement goals may care about requisition, assistance, shot count, or speed. Check the live medal text. “Minimum Assets” and “Unaided Fire” are player search terms, but a title alone does not prove a numerical condition.
Complete the operation once before optimizing when possible. On a medal run, record starting resources, every request, and final result. That produces evidence for the Medal Requirements page without turning an incomplete community table into fact.
Requisition mistakes and recovery
If the wrong item arrives, do not automatically load it. Inspect whether the console permits another request and whether the operation can be restarted safely. If a shell is already committed, the Loading guide explains why recalculation or a controlled restart is safer than improvised unloading advice.
For a console that appears unresponsive, confirm focus, current objective, available resource, and public build. Capture the item, mission, and state for a report. Avoid deleting progress for an economy or interface issue.
Build a trustworthy inventory record
A publishable inventory row needs item name exactly as shown, category, current description, unlock condition, cost, mission/mode, public patch, and at least one observed effect. Unknown fields should remain unknown. Screenshot the live interface rather than transcribing from memory.
When a patch changes a value, preserve the older version label. That distinction matters more than presenting one apparently complete but versionless table.
For a quick console audit, photograph the available categories before and after one confirmed Challenge unlock, then identify the exact new row. This isolates progression from a mission-specific inventory change and produces an unlock observation without guessing an overall level table.