This page records what the guide can safely say from current sources, and where the guide must avoid inventing details.
Steam app 4704690 describes MECCHA CHAMELEON as an online PvP hide-and-seek game. Players split into Hider and Seeker teams; Seekers win if they find everyone within the time limit; Hiders paint their white body to blend into the stage. The page also mentions public/private servers, friends or strangers, streamer viewer participation, and 2-10 recommended players.
Use current pages before making patch-sensitive claims.
The guide can safely say the game is on Steam, is paid in the checked Steam API region, is an online PvP hide-and-seek game, uses Hider and Seeker teams, asks Hiders to paint their white body to mimic the stage, supports public matching, supports private/friend play, and welcomes gameplay videos and streaming under the listed title/link notes.
Do not invent exact best hiding spots, map names, Workshop popularity lists, server UI steps, permanent max-player limits, patch behavior, official strategy terms, or best paint formulas unless a current source or direct gameplay check supports them.
Revise affected pages when the Steam page changes, Workshop pages show new map behavior, official posts clarify rules, or repeated player reports reveal a concrete question the site does not answer. Update the checked date and only change the affected task page.
Do not create free download, cracked build, key, coupon, cheat, or guaranteed reward pages. If users search for those terms, answer with a boundary and route them to official storefronts or support channels.
The source log separates stable game concepts from update-sensitive details. Stable concepts include the broad Steam description: online PvP hide-and-seek, Hider and Seeker teams, white-body painting, hiding spot, pose, artistic skill, and public or private play. Update-sensitive details include price, supported languages, requirements, Workshop items, exact room behavior, player limits beyond the recommended range, and any map-specific claim.
When this guide is updated, the editor should first verify the current Steam store page or Steam Community page, then change the public guide only where the source changed. If a detail cannot be verified, the page should present a decision rule instead of pretending to know the exact answer. That is why several guide pages say to check the live Steam page before purchase or custom-stage decisions.
Every future edit should ask four questions. Is the claim still visible on the live Steam page, Steam API, official publisher channel, Workshop page, or current gameplay check? Is the claim stable enough for a general guide, or is it tied to one patch, one custom map, one host setting, or one region? Does the claim help a player complete a task, such as buying safely, joining a room, understanding roles, or improving disguise? Could the same page answer the question with a safer checklist instead of an unsupported exact statement?
This matters because a young game guide can easily become lower quality by trying to sound complete too early. Exact map lists, hidden mechanics, permanent player limits, or specific UI button paths should not be treated as permanent unless current evidence supports them. If evidence is weak, the public page should say what to verify and where to verify it. That policy is less flashy than a fake complete guide, but it protects players from bad downloads, outdated Workshop claims, and confident strategy pages that cannot survive the next update.
The source log therefore acts as a boundary, not decoration. It tells readers why the guide is cautious and tells future editors what must be rechecked before expanding the site.
The guide should expand only when a new page can answer a real player question with evidence. Good expansion candidates include repeated Steam Community questions, a new official update that changes room behavior, a Workshop pattern that needs a safe evaluation checklist, or a beginner problem observed in current gameplay. Weak expansion candidates include copied keyword lists with no player task, map names that cannot be verified, and pages that promise free downloads or secret advantages. This rule keeps future pages useful even when the site grows beyond the first launch set.
Readers can use this page to challenge any guide detail. If a page gives a precise claim but the source log only supports a broad rule, the precise claim should be treated as provisional and rechecked before it guides a purchase, room plan, or custom-stage choice.