Trust
Corrections
Every fact on this site lives in one record and renders everywhere it is relevant. Correcting a mechanic updates its guide, the class pages that reference it, the builds that depend on it, and the Squad Builder's rules — all at once.
What helps most
Send evidence, not just a disagreement
A correction with a source attached can be acted on immediately. Without one it has to sit in a queue until someone can verify it.
- A link to the source — an official article, a developer statement, or a video with a timecode.
- Which page and which specific claim is wrong.
- For in-game observations: the game version, platform and difficulty.
- A screenshot, if the claim is about something visible in the interface.
Process
What happens to a correction
- Step 1
The source is recorded with its date, publisher and the exact location of the evidence.
- Step 2
The structured entity is updated — never just the page's prose.
- Step 3
Its confidence and version status are re-set.
- Step 4
A change record is generated listing every page the change affects.
- Step 5
The evergreen pages and the Squad Builder's rules update together.
- Step 6
A dated entry appears in the change log, linking to what moved.
On being wrong
This site publishes pre-release information about a game nobody outside Bit Reactor has finished. Some of it will turn out to be wrong, and some mechanics will change before launch.
When that happens, the old value is marked outdated rather than quietly deleted. Pages that had it keep their history, so you can see what changed and when — which is the only way to judge whether a source is reliable over time.