Skip to content
Method / version 1.0

Editorial
policy.

These rules exist so a reader can tell the difference between a fact, a build-specific observation and a guess. They apply to every page.

1. The three confidence levels

LabelMeaningExample
ConfirmedStated by the developer or publisher, listed on a storefront, or visible in an official screenshot.The December 2, 2026 Early Access date.
Playtest buildObserved in a public playtest or demo, often documented in official patch notes. Values may change.Telekinesis targeting dropvines.
UnverifiedReported or implied but not corroborated. Kept out of recommendations.Unconfirmed boss mechanics or item stats.

Every database record and guide carries one of these labels. A page can contain confirmed facts and open questions at the same time; the label describes the core claim, and the “Open questions” section lists the rest.

2. Source hierarchy

  1. Current official store listing, developer post, patch note or publisher release.
  2. Official screenshots and in-game UI captured by the developer or publisher.
  3. Dated interviews with named developers.
  4. Dated press coverage that quotes official material.

We do not cite other fan wikis, datamined files, leaked builds or anonymous comments. If a claim appears only on another fan site, it is not evidence.

3. Conflict resolution

Newer official material beats older marketing. Patch notes beat launch trailers. A visible screenshot beats a prose description. If two official sources still conflict, both values are shown with the reason — for example, the Stone Mallet’s 20 durability in the crafting view and 6 / 100 on the finished tool card.

4. Numbers we will not invent

  • Search volume, keyword difficulty or traffic estimates.
  • Drop rates, spawn rates, HP, DPS or exact damage values not shown in official material.
  • Playtime beyond the developer’s own estimate.
  • Review scores or user ratings before release.
  • Prices, pre-order bonuses or console dates that have not been announced.

5. Images

We use official screenshots and logos for identification and commentary, with credit. When an entity has no official image, we publish an original field diagram labelled as such. We do not fabricate gameplay screenshots, recolour another game’s assets, or use AI-generated “gameplay” images.

6. Tools and calculations

Each tool states its inputs and shows its arithmetic. The system checker compares against published specs; the cook calculator multiplies the published recipe; the loadout planner maps roles to documented needs; the path comparison uses confirmed design differences. None of them claim to predict performance or balance.

7. AI disclosure

Research summarisation and drafting are assisted by AI. Every published claim is checked against the linked source, and the confidence label reflects the source rather than the tool. This is disclosed because a wiki’s value is its trustworthiness, not its production speed.

8. Corrections

Corrections are published with a date. Send the official link and the specific sentence that is wrong. We will not silently rewrite a page; the record of the change matters.

9. Independence

This site is not affiliated with Pokuch or META Publishing. Advertising, if enabled, is clearly labelled and does not influence coverage. No publisher has editorial input.

10. Review cadence

All records carry a verification date. The archive is re-checked at major beats: playtest patches, the Early Access launch, and each content update. Records that cannot be re-verified are marked stale rather than left to look current.

Last policy review

17 November 2026 · Blind Descent Field Guide

Type to scan the archive

Try “telekinesis”, “sausage”, “crab”, “co-op”

Index covers — recordsVerified entries only