The Blox Fruits source policy gives priority to official Roblox and Gamer Robot sources, then in-game verification, community confirmation and clearly labeled editorial estimates. Rumors, fake stock APIs and unsupported values do not become facts.
Evidence tiers
The Blox Fruits source policy uses four visible trust labels:
| Label | Meaning |
|---|---|
| Official | Official Roblox page, Gamer Robot announcement or official game channel. |
| In-game Verified | An editor tested the claim in game and recorded date, version and account context. |
| Community Confirmed | Multiple community sources agree and no official source contradicts the claim. |
| Editorial Estimate | Values, tier scores, demand or recommendations based on stated methodology. |
What official sources control
Official sources control developer, official game page, current official description, fruit roster baseline, level cap language and dealer timing language. The Blox Fruits source policy does not let a community page override official source material.
What community sources can support
Community sources can help map page inventory, names, route ideas and historical context. They are useful for cross-checking, but the site should still record checked date and confidence before publishing a claim.
What this site refuses to guess
This Blox Fruits source policy blocks fake live stock, unsupported code lists, invented values, exact drop chances without evidence, empty item pages, external trade ads and speculative update claims.