METHOD
How this guide decides what to publish.
One rule runs through the site: a number we did not see in the client does not get published. Everything else follows from it.
The four marks
| Mark | Means | Where it appears |
|---|---|---|
| TESTED | We saw it on screen in a session we ran, with a timestamped screenshot | Page badge and the line itself |
| OFFICIAL ONLY | The developer's own wording, repeated as their claim | Quoted blocks and store-derived tables |
| NEEDS CHECK | Known to exist, details unconfirmed | Any row or section we have not walked |
| COMMUNITY INDEX | A name published by the community wiki, not verified by us | Every index page in the library |
A page takes the weakest mark of the claims on it, and a page that is mostly store copy says so at the top instead of pretending to be a measured guide.
How a session is recorded
A session means one browser window, one account-free playthrough, screenshots taken on the same machine within the same hour, and a note of the client version from the corner of the loading screen. A fact enters a page only if a screenshot shows it and the note records when. Two sessions of the same system are compared before either number is published as typical, which is why this site has so few numbers so far: the honest answer was zero. A mark moves for a page, not for a paragraph: one confirmed figure does not turn a community index into a tested page, and the header keeps the weakest mark until every claim on it has been seen.
What we will not do
We will not quote a number from a video, from another wiki, or from an aggregator that repeats the store blurb. If a figure matters it comes from the client, on our screen, with a timestamp.
We will not print a quest order we have not walked. Knowing a location exists is not the same as knowing how you get there, and a wrong order costs a player hours.
What we will say plainly
When the client hides a number — and it may, because the game sells perks — the page will say the number is hidden rather than fill the gap.
Status at launch
The site began on 2026-10-31 against client version 1791544558, while
the client was still loading on our connection. Pages published before the first session are
labelled as skeleton pages; the first measured tables will carry the date they were taken.