Editorial & Verification Policy

1. People-first purpose

We publish for players, not crawlers. A page must answer a practical question, teach a system, document a tested route, compare options or provide a genuinely useful tool. Search visibility is a consequence of usefulness, not the reason a record exists.

Large structured databases can remain valuable inside an application without each record needing to compete as a standalone search result. Repetitive entity pages are therefore kept available to users while marked noindex, follow; strong hubs and original editorial guides remain indexable.

2. Evidence hierarchy

1. Current first-party documentation, patch notes and data published by the game developer.
2. Versioned game data or reproducible in-game testing tied to a stated build.
3. TKB first-hand operational experience recorded with enough detail to repeat.
4. Reliable specialist references with clear provenance.
5. Community reports, which remain provisional until reproduced or independently supported.

Conflicting sources are not averaged into a false certainty. The page records the conflict, prefers the stronger evidence and identifies what remains unknown.

3. Authorship and review

TKB Gaming is the publisher. Conroy1988 owns publishing decisions and first-hand product direction; MartyBlyth contributes development and technical review. Guide-specific pages may credit additional researchers, artists, testers or community contributors.

Automated systems may collect public version signals, generate structured pages, check links, build search indexes or run regression tests. They do not have authority to turn an unsupported claim into fact. Publication and material corrections require human review through the repository’s protected release process.

4. Original analysis

Facts alone are not enough. Indexable guides should explain consequences: which option is efficient, what prerequisite players commonly miss, how a system behaves under different conditions and where the evidence changes the recommended strategy.

TKB-created calculators, planners and maps must expose their data version and assumptions. Transformed official datasets are used to support analysis and tools; they are not presented as original ownership of a game’s intellectual property.

5. Patches and dates

Material records should state the relevant game version, evidence release or last-reviewed date. Automated drift monitors may alert maintainers to official changes, but alerts open a review rather than rewriting advice automatically.

When a patch changes a conclusion, we update the affected guide, preserve useful release history and rerun the relevant checks. Historical notes remain historical; they must not be mistaken for active runtime content.

6. Corrections

Readers can report an error through the contact page or a guide’s evidence desk. A useful report identifies the page, game version, disputed statement and supporting source or reproduction steps.

We assess the evidence, correct confirmed errors, note material changes where appropriate and leave unresolved claims visibly unresolved. Good-faith corrections are welcome; advertising relationships, popularity and contributor status do not determine the answer.