07
Evidence ControlSources, build context and conflict handling
Current buildBuild 0.3.1.12
Evidence Control Policy
How the DrainSim guide separates decoded facts, official information, testing, community reports and conflicts.
- Evidence
- Official
- Verified
- 2026-07-28
- Spoilers
- No spoilers
Evidence grades
Section titled “Evidence grades”| Grade | Meaning |
|---|---|
| Game-file confirmed | Decoded directly from build 0.3.1.12 assets, map actors, DataAssets or class defaults |
| Official | CodePeas, official Steam store text or official update notes |
| Directly tested | Reproduced by TKB through controlled play |
| Community field report | A cited Steam guide or forum result that TKB has not yet reproduced |
| Provisional | A useful lead with insufficient confirmation |
| Conflicting shipped data | Two decoded sources disagree; both values remain visible |
Source priority
Section titled “Source priority”For a player-facing value, use this order unless runtime evidence proves otherwise:
- Directly reproduced current-build behaviour.
- A current placed player-facing UI configuration.
- Current mission or tool DataAsset.
- Blueprint class default.
- Older static arrays and inherited defaults.
- Community guide or forum report.
Internal units
Section titled “Internal units”Decoded distances, force values, target heights and multipliers remain labelled as internal values unless the game or controlled testing establishes a player-facing unit.
Conflict example
Section titled “Conflict example”Pump Mk II stores 650 in its DataAsset but 800 in the current placed shop widget. The guide displays 800 as the current shop price and separately records the conflict.
Patch discipline
Section titled “Patch discipline”Every page declares:
- current DrainSim build;
- last verification date;
- evidence grade;
- spoiler level;
- whether review is required after a later update.