Abilities extend the Nest beyond direct shell fire. Official descriptions establish reconnaissance and battlefield-control options and say ammunition plus abilities exceed thirty unlockables. They do not publish a complete current cost or effect table, so the live console and operation remain authoritative.
2950790, Windows base-game public version 1.0, checked 2026-08-09. Ability names, costs, unlocks, durations, and precise areas are reported only when visible in the current game.Treat abilities as answers to uncertainty
Before spending, state the decision the ability should support. Recon can distinguish target candidates or confirm an impact. Battlefield control can address movement, pressure, visibility, or operational positioning when the current description says so. If no decision changes after use, the resource may be better saved.
Plot the existing evidence first. A new map icon is meaningful only when compared with observer lines, reference points, and the current objective.
Read the current card and console together
An ability card may communicate role while the Requisition Console communicates availability and cost. Check both and record the public version. Do not assume an icon means the same effect as a similarly shaped Demo icon.
Distinguish unlock from current availability. An item can exist in the wider progression yet be unavailable in a particular mission, Challenge state, or resource situation. A guide should not tell every new operator to select something the run has not unlocked.
Reconnaissance workflow
Mark the suspected target area and name what remains unknown. Activate recon through the current supported sequence, wait for the result, and identify its timestamp or stage. Add the new evidence without erasing the earlier plot.
Use recon to confirm, not to excuse poor origins. If the result contradicts hand geometry, review clue type and origin. The Triangulation guide gives a reproducible method for resolving that disagreement.
Battlefield control and repositioning
Players discuss emergency movement and other control options, but exact triggers and map consequences require public-build observation. When the Nest or firing origin changes, every old Nest-to-target bearing and range is stale. Replot and recalculate before the next shot.
Record before/after position, mission stage, ability name, cost, and any cooldown shown. Do not describe a reposition as universally safe from counter-battery or as a guaranteed medal strategy without repeatable evidence.
Combine abilities with ammunition deliberately
An ability can prepare a shot, confirm it, or change the battlefield after it. Define the order. Illumination or smoke ammunition may occupy a support role while remaining shells, not console abilities; keep the categories clear.
Wait for mission feedback between steps. Firing immediately after an ability without reading the new dispatch can apply an old solution to a new state.
Challenge and progression use
The developer FAQ says Challenge Missions offer varied situations and unlock ammunition and abilities. It also explains that a correctly completed run is saved after newspaper dismissal. Track which unlock appeared after which confirmed completion rather than assuming a fixed level table.
For leaderboard attempts, ability cost and time may interact with score, but exact scoring rules should come from the current mode display and reproducible runs. Complete cleanly before optimizing a guessed multiplier.
Build evidence without a fake database
For each observed ability, record exact label, category, displayed description, unlock state, cost, activation steps, visible result, mission/mode, and patch. A field can remain “not yet verified.” That is more useful than filling gaps with Demo values.
If an ability seems broken, reproduce with the same objective state and include whether a result icon appeared. Search current announcements and discussions, then report through the official hub with a concise sequence.
Audit an ability after a patch
Repeat one known use from a clean state and compare availability, cost, activation, map result, and persistence. If any field changes, update the evergreen ability record and link the official announcement; do not duplicate a stale value across mission pages. Keep screenshots with the public patch and mode so a Campaign restriction is not generalized to Challenge.