This page separates verified source existence from guide interpretation. It is part of the guide's safety boundary.
What sources prove: the game exists, public pages discuss it, and players need careful source boundaries. What sources do not prove: permanent room mechanics, official terminology, best routes, or future balance.
Use current pages before making patch-sensitive claims.
When a patch, official post, or high-quality community finding appears, update only the affected page first. Add the date checked, the source type, and the reason for the change. Do not rewrite the whole site unless the core game loop or public vocabulary changes.
If a claim cannot be traced to official material, current gameplay, or repeated community evidence, mark it as guide interpretation. This protects the site from becoming a thin rewrite of search snippets.
Add new guide pages only when they solve a distinct player problem. Good candidates include beginner movement mistakes, multiplayer friction, map/room vocabulary, or paint decision examples. Avoid fake codes, download pages, coupon pages, or any page that implies free access to the game.
When adding a page, start with the player job, list what is known, and separate direct observation from interpretation. A useful small page is better than a broad page that repeats the same advice without examples.
This page can show where the guide is cautious, what source types were considered, and which claims need rechecking. It cannot prove the best route, final balance, or universal multiplayer meta.
The practical question is modest: does the guide help a player make a better next decision? If not, the answer should be revised, shortened, or moved out of the public guide.
Every major guide page links back to this source log so readers can check boundaries before trusting patch-sensitive claims. This is part of the site architecture, not decoration.
Return to the guide hub, beginner guide, or paint tactics when applying these source rules.
Official store pages are good for release status, supported platforms, publisher/developer naming, and broad descriptions. They are not enough to write advanced tactics. Community posts are good for discovering friction and vocabulary. They are not enough to state universal mechanics. Direct gameplay checks are good for current behavior, but they still need a checked date because patches can change details.
When expanding the site, label the source type in your notes before writing content. This keeps the next editor from treating a community complaint as an official rule.
Record the date, the page changed, the claim changed, the source type, and the reason. A compact log is enough. Example: "2026-06-25, paint tactics, added over-switching drill, guide interpretation based on current practice framework." This is more useful than a vague "updated content" note.
Revision notes are especially important for game guides because pages can change quickly. Without a source log, pages can start to disagree, old claims can stay live, and future corrections become slower.
The source page is the memory layer for this guide. It helps readers understand which claims are official, which are community-informed, and which are guide interpretation that should be tested in play.
If a future update changes how players describe routes, rooms, colors, or multiplayer roles, this page should make it easier to revise the right guide page without changing unrelated advice.
Do not publish free download claims, key claims, code pages, guaranteed reward claims, or claims of official access. Do not imply that the site is official. Do not copy review copy as if it were original testing.
If users search for unsafe or misleading terms, answer with a boundary and route them to official storefronts. A safe boundary page is better than a risky traffic grab.
A beginner-help page can rely on cautious guide interpretation and current play checks. Official availability should come from official storefront sources. Exact mechanics need direct verification before they become recommendations.
This prevents the common failure where a guide adds pages faster than evidence. The source log should slow down risky claims while allowing safe, practical advice to improve quickly.
2026-06-25. Re-check after patches, major reviews, multiplayer changes, or new official documentation.
This site does not claim official affiliation, free access, secret keys, guaranteed rewards, or permanent best routes.