Corrections

PalSphere is a living database. Wrong stats, missing recipes, and stale guide claims get fixed on the next verified rebuild. This page explains how to report issues and what happens next.

How to report

• Use Contact with the exact page URL.
• What you expected versus what you saw.
• Game version or patch if the issue is version-specific.
• Screenshots when a UI bug is hard to describe in text.

Verification

We re-check reports against the current client extract before changing published numbers. Community charts alone are not enough; native tables win when sources conflict.

Revision

Confirmed fixes land in the next data rebuild. The extract stamp in the footer and on /data advances when catalogs ship. Methodology for how catalogs are built is on /methodology.

Visible notes

Where a field is unresolved or placeholder in source tables, entity pages say so instead of inventing a value. Guide provenance strips call out the extract used for rankings and tables.

Response expectations

We read every report. Simple typos and clear extract mismatches usually ship in the next rebuild; deeper research may take longer. We do not publish a public inbox on the site — Contact is the canonical channel.