Source table
The source hierarchy is intentionally strict. Roblox API data wins for the live title, place identity, visits, favorites, max players, update time, and the current public description. The official Trello wins for detailed gameplay lists because it exposes the highest-volume structured data: fruit cards, swords, races, NPCs, locations, events, gamepasses, ships, and boss notes.
Third-party sites are used only for fast-changing code cross-checks. They are useful because code pages update daily, but they can conflict with each other. When a code appears in two or more July 2026 trackers it is presented as stronger; when only one tracker lists it, the page labels that narrower source.
Do not use private screenshots, unsourced Discord reposts, or old Haze Piece videos as primary proof for live gameplay claims. They can guide research, but they need to be reconciled against the current Roblox place and official Trello before changing a wiki row.
For route pages, prefer public structured notes over guesses. If a location card only names the island, this wiki keeps the island as a map anchor and explains useful links from related NPC, boss, sword, or event cards rather than inventing level ranges.
| Source | Use | URL |
|---|---|---|
| Roblox public game API | Current title, description, visits, favorites, max players, update date | Roblox game page |
| Haze Studios Roblox group | Creator/group identity and member count | Roblox group |
| Official Trello board | Fruits, swords, races, locations, NPCs, bosses, events, gamepasses | Official Trello |
| Roblox badges API | Sea 3 and level milestone signals | Roblox universe |
| Code trackers | July 2026 code cross-check | Beebom / Destructoid / GamesRadar |
Refresh workflow
Use this workflow when the game updates or a player reports stale information. The goal is to prevent one changed code, one renamed island, or one new Trello card from causing broad unverified edits across the site.
A correct refresh starts with identity, then gameplay data, then volatile rewards. First confirm the Roblox place still resolves to the same universe and official title. Then refresh Trello cards and badge data. Only after those are stable should the codes page be updated from current trackers or in-game tests.
If a claim cannot be verified, keep it out of the main route tables. Add it to a conflict note, unreleased context, or TODO item until there is enough public evidence. This is especially important for codes, drop rates, level gates, and event timers.
| Step | Check | Why it matters |
|---|---|---|
| 1 | Roblox place and universe identity | Prevents mixing Haze Piece/Haze Seas with clones or unrelated One Piece Roblox games. |
| 2 | Roblox description and update date | Confirms live title, platform notes, fruit spawn rule, and current public status. |
| 3 | Official Trello JSON | Refreshes fruits, bosses, NPCs, locations, ships, events, gamepasses, and unreleased markers. |
| 4 | Roblox badges | Confirms milestone signals such as Sea 3 or level-cap movement. |
| 5 | Code trackers and in-game reports | Handles volatile rewards only after the current game identity is confirmed. |
| 6 | Build, validation, and browser check | Makes sure sitemap, images, links, and mobile reading still work after content changes. |
Primary source shortcuts
For gameplay systems, start with Trello because it contains the richest public structure. For live status, start with Roblox because it owns the title, update timestamp, player count, and current description. For codes, compare multiple current trackers and keep conflict labels visible.
When deciding whether to trust a claim, ask what kind of fact it is. A title, place ID, visit count, or platform support claim should come from Roblox. A fruit skill, boss spawn, NPC location, gamepass effect, or ship speed should come from Trello. A code claim should show recency and ideally an in-game redemption date.
This division keeps the wiki honest. It also makes future updates faster because each page has a clear source owner instead of a pile of copied text from mixed articles.
