Helldivers Field Manual
Editorial method

Sources, Testing & Corrections

How this field manual separates official facts, direct checks, community evidence, editorial judgment, and unresolved claims.

Priority

Source order

  1. 1. Arrowhead patch notes and official Known Issues.
  2. 2. PlayStation, Steam, and Xbox official announcements.
  3. 3. A recorded in-game check with build, platform, and date.
  4. 4. A maintained community database.
  5. 5. Repeatable community testing.
  6. 6. Videos, forum posts, and general guide sites as discovery sources.

A lower source can add context. It cannot silently overrule a current official statement.

Claim labels

Evidence labels

Official

Arrowhead, PlayStation, Steam, or Xbox states the fact.

In-game verified

A contributor records the build, platform, test condition, and result.

Community tested

Repeatable player testing is useful, but is not presented as an Arrowhead statement.

Editorial recommendation

The page makes a practical choice from cited evidence. It is not an official ranking.

Unverified

The claim is disputed, incomplete, or not reproducible and stays uncertain.

Affected by known issue

The item or mechanic is named in Arrowhead's issue list, so recommendations must warn readers before ranking it.

Discovery only

How YouTube is used

Videos help discover player questions, test conditions, and comparisons. This site does not copy transcripts, reproduce another creator's structure, or treat opinion as official.

  • Record upload date and game build.
  • Identify the exact test.
  • Compare it with an official or second independent source.
  • Label it Community tested when not reproduced here.
  • Exclude claims that cannot be separated from speculation.
Conflict handling

Conflicting information

  1. 1. Preserve the official statement.
  2. 2. State the conflict.
  3. 3. Do not average incompatible numbers.
  4. 4. Show the build and date.
  5. 5. Keep disputed fields Unknown until resolved.
Date discipline

Four different dates must not be collapsed into one

Source publication date

When a page or announcement first became public.

Source modified date

When the publisher last edited a page. This does not prove a patch, event, or item launched that day.

Game event or release date

When a patch, Warbond, campaign window, or platform release actually became applicable.

Site verification date

When this site re-read the source and checked the page-specific claim.

A support article updated on September 6 is recorded as a September 6 source review. It is not renamed into a September 6 game patch unless the source says a patch shipped.

Future content

Roadmaps and previews

  • Released: live and supported by a release source.
  • Planned: shown by an official roadmap or announcement.
  • No exact date: a month or broad window is known, but not a day.
  • Unconfirmed: community interpretation, leak, or unresolved report.

Unnamed roadmap content does not receive a definitive entity page.

Access record

Video evidence level

Every video citation records what was actually available: title and description, readable official captions, a manually viewed segment, an embed without transcript, or an inaccessible/removed source.

No timestamp or unseen control detail is added unless it was visible or supported by caption data.

Maintenance

Corrections and change logs

A correction must identify the page, claim, evidence, and build. Update-sensitive pages keep a short visible change log with the date, changed field, and reason.