Editorial and verification policy
How sources, code status, testing and corrections are handled.
Evidence before a claim
Official game descriptions and developer announcements establish what the creator has published. In-game screenshots and repeatable tests establish what happened under recorded conditions. Community reports are attributed and not relabelled as our own tests.
For an individual fish page, we require a documented name, rarity, world, acquisition method and gameplay screenshot. A guessed list is not a substitute for a collection database.
Code status
Creator-listed means the code appears in our dated snapshot of the official description. Reported means code trackers say it works. Tested means a redemption was performed and its outcome recorded. Expired requires a documented expiry result or authoritative announcement.
We do not invent first-seen dates, rewards or expiry dates. First observed by this wiki is different from first released by the developer.
Dates and corrections
Source checked records when the cited source was reviewed. It is not a promise of automatic daily updates. A page’s modification date changes when its content changes.
Corrections should include the page, exact disputed claim, current game version or server date, and supporting evidence. Personal account information is not needed.