This page records changes that can be tied to a dated first-party Roblox record. It does not convert an experience “updated” timestamp into a fictional changelog. Roblox metadata can change when developers publish content, alter configuration, refresh presentation, or make another platform-side update; the timestamp alone does not tell players which weapon, map, enemy, reward, or rule changed.
October 30, 2026 experience snapshot
The official Games API identifies the experience as Guts & Blackpowder and describes a Napoleonic setting where survivors use muskets and swords against undead hordes. It lists the verified creator as the Guts & Blackpowder group, identifies the root place, and provides the public update timestamp above. These facts verify identity and recency. They do not identify a balance patch or prove a particular gameplay change.
Use the official Roblox experience as the launch destination. If the public description, creator identity, root place, or access state changes, those changes can be recorded directly. Gameplay claims need a developer announcement, a comparable first-party record, or a current reproducible in-game observation.
October 26, 2026 badge metadata changes
The official badge API shows two event-related records updated on October 26, 2026. The Hollow was updated at 2026-10-26T21:03:58.851Z and its public description says to beat the Halloween map Transylvania for the Roblox “The Hollow” event (2026). Saviour Complex was updated at 2026-10-26T21:07:08.3Z and its public description says to beat Transylvania and the full Sleepy Hollow campaign back to back.
Those records prove the descriptions and update times. They do not publish an event closing date, a ticket reward, a hidden drop table, or a guarantee that the maps remain selectable at every hour. Check the live event and map interfaces before beginning a run. Use The Hollow badge guide and the Transylvania guide for the supported condition and route.
October 7, 2026 Halloween badge status
The official badge API shows Voivode updated on October 7, 2026. Its public description requires beating Transylvania without dying and says the badge unlocks the in-game items Voivode and Iron Stake. For Whom The Bell Tolls was also updated that day and requires beating Sleepy Hollow without dying, with the Jack-o’-lantern Utility named as the reward.
These are badge-record changes, not a complete Halloween patch note. They can support event planning, but they do not establish every map adjustment or enemy balance change. When a community changelog claims more, verify it against a developer-owned post or the live game before treating it as official.
June 26, 2026 Moss and Holdout badge records
The official API lists June 26 updates for Forged In Fire, Counter-Battery Fire, Dead of Night, and Every Man’s Duty. Forged In Fire requires escaping Moss Ironworks in Objective mode in one life. Counter-Battery Fire requires being hit by the recoiling cannon cart in Moss Ironworks. Dead of Night requires surviving all six waves at Trafalgar House in Holdout. Every Man’s Duty requires protecting all four Holdout zones and names two cosmetic unlocks.
Together, these records verify Moss Ironworks and the Trafalgar House Holdout goals. They do not provide the complete route, exact enemy timings, reward values, or every system introduced with the surrounding game update. Those details remain community documented or require current in-game testing.
June 23, 2026 Holdout entities
The badge API creation dates show Dead of Night and Every Man’s Duty entering the official badge set on June 23, 2026. This is evidence for the public achievement entities and their stated conditions. It is not safe to infer that every related map feature launched at the exact badge creation second, because a badge can be configured before or after a public gameplay change.
For current play, use the Holdout mode guide and watch the live wave or zone display. The official badge condition is the goal; the current client is the authority on how that goal is presented during the match.
How to read Roblox update evidence
There are four useful levels. A developer-owned announcement can name a patch and describe changes. An official API record can prove identity, a public description, enabled state, and timestamps. A reproducible in-game check can verify the current UI or mechanic. A community page or video can document a route and help players compare observations. These sources are not interchangeable.
When only metadata changes, this page says “metadata updated.” When an official badge description changes, it records the exact supported requirement in original words or a faithful summary. When a gameplay value comes only from a community source, it is labeled community reported and kept out of the official status timeline.
What is not confirmed by the latest timestamp
The October 30 Games API timestamp does not by itself confirm a new weapon, class, map, code, badge, reward, enemy, balance adjustment, or private-server command. It does not prove that a seasonal event began or ended. It also does not make an unofficial video title into a changelog.
No verified code or redemption instruction appears in the official experience description at the check time. Use the Codes hub for that status. A future code will require an exact developer source and a working in-game redemption path before it is listed.
Player update checklist
- Confirm the exact experience and verified creator group before following a link.
- Read the current Roblox description for access, rules, and creator-linked destinations.
- Check official badge descriptions before attempting a multi-part unlock.
- Use the live map vote, Shop, Settings, and class interface for current availability and controls.
- Treat community values as update-sensitive until they match the client you are playing.
- Ignore “leak,” “secret code,” or “new meta” claims that cannot show a developer source or reproducible result.
Current facts that still need live testing
The complete gameplay patch associated with the October 30 timestamp is not public in the API response. Event availability, exact Shop prices, weapon balance, control layout, route timers, enemy values, and reward delivery should be checked in the current client. The site will not fill those gaps with a guessed changelog.