Build change logDated observations of the experience's own Updated field (games.roblox.com/v1/games?universeIds=10642022844), each paired with a catalog check of the badges and game passes.
| Read on | Updated field | Catalog check |
|---|
| 2026-09-20 | 2026-09-20T00:37:48Z | 12 badge records, the newest being Endless Mode (created 2026-09-18). This is the read the statistics table below is built from. |
| 2026-09-25 | 2026-09-25T17:54:33Z | Unchanged at that hour: the same 12 badge records with the same IDs, names and descriptions, and the same four game passes (Show Impostors 159, Big Lobby 149, Infinite Revives 139, Faster Movement 89 Robux) still on sale. |
| 2026-09-26 | 2026-09-26T15:41:03Z | New badge ID: THE WHISTLER. The catalog returns 13 records instead of 12. The addition is badge 936532269988598, created 2026-09-25T19:07:51Z with the description “Stay inside while it whistles. Run back into the house if it spots you.” It carried no awards in this read. The other twelve records and all four game passes were unchanged. See the The Whistler threat page. |
| 2026-10-14 | 2026-10-03T17:35:58Z | A later rebuild that moved nothing else. The Updated field advanced to 2026-10-03T17:35:58Z, where the 2026-09-26 read had left it at 2026-09-26T15:41:03Z. The badge catalog still returns the same 13 records with the same IDs, names and descriptions as the 2026-09-26 read, and all four game passes are still on sale at the same prices (Show Impostors 159, Big Lobby 149, Infinite Revives 139, Faster Movement 89 Robux). By this read the field had not moved again for eleven days. |
| 2026-10-20 | 2026-10-17T17:48:21Z | Fourth move, and again no catalog change. The Updated field advanced from 2026-10-03T17:35:58Z to 2026-10-17T17:48:21Z. The badge catalog still returns the same 13 records with the same IDs, names and descriptions, and all four game passes are still on sale at the same prices (Show Impostors 159, Big Lobby 149, Infinite Revives 139, Faster Movement 89 Robux). This read also recorded the experience page's official UPDATE 4 event card, described above. |
| 2026-10-27 | 2026-10-24T15:24:30Z | Fifth move, and the first one delivered inside an announced window. The Updated field advanced from 2026-10-17T17:48:21Z to 2026-10-24T15:24:30Z. The badge catalog still returns the same 13 records with the same IDs, names and descriptions; the newest is still THE WHISTLER, created 2026-09-25T19:07:51Z. Each of the four game-pass listings still carries its own updated timestamp of 2026-09-03, so none has been edited since the price read published on the game-pass pages. That price field itself no longer returns through the game-passes API for an unauthenticated read, so this row does not re-quote prices. The experience page rendered the field as 10/24/2026 and the event card as UPDATE 4 with “More infos soon”; the Dread Forge group page still showed “No announcements yet...”. |
What this means: the Updated field moved on 2026-09-25, again on 2026-09-26, again on 2026-10-03, again on 2026-10-17 and again on 2026-10-24, so the build running today is not the build the statistics below were read from. A rebuild on its own is not evidence of a content, balance or drop-rate patch: Roblox does not publish what changed and Dread Forge has published no changelog. The catalog is what a player can actually check, and the 2026-09-26 read is the only one that broke the pattern — a new badge ID appeared. Two things about that are worth keeping straight. First, the badge record was created at 2026-09-25T19:07:51Z, which is 73 minutes after the 17:54:33Z rebuild read that still showed twelve records, so the rebuild and the new threat are separate events rather than one patch note. Second, a new badge record is a configured achievement, not a published rule: the description is the only first-party text about The Whistler, and no night, spawn rate or drop rate accompanies it. The 2026-10-03, 2026-10-17 and 2026-10-24 rebuilds are the other half of the lesson: the third, fourth and fifth moved timestamps each added nothing to the catalog, so a new date is not a new feature. The fifth differs in one respect: it landed inside an announced window. The field moved at 2026-10-24T15:24:30Z and the UPDATE 4 window opened at 2026-10-24T18:00Z, so the build arrived before the event did, and five days into the window the official text still described nothing. A dated event tells you when to look; it never said what to expect. Later reads that show a pulled pass, a changed description or a new badge record will be recorded here on their own dates.
Checking UPDATE 4 yourself, in about two minutes
- Open the experience page and read the Updated field. It should read 2026-10-24 in the Americas and Europe (the API field is 2026-10-24T15:24:30Z; far east of UTC+8 the local date can already be 2026-10-25). A later date means a newer build exists and this page is behind it.
- Open the Events tab and read the UPDATE 4 card. If its description has been replaced by a content list, that list is the official answer and this page’s “no content list” line no longer applies.
- Request
badges.roblox.com/v1/universes/10642022844/badges?limit=25 and count the records. Thirteen means no new achievement exists; more than thirteen means a new one was configured, and its own created date says when. - Compare the game-pass listings. Four passes at four published prices is the standing state; a fifth pass, a changed price or a changed listing text is the fastest visible content change to confirm.
