This unofficial Experience Abstraction wiki publishes official Roblox facts first, labels player reports separately, and holds any route, map, code, timer, or character claim until it can be checked against a reliable source or reproducible hands-on session.
How this Experience Abstraction wiki checks facts
This site is an unofficial fan-made information hub. It is not operated by Roblox, @pawlooz, GLITCH Productions, or The Amazing Digital Circus. The first source used for Experience Abstraction identity, creator, inspiration, and the three listed Abstraction conditions is the official Roblox experience page. This Experience Abstraction source policy keeps the same standard for every future page. The Experience Abstraction source policy is also the place to check when a claim sounds more specific than the source.
The page was checked on July 11, 2026. It identified the experience and reported no running experiences at that time. Because that availability signal can change, the site records the check date instead of treating it as a permanent launch or shutdown statement.
Evidence levels
Official means the claim appears on a Roblox listing, creator post, or clearly attributable official channel. The three ways to Abstract are official because the Roblox description states them.
Tested means a claim has been reproduced in the experience with a date, conditions, and enough detail for another player to understand the limits. A tested observation is not automatically an official rule, but it is stronger than an unverified rumor.
Reported means a community player or video has raised a useful lead. Reports can help this site discover questions such as Caine, Cellar, or a new route, but they do not confirm the answer by themselves.
Held means the topic is important enough to watch but not safe to publish as a fact. Held topics currently include Caine, Cellar, maps, codes, exact timers, device support, private servers, and route guides.
Why popular pages are missing
The supplied research brief contains a larger page plan, including Caine, Cellar, maps, screenshots, and experiments. That plan is useful for future work, but the official source checked here does not confirm those in-game details. The Roblox page also reported no running experiences, so a hands-on test was not available during this build.
Publishing a polished route without evidence would make the site look complete while giving players a fragile answer. This tracker chooses the smaller useful set: current status, official platform identity, the public gameplay signal, the three conditions, media status, updates, FAQ, and this policy. The Experience Abstraction source policy is visible so the boundary is part of the guide, not hidden in an editor note.
Update process
When the official Roblox page changes, recheck the title, creator, description, running-experience state, and attached media. Record the date. If a community claim points to a new mechanic, find an official source or reproduce it in a playable session before promoting it to a published guide. Keep exact numbers, maps, and routes marked unknown until the evidence supports them.
Read the official Experience Abstraction Roblox page and the current status page before relying on older search results. Return to this Experience Abstraction source policy whenever a new route or character claim appears.