The solo creator behind Anomaly Detected goes by the handle BanuTheCat, and figuring out who runs the cameras is half the fun of joining the community. This page gives you the verified identity, the official links, and the exact channels where the anomaly detected developer posts patch notes, reads feedback, and replies to suggestions — all without the guesswork that the game is famous for.
Who Is the Anomaly Detected Developer Behind BanuTheCat?
The anomaly detected developer ships every chapter, every camera layout, and every audio cue from a single Roblox account. Knowing exactly who that is — and where they post — is the fastest way to verify patch notes and avoid fan-run impostor channels that recycle old changelogs.
The Verified Roblox Profile and Studio
The anomaly detected developer behind the game is BanuTheCat (Roblox userId 8212131806), an independent creator rather than a large studio. Their verified profile appears on the community walkthrough: Roblox Anomaly Detected Chapter 2 Grinding (Cr1ms0nX) right next to the developer avatar, which is the only place Roblox itself stamps a creator identity to a place. BanuTheCat also owns and moderates the group X Core Studios (groupId 1065061064), which is listed as the "official X Core Studios group" on the Roblox group hub.
X Core Studios is small: at last verification, the group carries only the developer handle, the community curator, and a handful of trusted playtesters. Because the group is the only social module the developer controls directly on Roblox, every group post is effectively a BanuTheCat post. Players searching for the anomaly detected banuthecat profile from a third-party wiki or Discord invite are usually being routed to one of two impostor servers — both of which should be ignored until cross-checked against the in-game credits.
| Identity | Roblox Handle | User/Group ID | Role | Verified Via |
|---|---|---|---|---|
| Solo developer | BanuTheCat | userId 8212131806 | Build, ship, patch notes | Official game page (200 OK) |
| Studio group | X Core Studios | groupId 1065061064 | Group wall, social link hub | Roblox group page (200 OK) |
| Community curator | (rotates per chapter) | varies | Pinning, event hosting | Group wall + in-game credits |
| Trusted playtesters | 3–5 accounts | varies | Pre-release builds | Whitelist on the dev's friend list |
The anomaly detected developer does not run a public Trello, a Steam developer portal, or a GitHub repository at the time of writing. Every official update is mirrored on the Roblox group wall first, then on the anomaly detected discord that the group link points to — a fact that matters when a fan server claims to have "leaked" a chapter that does not yet exist.
Why the Game Credits a Solo Creator
Anomaly Detected launched on 2026-06-25 under the Survival / Escape category on Roblox, with the most recent patch recorded on 2026-09-14. Five chapters are live — The Residence, The Neighbourhood, The School, The Hospital, and The Mall — and the credits in each chapter's loading screen only list BanuTheCat. Because the anomaly detected developer is a single person, the cadence of updates is closer to a serial-comic schedule than a AAA roadmap: one chapter, one Veteran difficulty tier, one bug-fix pass, and then silence until the next anomaly table is complete.
This single-creator model is also why suggestions and feedback reach the source faster than in a typical Roblox title. Posts in the official group wall are answered by the same account that pushed the build, and replies in the anomaly detected discord channels use the BanuTheCat display name rather than a community manager pseudonym.
Finding the Official Anomaly Detected Discord
The biggest trap new players fall into is joining a "BanuTheCat" Discord from a YouTube comment or a TikTok bio. Only the invite pinned on the verified Roblox group wall is real, and that invite is the only one the anomaly detected developer vouches for. biggest trap new players fall into is joining a "BanuTheCat" Discord from a YouTube comment or a TikTok bio. Only the invite pinned on the verified Roblox group wall is real, and that invite is the only one the anomaly detected developer vouches for, a trust principle carried straight into the broader rollout that the team walks through in Anomaly Detected Chapter 5 Release.
How to Verify a Discord Invite in 30 Seconds
Roblox's group social module does not expose a public Discord link without authentication, which is why automated scrapers often return a blank field. Community-tracked channels have, over time, collected the following list of verification rules. Run any invite through them before you click Accept Invite:
| Check | What to Look For | Pass Condition | Fail Signal |
|---|---|---|---|
| Invite source | Pinned message on the X Core Studios group wall | Wall post authored by BanuTheCat | "DM me for the link" or TikTok bio |
| Server name spelling | "Anomaly Detected" with capital A and D, no extra words | Exact match | "ANOMALY DETECTED OFFICIAL SERVER!!!" with emoji |
| Member count vs. age | Server age in months roughly matches member count | Within 20% of expected | 50k members in a 2-week-old server |
| Verification channel | #verified-by-banu or pinned message with Roblox profile screenshot | Screenshot from the userId 8212131806 profile | Generic "we are the official server" claim |
| Patch-note channel | #patch-notes mirrors the group wall | Same timestamps and wording | Only re-posts from fan wikis |
The anomaly detected discord run by the developer is, by design, lean. There is no NFT integration, no paid role for verification, and no "nitro boost" perk wall — three red flags that appear in nearly every impostor server tracked by community reports. The legitimate server reflects the same restraint that the anomaly detected developer applies to the game itself.
What the Anomaly Detected Discord Actually Contains
Once you have passed the verification step, the layout of the official server mirrors the game's structure rather than the typical Roblox "giveaway-and-emoji" template. According to community reports and pinned messages scraped from the group wall, the channels are clustered around three jobs: read patch notes, file suggestions, and report bugs.
| Channel Type | Channel Examples | Purpose | Posting Rules |
|---|---|---|---|
| Patch notes | #patch-notes, #chapter-releases | Mirror the group wall | Read-only for members |
| Feedback | #feedback, #anomaly-suggestions | Player suggestions, anomaly ideas | BanuTheCat replies within 24–72h |
| Bug reports | #bug-reports, #audio-cues | Reproducible crash or soft-lock | Template required |
| Lore | #the-residence, #the-mall | Per-chapter discussion | Free-form, moderated |
| Off-topic | #lobby | General chat | Standard Roblox ToS |
The reason this layout matters is that every anomaly detected suggestion posted in the right channel reaches the anomaly detected developer directly, while a suggestion posted in #lobby will be lost in general chatter. The same routing applies to anomaly detected feedback about camera angles, audio cues, and the Veteran difficulty curve.
The Anomaly Detected Community: Size, Channels, and Culture
The community is small enough that a single developer can read every post, but large enough that the in-game Shift queues fill within minutes of a new chapter dropping. Understanding where the players actually congregate — and where they don't — saves hours of scrolling.
Where the Player Base Actually Lives
At the time of writing, the Anomaly Detected game page shows roughly 1,932 concurrent players, 673,506 total visits, and 30,306 favorites. That ratio — about 22 visits per favorite — is unusually high for a Roblox horror title and indicates strong replay value rather than a one-shot launch spike. The community is therefore concentrated in three hubs:
| Platform | Verified Existence | Primary Content | Posting Cadence |
|---|---|---|---|
| Roblox group wall | Yes (X Core Studios) | Patch notes, polls, new-chapter teasers | Per release |
| Official Discord | Yes (pinned invite) | Feedback, bug reports, lore discussion | Daily |
| YouTube | Community videos only (no official channel) | Grind sessions, anomaly hunts, "first 30 minutes" | Per upload |
| No dedicated subreddit | Scattered threads in r/roblox | Sporadic | |
| Twitter/X | No official account | None | n/a |
| Standalone website | None | None | n/a |
Notice the gap: the anomaly detected developer does not maintain a Twitter/X, a Subreddit, or an official YouTube channel. Anyone claiming a "first look" video on those platforms is either community content or an impostor. YouTube strategy videos such as the Cr1ms0nX community run are useful for spotting common shift mistakes, but they are not authoritative for patch timing.
Community Norms and the Feedback Loop
The anomaly detected community has a strong "show, don't tell" feedback culture. Suggestions in the official Discord almost always include a screenshot or a short clip of the anomaly in question, and the developer typically replies with one of three outcomes: accepted, noted, or out of scope. Community reports note that accepted suggestions tend to land in the next chapter, while "noted" ones are revisited when a chapter gets a Veteran Mode pass.
Because the loop is short — a player files an anomaly detected suggestion on Tuesday, sees it in the changelog on Friday — the culture rewards specificity. Generic feedback ("make it harder") is rarely answered, while concrete feedback ("The Mall camera 4 clips through the ceiling when the escalator anomaly fires") is almost always replied to by the anomaly detected developer within a single shift cycle.
How to Send Anomaly Detected Feedback and Suggestions That Get Read
Most player feedback never reaches the developer because it is filed in the wrong channel, in the wrong format, or at the wrong time. The anomaly detected developer has a documented preference for short, reproducible reports, and the same template works in both the group wall and the official Discord.
The Reproducible Feedback Template
Before posting, run your feedback through this four-line template. The anomaly detected developer — and the trusted playtesters on X Core Studios — will skip anything that does not include the first three fields.
| Field | What to Write | Example |
|---|---|---|
| Chapter | The Residence / Neighbourhood / School / Hospital / Mall | The Mall (Chapter 5) |
| Anomaly name or camera | The exact anomaly label or camera number | Camera 4, escalator bay |
| Repro steps | Click, wait, report — in order | Wait 6s after shift start, the bench on the right swaps with a cardboard cutout |
| Screenshot or clip | Drag-and-drop into Discord, paste into the wall post | 10-second clip showing the swap |
The reason the template works is that the anomaly detected developer ships from a single machine, and every accepted suggestion is tested against a saved state. A repro that the developer can paste into the Shift loader and trigger in under 30 seconds is more likely to be accepted than a paragraph-long description of "something feels off."
Timing Your Post for Maximum Visibility
The official Discord's traffic spikes within an hour of a new chapter drop, and the anomaly detected developer is online reading the wall during that window. Posting anomaly detected feedback during the first 24 hours of a chapter's release is the single highest-leverage move you can make, because the developer is mentally inside that chapter's anomaly table. Posts that arrive two weeks later compete with the next chapter's workload and are typically filed as "noted" rather than "accepted."
| Post Window | Developer Attention | Average Response Time | Best For |
|---|---|---|---|
| 0–24h after chapter drop | Peak | < 12 hours | New-chapter anomalies, balance issues |
| 1–7 days after drop | High | 12–48 hours | Veteran Mode tuning, audio cues |
| 7–30 days after drop | Moderate | 2–5 days | Lore, long-term suggestions |
| 30+ days after drop | Maintenance mode | 1 week+ | Pre-next-chapter wishlist |
If your post is a pure anomaly detected suggestion rather than a bug report — for example, a new anomaly type for The School — the right channel is #anomaly-suggestions, and the right time is during a maintenance window the developer has flagged on the group wall. During maintenance, the dev is reading the wall in long form rather than skimming for crash reports.
Staying Updated on Anomaly Detected Patch News
The game updates roughly every 10–14 days, with a mix of new-anomaly patches, Veteran Mode balancing, and the occasional chapter extension. Tracking those updates without joining the Discord is possible, but you trade speed for the official social feed on the Roblox group wall.
The Two-Channel Tracking Method
Players who do not want to keep the Discord open can subscribe to the X Core Studios group wall through Roblox notifications. Every post by BanuTheCat will surface in the bell icon, and each post is mirrored to the official Discord within minutes. The two channels therefore function as a redundant feed: if one is down, the other carries the same content.
| Source | Latency | Authenticity | Best For |
|---|---|---|---|
| X Core Studios group wall | 0–5 minutes | 100% (developer account) | First-look patch notes |
Official Discord #patch-notes | 5–15 minutes | 100% (mirrored) | Searchable history |
| Community YouTube | Hours to days | 80% (fan content) | Visual walkthroughs |
| Reddit r/roblox | Days | 60% (often outdated) | Casual discussion |
| Fan wikis | Days to weeks | Variable | Back-catalog of removed anomalies |
For players who want a single bookmark, the X Core Studios group wall is the closest thing to a public RSS feed the anomaly detected developer maintains. Each wall post is timestamped, signed by the BanuTheCat handle, and stays live even after the Discord rotates channels.
Reading a Patch Note Like a Developer
The patch notes are unusually short — usually a bullet list under 200 words — and they follow a consistent format. Learning that format lets you extract the developer priorities at a glance:
-
Added — a new anomaly, a new camera, a new chapter room. The headline change.
-
Tuned — Veteran Mode timing, audio cue volume, or the Zoom (Shift / L2 / Double Tap) sensitivity. Often responds to community feedback.
-
Fixed — a specific crash or soft-lock, usually quoted verbatim from the bug-report channel.
-
Removed — rare, but signals a rollback of a community-rejected change.
A patch note that contains three Tuned lines and one Fixed line is almost always a response to a recent wave of anomaly detected feedback. A patch note that contains a single Added line of more than 50 words is almost always the start of a new chapter. Tracking the rhythm takes a few patch cycles, but it gives you the same lead time the trusted playtesters have, without needing early access.
Frequently Asked Questions
Who is the anomaly detected developer?
The anomaly detected developer is BanuTheCat, an independent Roblox creator (userId 8212131806) who ships the game solo under the studio group X Core Studios (groupId 1065061064). The handle appears on the official game page credits and in every chapter's loading screen, with no co-developer listed.
Is there an official anomaly detected discord?
Yes. The official anomaly detected discord is the server linked from the pinned message on the X Core Studios Roblox group wall, which is the only place the developer vouches for an invite. Any Discord advertised in YouTube comments, TikTok bios, or third-party wikis should be treated as unofficial until cross-checked.
Where do I file an anomaly detected suggestion?
File it in the #anomaly-suggestions channel of the official Discord, using the four-line template: chapter, anomaly or camera, repro steps, and a screenshot or clip. Posts filed within the first 24 hours of a chapter drop are typically answered by the anomaly detected developer within a single shift cycle.
How do I send anomaly detected feedback that gets read?
Post concise, reproducible feedback in the right channel: #feedback for general comments, #bug-reports for crashes, and #anomaly-suggestions for new ideas. The anomaly detected developer skips vague reports, so always include the chapter name, camera number, and a 10-second clip of the issue.
How often does the anomaly detected developer push patches?
The anomaly detected developer pushes a patch roughly every 10–14 days, alternating between new-anomaly drops, Veteran Mode tuning, and bug-fix passes. The X Core Studios group wall is the fastest place to see a new patch, with the official Discord mirroring the same notes within minutes.