1. Start with official sources
NPC Studio's website, Steam store page, Steam News posts, and published patch notes are the first stop for release status, features, update changes, and official destinations.
An official source only supports what it actually says. A general feature statement does not prove an exact gift, birthday, schedule, or tool rule.
2. Confirm gameplay details
When a useful gameplay detail is not stated by the developer, we check it against the current game build before publishing it as a guide fact.
Community pages can point us toward a value to check, but a copied table or repeated claim is not treated as independent confirmation.
3. Attach a version and review date
Guide pages show the game version and the date used for the latest review. Volatile details are re-checked after relevant patches instead of being presented as timeless facts.
If two credible observations conflict, the disputed value stays out of the public answer until it can be resolved.
4. Generate tools from one data source
Interactive tables and checklists are generated from the same accepted data used by their related guides. We test counts, relationships, links, storage behavior, and the final built HTML so a second hand-maintained table cannot drift away.
For example, the gift-by-item lookup is inverted at build time from the governed character gift relationships rather than copied into a separate list.