Walkthrough Notes
Steam and PC notes
Steam is the cleanest source for the PC page because it carries the live store metadata, feature tags, achievements, language support, demo relationship, and official screenshots. For PC guide pages, link Steam when making claims about features rather than relying on old reveal articles.
- Use Steam for release date, achievements, and store feature checks.
- Point PC players to demo and full-game save notes when troubleshooting.
- Do not assume a controller issue applies to every platform.
Xbox, Game Pass, and Play Anywhere
Xbox players have a different search intent: they often want to know whether the game is in Game Pass, whether progress is tied to the Xbox ecosystem, and whether the same purchase works across Xbox and Windows. Xbox Wire and the Xbox store should anchor those facts, with route and build advice staying platform-neutral.
- Answer Game Pass intent near the top of platform pages.
- Keep combat advice shared unless platform input changes the play experience.
- Link platform setup back to Start Here after the install question is solved.
Console and future mobile wording
Official community posts, the poncle FAQ, and console storefronts show the broader checked launch context across Steam, Nintendo Switch, Nintendo Switch 2, Xbox, and PlayStation. Nintendo also exposes a useful distinction: current official regional eShop pages can separate the base Switch listing from a dedicated Switch 2 version, and one checked regional page explicitly says Switch save data carries into the Switch 2 version. Mobile wording should remain cautious unless a current official mobile storefront is checked. Use "planned" or "not yet verified here" rather than promising a date that is not on the source list.
- Separate available platforms from planned or unverified platforms.
- Treat generic Switch support, separate Switch 2 storefront coverage, and save-transfer wording as different evidence types.
- Name Switch and Switch 2 only when official Nintendo storefront pages are the source.
- Keep controller-support and cross-save wording tied to the official FAQ instead of storefront assumptions.
- Use date-stamped source notes for any future mobile claim.
- Avoid mixing platform news with build tier changes.