Sponsored link
ChameleonGame
References

Chameleon! Sources

Every table on this site names a source, and this page registers them all with a type and checked date. The primary reference is the official Roblox Games API for universe 10397566868, cross-read against the public game page; community trackers and searches fill the same-name picture the official page cannot give.

Source register

What we read, and when

A checked date means a human or scripted pass produced the data still in use; endpoints are re-read after every game update.

Up/down vote counts for the rating figure

Checked: 2026-10-10

Title tag, description text, page HTML checks for code/Discord/Trello mentions

Checked: 2026-10-01 capture; identity re-confirmed 2026-10-10

Ownership identity (group 127465947, verified badge)

Checked: 2026-10-10

Conflict table — what each "Paint or Die / Chameleon codes" article actually covers

Checked: 2026-10-01 capture; re-checked 2026-10-10

Conflict table — the Blumea [MUSEUM] Chameleon code list

Checked: 2026-10-01 capture; re-checked 2026-10-10

games.gg code article

Absent

Bot-blocked (HTTP 403) and already 404 at earlier captures; no usable list

Checked: 2026-09-27 and 2026-10-01 captures

YouTube results search

Search

Checking whether any video documents codes for this exact place (none found)

Checked: 2026-10-01 capture

Google News RSS

Search

Same-name September/October coverage from Sportskeeda, Dexerto and others

Checked: 2026-10-01 and 2026-10-10 captures

Tracking the independent fan-wiki landscape

Checked: 2026-10-01 and 2026-10-10 captures (unchanged)

Meccha Chameleon coverage (Steam/web)

Community

Lineage context for the official "Inspired by Meccha Chameleon" credit

Checked: 2026-10-10

Method

How claims earn a place on this site

  1. Place lock. A fact belongs to universe 10397566868 / place 74511210941284 or it does not ship. The description hash has stayed identical across every capture since August 2026, so renames (Chameleon! → PAINT OR DIE!) never silently change the subject.
  2. Official first. Name, description, stats, and update timestamps come from the Games API and the public page — both readable by any player, no account or special access needed.
  3. Conflicts stay visible. When a tracker's headline says one game and its link says another, the pages show both instead of averaging — see the codes conflict table.
  4. Absence is data. A code box, Trello, or Discord that six checks have never found is reported as a dated finding (“Absent, checked 2026-10-10”), never padded with invented substitutes.
  5. Recheck on update. The creator ships title-tag updates roughly twice a week; each one re-triggers the codes, links, and updates passes.
Source types

What this game has, and has not

Present and usable: the official Roblox page and its public API endpoints, the creator group page, third-party code trackers (used mainly to prove their lists cover other places), video and news searches, and independent fan wikis.

With no entry as of 2026-10-10: an official Trello board, an official Discord invite, a creator-run wiki, patch notes of any kind, and any code or redeem system. Those five stay registered as Absent findings with dates, because the fastest way to poison a fan site is to fill one of those gaps with a foreign game's content.

Corrections follow the same path as additions: send the page URL, the claim, and a checkable reference through the contact page, and an accepted correction ships with a fresh checked date.

Evidence classes

Three kinds of claim live on this site

Pages label which class a statement belongs to, so a capture never masquerades as official documentation and an inference never dresses up as either.

Documented

Written by the creator or Roblox itself: the description text, title tags, API stats, server size, genre. These claims change only when the source changes, and every change ships with a new date.

Example: the official loop lines quoted on the wiki pages.

Captured

Observations this site made by fetching a public source at a known time: a title tag seen on September 27, a tracker article's linked place ID, an absent Discord. They are historical facts about the source, re-verified after each update.

Example: the title-tag timeline on the updates page.

Inference

Player-facing conclusions drawn from documented mechanics: why color weighs 30% of the Camouflage Score, when a floor edge beats a wall. Tools and tactics pages carry these with their reasoning shown, never as hidden game data.

Example: the worked example on the calculator page.

Codes statusUpdate timelineCommunity linksAbout this site