This page tracks changes that can be tied to an official Anomaly Detected source. The Experience is by BanuTheCat, belongs to Roblox universe 10391036163, and uses root place 126096010539917. Its public description says new contracts, anomalies, cases, and surveillance sites are in development. That confirms direction, not a release calendar. Dated checks below separate what an official page shows from what still needs a live comparison.
How to read an update safely
Use three levels of confirmation. First, identify an official source: the Experience, Roblox game data, enabled badges, the creator profile, or the X Core Studios group. Second, record the exact visible change and date. Third, compare the live game when the claim concerns rooms, controls, anomaly pools, Journal behavior, or mode tuning.
A Roblox updated timestamp is useful for deciding when to recheck, but it can move for reasons that are not a player-facing content patch. Do not infer a new chapter, changed probability, bug fix, or balance adjustment from that field alone. An enabled badge proves a named goal exists; its creation time is not automatically the chapter’s public launch time.
Use the Chapters hub for the five official chapter identities, the Anomalies hub for current spotting methods, and the Journal hub for before-and-after completion checks.
Official status snapshot
What to recheck after a change
Start with the contract selector. Record which chapter names and modes are visible and whether access differs from your last session. Then inspect the Journal for added slots or changed completion. Enter one familiar chapter and compare a known camera baseline before trusting a claim that a room or anomaly changed.
Verify controls on your own device. The three published zoom inputs may remain stable, but reporting, camera navigation, and interface placement can move. A current in-game prompt outranks an older screenshot. If a menu has changed, describe the new path and the device used.
For co-op, check lobby creation, player permissions, feed ownership, and progress feedback. Do not assume an update changed shared rules merely because a group run felt different. Reproduce the result in the same chapter and mode before presenting it as a stable behavior.
Report a useful version observation
A strong player report includes the UTC date, exact place ID, chapter, mode, party size, device, route to the feature, what happened before the change, what happens now, and whether it reproduced after rejoining. Leave out account secrets and private server links.
Screenshots should show the relevant interface, not another player’s private information. A short clip can help with moving shadows, flickering lights, or control behavior, but it should include enough context to identify the chapter and feed. One isolated frame cannot prove motion.
If the observation conflicts with the public description, state the conflict rather than forcing a conclusion. Roblox’s web page can show a stale or incomplete server panel while game data reports activity. Availability should be checked by launching the official place, not by one scraped sentence.
Creator-controlled checkpoints
The official Experience is the primary public description and launch destination. Confirm the creator name BanuTheCat and place ID before following a claimed update. The X Core Studios group identifies itself as the official group and names Anomaly Detected among its games.
Roblox game data is useful for identity, maximum server size, creation time, and last-updated time. Badge data is useful for exact goal names and enabled state. Neither endpoint is a substitute for patch notes. Dynamic player, visit, favorite, award, or win-rate values should always carry a retrieval time and should not be frozen into evergreen strategy.
The developer currently asks players to use the group for feedback, suggestions, bug reports, and feature ideas. Keep reports concise and reproducible. Do not treat a suggestion as a promised roadmap item.
Rumor filter
- “A timestamp moved, so a new chapter released.” Recheck the live selector and creator text; the timestamp alone is insufficient.
- “A badge was created on this date, so that is the patch date.” Creation supports chronology, not exact public release.
- “The description says coming soon, so a feature arrives next week.” No schedule is published.
- “A community list has an exact anomaly total.” Compare it with the current Journal and version before using it.
- “A code arrived with the update.” Require a creator-controlled string and a working in-game destination.
- “The web page says no running experience, so the game is shut down.” Launch the official place and compare current Roblox status before concluding that.
This filter lets players act on strong evidence without ignoring useful community observations. A report can be worth testing while still being labeled Community reported.
Update timeline
2026-09-15 — Official Experience metadata check
Type: Official status check
Roblox game data lists Anomaly Detected with universe ID 10391036163, root place 126096010539917, creator BanuTheCat, a maximum server size of eight, and an updated timestamp on September 15, 2026. The timestamp does not identify patch contents.
- The public description confirms the surveillance loop, solo/co-op play, zoom inputs, headphones, and future content direction.
- No official public code or redemption path was found in the checked Experience and group descriptions.
- Players should compare the live contract selector, Journal, controls, and familiar feeds for user-visible changes.
Source: Official Roblox game data
2026-09-12 — Chapter 5 badge family visible
Type: Official badge checkpoint
Roblox badge data shows enabled Chapter 5 – The Mall completion, Veteran, and Journal 100% Completion badges created on September 12, 2026. Each description includes “Half way there,” whose meaning is not explained by the API.
- The badge family confirms The Mall identity and its three named goals.
- It does not prove exact release timing, route completeness, room layout, or available anomaly entries.
- Check The Mall guide and the current game before drawing a progression conclusion.
Source: Official Roblox badge list
2026-06-25 — Experience record created
Type: Official identity checkpoint
Roblox game data records the Experience creation timestamp on June 25, 2026. This date establishes the public universe record; it is not used here as a claim about every testing or release milestone.
- The exact current title is Anomaly Detected.
- The creator identity is BanuTheCat.
- The X Core Studios group description names the game and invites feedback.
Source: Official Anomaly Detected Experience
Frequently asked questions
When was Anomaly Detected last updated?
Roblox game data returned an updated timestamp of September 15, 2026 during this check. That value is dynamic and does not explain the content of the update.
Are new contracts confirmed?
The official description says new contracts, anomalies, cases, and surveillance sites are in development. It does not provide names or dates.
Is The Mall released?
Its three official badges exist, but public badge metadata alone cannot establish the current live route or completeness. Check the contract selector and current creator announcements.
Where should I report a problem?
The X Core Studios group description invites feedback, suggestions, bug reports, and feature ideas. Do not share passwords, cookies, or private account information.