Primary sources first
Release date, price, platform, system requirements, language support, and developer details should come from the Steam store page, Steam news, Steam community posts, or other sources that clearly identify the game and app ID. SteamDB can help cross-check store metadata, but player-facing facts should still point back to Steam whenever possible.
If a third-party article or video introduces useful context, it should be treated as supporting material rather than the final authority for release facts. The guide can link to that material, but dates, platform claims, system requirements, and patch status should be checked against Steam before they are repeated as facts.
Hands-on guide limits
Strategy pages should be based on public mechanics and repeatable play observations. Hider and Seeker pages can explain fundamentals such as color matching, silhouette checks, room scanning, and version checks. They should not invent map-specific hiding spots, exploits, or best routes before enough public play data exists.
A good guide update should help a reader make a decision in the next round: where to stand, what to scan, how to host, what to update, or which official page to check. If a note does not help with a real player task, it should probably stay out of the main guides until more evidence exists.
Corrections
If Steam news, the store page, or later patches change a detail, the affected guide page should be updated with a date and a link to the source. Older assumptions should be removed rather than preserved as confusing footnotes.
What counts as a good strategy source
For strategy, a good source is repeatable play rather than a single lucky clip. A hiding tip is stronger when it works across several rounds or when both Hider and Seeker perspectives explain why it works. A seeker tip is stronger when it identifies a visual signal players can actually check, such as outline, placement, color seams, or repeated prop logic.
This policy keeps the site useful as MECCHA CHAMELEON changes. If patches alter rooms, visibility, matchmaking, or role behavior, older advice should be retested before it stays on the page.
Video and community material
Videos are useful for seeing MECCHA CHAMELEON in motion, but this site should not copy transcripts or present one creator's round as universal strategy. Video observations should be rewritten as original advice and linked back to the creator when the video is the reason a reader may want to inspect the moment directly.
Community posts can reveal common problems faster than official pages, but they also include guesses. For troubleshooting pages, the guide should separate confirmed fixes from reports that still need testing.
Page publication standard
A new page should be published only when it can stand on its own as useful player help. For this site, that usually means a confirmed fact, a clear gameplay question, a repeatable troubleshooting step, or enough observed play to explain a pattern. A title alone is not enough reason to create a page.
This is especially important for map guides. Until a map has stable public information and enough testing, the site should avoid thin pages that name a map but do not teach a player what to do.