Strong
Official Roblox page, public Roblox API, in-game screenshots, creator group posts.
Proof
Proof board
A useful wiki is only useful if players can tell what is proven and what is still being checked.
| Claim area | How solid is it? | Current handling |
|---|---|---|
| Game name, creator, place and universe IDs | Strong | Published in source pages. |
| Weights, floors, brainrot money loop | Strong | Used in mechanics and guide logic. |
| Working codes | Not enough yet | No working code published until a fresh redeem screen appears. |
| Brainrot roster, income, rarity | Not enough yet | Kept as a notebook, not a rushed database. |
| Exact prices and formulas | Not enough yet | Waiting for current in-game screens. |
What counts
Useful lead
YouTube gameplay, update videos, comments pointing to questions players ask.
Weak
Copied code lists, unsourced tables, cropped images without context.
Useful proof
A good clip shows the whole screen long enough to identify the game, UI label, current value and the action that produced it.
Proof gaps that block stronger pages
| Page | Missing proof | What happens when found |
|---|---|---|
| Codes | Current redeem screen. | Move code into working or expired status. |
| Brainrots | Name, rarity and income screenshots. | Build a searchable roster and ranking notes. |
| Mechanics | Before and after upgrade tests. | Build formulas or calculators. |
| Updates | Event reward screens. | Expand update notes into reward guidance. |
Why this board helps rankings
The proof board is not just an editorial page. It explains why some pages are shorter, what data is missing, and how the site will grow. That gives search engines and players a clear maintenance story, while also preventing the site from publishing weak tables just to look large.
Confidence levels used by the wiki
| Level | Meaning | Example |
|---|---|---|
| Strong | Visible on official Roblox pages, public APIs or current in-game screens. | Game title, creator, place ID, product rows. |
| Useful | Good enough to guide testing, not enough for a final table. | A gameplay video showing a shop screen. |
| Weak | May point to a search trend but should not be published as fact. | A comment claiming a code. |
| Blocked | Kept out of mature pages until proof appears. | Exact income tables without screenshots. |
Why a proof board improves trust
Many Roblox guide pages hide uncertainty. This board does the opposite. It tells players which pages are ready and which ones are waiting for better screens. That makes the site look smaller in the short term, but it makes each published claim more reliable. As proof improves, this page becomes a growth map for the whole wiki.