A database with visible limits

This IRON NEST database is a source-qualified operator index, not a copied encyclopedia. Every database record has a type, public name, short use case, route, evidence status, check date, and one or more source identifiers. The database currently favors stable official facts, directly observed source text, and clearly labelled community references. It does not turn a competitor table into fact merely because that table looks complete. A smaller database with inspectable boundaries is safer to use and cheaper to maintain.

The database separates game facts from product discovery. Competitor sites helped identify useful page patterns and missing workflows, but their selections are not the evidence behind this public database. Official store and news records support official claims. Community guides support attributed community claims. A removed guide can support only a stale reference with a warning. This database design lets an operator see what is usable now, what needs current-client confirmation, and what remains intentionally absent from automation.

Mission database index

The mission database contains seventeen titles documented in the current public gold-medal guide: fifteen campaign names and two Skirmish variants. The database treats those names as community evidence because the source is a player guide, not an official machine-readable mission list. A database title is not a promise that every objective, coordinate, medal threshold, or enemy position has been verified. Only focused routes with enough evidence and a complete operator procedure enter the public sitemap.

Use the database mission index to find an existing guide or to name a private Console record consistently. Do not infer mission order, objective text, or current behavior from database position. Mission 2 and Counter-Battery have focused help because public discussions expose specific operator problems. Other database names link back to the mission hub until their current evidence can support a useful page. This prevents the database from creating thin pages that add maintenance work but no reliable answer.

  • Calibration Fire: Opening calibration mission and gunnery qualification. Status: community.
  • Fire and Light: Early mission involving spotter bearings and target plotting. Status: community.
  • Liberation: Campaign mission listed in the community medal guide. Status: community.
  • Counter-Battery: Counter-battery mission with a time-pressure objective. Status: community.
  • Iron Road: Campaign mission listed in the community medal guide. Status: community.
  • Siege of Cartagena: Campaign mission listed in the community medal guide. Status: community.
  • The Gorge: Campaign mission listed in the community medal guide. Status: community.
  • Rock of Gibraltar: Campaign mission listed in the community medal guide. Status: community.
  • Dead Reckoning: Campaign mission listed in the community medal guide. Status: community.
  • Fire on Call: Campaign mission listed in the community medal guide. Status: community.
  • High Tide: Campaign mission listed in the community medal guide. Status: community.
  • Blind Fire: Campaign mission listed in the community medal guide. Status: community.
  • Phantom Battery: Campaign mission listed in the community medal guide. Status: community.
  • Final Harvest: Campaign mission listed in the community medal guide. Status: community.
  • White Shells: Campaign mission listed in the community medal guide. Status: community.
  • Skirmish - Challenge - Counter Battery Timer: Challenge Skirmish variant listed in the community medal guide. Status: community.
  • Skirmish - Chill - Uncontested Front: Chill Skirmish variant listed in the community medal guide. Status: community.

Ammunition reference subset

The ammunition database publishes five codes found in a community operator guide: AP, HE, HCHE, SMK, and STAR. Steam currently marks that source as removed or incompatible, so each database item is explicitly stale. The five codes are a documented subset, not a complete current arsenal. The database does not publish damage, radius, cost, unlock, charge, or effect numbers because the available evidence does not meet the current-client threshold for those claims.

Use this database subset as a search aid, then read the current game interface before selecting a round. The official store advertises a combined total of thirty ammunition types and abilities, but it does not publish a verified split. That official claim cannot be converted into a shell count. The database keeps both statements separate: official combined scope on one record, stale named references on another. This is more honest than merging incompatible evidence into one confident table.

  • AP shell: Armor-piercing ammunition code documented by a community guide. Status: stale.
  • HE shell: High-explosive ammunition code documented by a community guide. Status: stale.
  • HCHE shell: HCHE ammunition code documented by a community guide. Status: stale.
  • SMK shell: Smoke ammunition code documented by a community guide. Status: stale.
  • STAR shell: Illumination ammunition code documented by a community guide. Status: stale.

Operator systems

The systems database organizes target plotting, teleprinter intelligence, and Nest position calibration. Target plotting and command reports are supported by the official gameplay description. Nest calibration is a popular community method and stays attributed as such. The database links each system to a guide instead of repeating a shallow definition. A system record answers where to continue, which evidence supports the route, and when that evidence was last checked.

Future database automation should update one system record only when its source scope changes. It should not rewrite stable geometry after every news post. The database separates deterministic map mathematics from version-sensitive game behavior, so a patch that changes an interface can trigger a targeted review. This system boundary reduces false alarms and prevents one weak social post from contaminating the entire database. Unknown mechanics remain outside public calculation until stronger evidence appears.

  • Target plotting: Convert map coordinates or observer bearings into a Nest firing solution. Status: official.
  • Teleprinter and intelligence: Read command traffic and frontline reports before plotting a target. Status: official.
  • Nest position calibration: Community-documented method for establishing the Nest origin on the map. Status: community.

Official patch records

The update database currently includes official Patch 1.0 builds 1558 and 1547. Each database record stores the visible build label, a narrow paraphrase of affected areas, the official news source identifier, and the common check date. The database is not a full reproduction of patch notes. It captures enough scope to decide which guides may need review while sending readers to the official source for the complete wording.

A new official patch should enter the database before it changes public guidance. The maintenance pass compares current official fields with the previous database snapshot, identifies affected systems, and checks only the routes that depend on those systems. If the news endpoint is unavailable or malformed, the database check fails visibly. It does not silently preserve a current label or publish a guessed update. This fail-fast rule keeps unattended maintenance understandable.

  • Patch 1.0 (1558): Official stability and input fixes plus a motion blur toggle. Build 1.0 (1558). Status: official.
  • Patch 1.0 (1547): Official localization, briefing, aiming, UI, and progression fixes. Build 1.0 (1547). Status: official.

Read database evidence status

Official means the linked first-party source supports the exact database claim. Corroborated means independent sources agree within a stated scope, although none alone is treated as official. Community means a player source supports an attributed database observation. Unverified means evidence conflicts or lacks current-client proof. Stale means the source age, compatibility warning, or version context makes the database record unsafe for current behavior without rechecking.

Status controls wording and features. An official database record can state the supported fact directly. A community database record says that a guide or player reports it. A stale database record may remain searchable because it helps identify a label, but it carries a warning and cannot drive automatic recommendations. An unverified formula can explain why automation stops, but it cannot power a calculator. These rules reduce review time because the publication boundary is encoded in the record.

Missing data is an explicit state

A blank database field should not be filled by the first available page. Numeric ammunition statistics, exact objective thresholds, hidden unlock rules, and current coordinates need direct current-client evidence or an official source. If that evidence is missing, the database omits the field. If two sources conflict, the database records the conflict and blocks dependent automation. Approximate content can be useful only when its uncertainty is visible and the action it drives is low risk.

For unattended updates, official changes have the highest database confidence. Multiple independent community sources can raise confidence for a problem statement, but interaction counts alone do not prove a mechanic. A single anonymous claim can enter a private candidate queue, not the public database. The scheduled Codex task should fetch, compare, classify, test, and deploy only records that clear the evidence rules. That workflow keeps the database useful without creating a daily human review obligation.