Official and versioned
First-party documentation, patch notes and developer-published data form the strongest baseline. Pages identify the relevant game build or review date so a later patch cannot silently masquerade as the same answer.
TKB Operations
Proof before confidence.
The Trust Centre explains how TKB Gaming separates verified guidance, versioned data, first-hand testing and unresolved research. Live coverage and roadmap cards replace this fallback when JavaScript is available; the publishing standard remains readable without it.
Return to TKB GamingHow to read a TKB guide
Tested and reproducible
Where official material is incomplete, TKB records direct in-game observations or versioned local data. A useful claim includes enough context to repeat the result and does not promote an estimate into a fact.
Provisional and blocked
Community reports and unresolved values remain visibly provisional. Missing evidence is treated as a boundary, not an invitation to generate filler. Records may remain searchable inside a tool while being excluded from search indexing and clearly labelled as provisional.
Current guide estates
Palworld
A complete visual Palpedia for all 287 obtainable Pals, plus Pal Lab comparisons and an interactive, evidence-pinned Atlas for Palpagos and the World Tree.
MissionChief UK
Operational reference for missions, units, personnel, infrastructure and planning. Structured dossiers remain useful inside the guide but are not promoted as thousands of separate editorial search pages.
DrainSim
Mission routes, equipment and recovery guidance built from game files, official information and directly tested behaviour. Community findings stay provisional until they can be reproduced or sourced.
Eco
Systems and server guidance tied to a stated build. The wider data-mined inventory is presented as an internal lookup utility; only field-verified records become standalone player guidance.
Crimson Desert
Original strategy, systems, world and technical guidance with evidence gaps left exposed. Generated record pages support internal discovery and remain noindex while carrying the same advertising-disabled boundary.
Release and correction process
1. Evidence enters review
Automated watches and reader reports can flag a possible change. They cannot publish a conclusion. A maintainer checks the source, affected version and practical consequence before changing guidance.
2. Protected checks run
Build, content, link, rights, privacy and route-policy checks guard the release. The site fails closed when an asset lacks permission, a protected route becomes monetised, or an advertising runtime duplicates.
3. Production is verified
Deployment workflows compare the generated release with the public site and verify critical pages independently. Material errors can be reported through the Contact page; the full research method is in the Editorial Policy.
Live coverage percentages and roadmap status require the current release data. If those cards do not load, use the direct guide links above; no core policy or correction route depends on JavaScript.