Updates

Introduction

Updates tracks how fast Anomaly Detected has grown and what is confirmed to be coming next. The release cadence has been unusually brisk for a solo-developed Roblox game: it launched at the end of June 2026 and added four more contracts over the following eleven weeks, roughly one new location every two to three weeks. The timeline is reconstructable with some confidence because every contract ships with its own badges, and badge creation dates give a reliable record of when each chapter went live. Layered on top of the chapter releases are the systems updates, most notably the Veteran tier rollout that retrofitted a top difficulty onto the chapters that predated it. That pattern matters for anyone using this wiki, because it means older pages drift. An anomaly pool that was complete in August can gain entries in September, and a clear rate published at launch will move as balance patches land. The section keeps the release history, the systems changes and the developer roadmap statements in one place so you can tell how current a given piece of information is.

Release Timeline

Update Milestones

Core Mechanics

The update history explains a problem that every Anomaly Detected player runs into: information ages faster than it is written. Because contracts arrive roughly every two to three weeks and each carries its own anomaly pool, journal and badges, any reference material has a short shelf life by design. The timeline also reveals how the game was built rather than merely when. Veteran mode was retrofitted onto existing chapters in late July, which tells you that difficulty was not part of the original design and that the developer treats it as a tuning layer over a single rule set. That is the same reason a chapter you already know stays familiar when you raise the tier. The chapter releases themselves follow a deliberate escalation: a small bedroom, then an outdoor map, then long corridors, then reflective wards and finally a full mall. Each one introduces exactly one new perceptual challenge, which is why the clear rates fall in a smooth curve rather than in steps. Finally, the newest contract tells you where the uncertainty is. Anything written about The Mall shortly after release is provisional, and patches are most likely to land on the most recent content.

Advantages

The practical advantage of tracking updates is calibration. Knowing that the pool, the clear rates and the badge counts all move with each release stops you treating an out-of-date figure as a contradiction and lets you judge how much to trust a given page. The timeline also gives a reliable release cadence, which is genuinely useful for planning: a player who knows a new contract lands every few weeks can decide to finish a journal on a settled map rather than starting one on content that is about to change under them. Systems history has value too. Knowing that Veteran was retrofitted explains why the tier feels bolted on to the earlier chapters in a way it does not on the newest map, where it shipped alongside the content. Finally, the roadmap statements — additional contracts, anomaly packs and surveillance sites — tell you what kind of content is coming. A new surveillance site implies a new map with a new camera layout, which is precisely the kind of change this wiki has to update in several sections at once.

Challenges

The obvious limitation is that almost nothing here is officially versioned. The developer does not publish patch notes in a structured log, so the timeline is reconstructed from badge creation dates, release metadata and player observation. That method is reliable for chapter releases and less reliable for balance changes, which generally leave no badge trail at all. Roadmap statements are similarly informal: the confirmation that more contracts and anomaly packs are in development is a clear statement of intent but comes with no dates, so it cannot be used to predict when the next update lands. There is also an accuracy cost to writing quickly. This section aims to describe the shape of the update history rather than to be a complete patch log, and players looking for the exact state of a balance change should verify it against the live game rather than relying on a snapshot taken at publication time.

Frequently Asked Questions

Quick Tips