1. Sources
Each data bundle on the wiki is assembled from at least two independent sources. The usual combination is primary in-game observation (someone on the team plays the relevant section on Switch 2 and transcribes the data) cross-referenced against the public Serebii and Game8 Pokopia listings. Where the three agree, the entry ships. Where they disagree, we favour primary observation but flag the discrepancy.
Sprites and item icons come from Serebii’s public catalogue; they’re attributed on every relevant page via the image’s source path. We don’t re-host anything we can’t cite a source for.
2. What counts as verified
A record is considered verified when:
- The primary fields (name, slug, category, canonical ID) match in-game display verbatim.
- At least two external references agree on the derived fields (types, specialties, habitats, locations, ingredients, etc.).
- Screenshots or in-game footage exist for anything narrative — cutscenes, unlocks, dialogue.
Entries that don’t yet meet all three carry an explicit “unverified” marker — most visibly on a handful of recipe pages where ingredient lists couldn’t be cross-checked.
3. Update cadence
We target a 24-hour turnaround after every game patch for small corrections, and an end-of-week rebuild for larger data-bundle regenerations (a dex refresh, a new habitat wave, a post-patch balance pass). Mechanic changes are surfaced in the changelog on the same day we ship them.
4. Corrections
Spotted a mistake? Open the Discord and drop the correction in #corrections. Include a screenshot or a timestamped capture if the claim is contentious. A mod ack’s within a day, the underlying data file gets patched, and the wiki picks up the change on the next deploy. Corrections are called out in the changelog by slug so anyone linking to the old page can see what changed.
We don’t silently rewrite history. If a page had wrong data, we leave a note on the changelog entry so returning readers understand what was updated and why.
5. Editorial independence
WikiPokopia takes no sponsorships from games-industry companies. The one revenue line we run — a small Google Ads conversion campaign — pays for hosting and the Creator Program. No coverage is paid for, pre-shown, or embargoed in exchange for anything.
6. What we don’t do
- Ship datamine-only content ahead of its public release.
- Publish player-submitted lore or theory as if it were canon — if a claim isn’t in the game itself or in official Pokémon Company materials, it isn’t on the wiki.
- Accept paid inclusions in the Creator Program or on any entity page. All link-outs are editorial.