Source method
Official facts lead; gameplay helps us find the real question
A video can reveal where a button sits or identify an encounter. It does not automatically prove a permanent rate, drop table, or rank.
Game facts checked August 4, 2026
Evidence ladder
How a claim reaches a page
| Source | What we use it for | Boundary |
|---|---|---|
| Official Roblox experience | Core loop, update note, platforms, developer identity. | A short description cannot support missing formulas or tables. |
| Roblox public APIs | Place/universe IDs, genre, server size, public counters, dates. | Live counters are snapshots and receive a checked date. |
| Official thumbnails | Recognizing the game and illustrating named systems. | Promotional numbers are not treated as universal stats. |
| Public gameplay | UI location, boss-name leads, player problems, test ideas. | Edited thumbnails and one-off outcomes do not become facts. |
| Community code reports | Strings worth trying and troubleshooting. | Rewards and expiry stay unconfirmed until supported. |
Current record
Research is kept outside the prose
The internal claim bank stores the URL, capture date, source type, and allowed wording. Readers see the useful conclusion, not a dump of research notes. The verified public destinations are on Official Links; page-level uncertainty stays next to the claim it affects.