Official event records only.

Statuses below are evaluated against each event's published UTC window at the verification timestamp. Event text does not prove unlisted stats, recipes, rates, discounts, or balance changes.

Versioned Snapshot

Dataset version2026-09-03.1
Verified at2026-09-03T03:01:42Z
Official game updated at2026-09-01T12:57:48.784Z
Historical coverageHISTORICAL_COMPLETENESS_UNKNOWN
Next lifecycle review2026-09-04T03:00:16.475Z

Current Official Event Log

Event / updateAnnounced UTCStart UTCEnd UTCSource updated UTCAffected systems / pagesEvidenceVerifiedStatusUncertainty
New Weapon: Dual Pistols
Event ID 5878802766926840463
2026-08-19T06:29:32.963Z2026-08-21T14:00:10.383Z2026-09-04T12:00:10.383Z2026-08-21T12:39:07.189ZNew weapon type and new boss. Related pages: /weapons/, /dungeons/, /updates/Roblox official public virtual-events API; verified Iron Soul group host2026-09-03T03:01:42ZLIVEThe event does not publish Dual Pistols stats or recipes, the boss identity, or a balance changelog.
Black Thursday
Event ID 4187104964516119310
2026-09-01T03:16:59.559Z2026-09-03T03:00:16.475Z2026-09-04T03:00:16.475Z2026-09-01T03:16:59.660ZDeal event. Related pages: /updates/Roblox official public virtual-events API; verified Iron Soul group host2026-09-03T03:01:42ZLIVEThe event does not publish the exact discount, eligible items, or purchase conditions.
New Map: Sakura Village
Event ID 2516485587935036060
2026-08-31T09:43:47.251Z2026-09-04T13:00:20.230Z2026-09-11T11:00:20.230Z2026-08-31T10:07:14.072ZMap 5 dungeon, boss, enemies, and forgeable weapons. Related pages: /dungeons/, /forge/, /weapons/, /updates/Roblox official public virtual-events API; verified Iron Soul group host2026-09-03T03:01:42ZANNOUNCEDThe event does not publish boss or enemy names, recipes, stats, or drop rates.
Map 5: Hell Mode
Event ID 6955332714245522093
2026-08-31T10:06:17.341Z2026-09-18T13:00:23.208Z2026-09-25T11:00:23.208Z2026-08-31T10:07:35.828ZSakura Village Hell Mode, new Hell boss, drops, and weapons. Related pages: /dungeons/, /materials/, /weapons/, /updates/Roblox official public virtual-events API; verified Iron Soul group host2026-09-03T03:01:42ZANNOUNCEDThe event does not publish the boss identity, drop table, weapon list, or stats.

Historical Coverage

HISTORICAL_COMPLETENESS_UNKNOWN. The official endpoint was queried from 1970-01-01T00:00:00.000Z and returned 4 records with no next or previous page cursor. The public endpoint returned four records and no pagination cursors even from the Unix epoch. This proves the accessible set, not that Roblox exposes a complete archive.

Stale-Event Handling

Lifecycle status is calculated from the stored official UTC start and end timestamps, using the visible verification timestamp as the deterministic reference. Recheck the official source at the next lifecycle boundary, 2026-09-04T03:00:16.475Z, then publish a new dataset version. An expired window becomes ENDED; an invalid or contradictory window becomes UNKNOWN.

Latest Known Official Game Update Signal

The Roblox official game API reported the experience updated at 2026-09-01T12:57:48.784Z when checked at 2026-09-03T03:01:42Z. This timestamp is a technical update signal, not a full patch note.

A changed API timestamp can result from many kinds of game maintenance. BloxDungeon does not infer a new weapon, code, recipe, boss, or balance change from the timestamp alone. A gameplay claim moves into a guide only when the official description, a developer-controlled announcement, or a repeatable in-game observation supports it.

Evidence Gaps After This Check

The official event records do not provide Dual Pistols stats or recipes, Black Thursday's exact offer, Sakura Village drop rates, boss stats, race effects, or attribute formulas. Those fields stay pending until a developer-controlled source or a reproducible in-game test supplies them.

Maintenance Checklist

  • Recheck the official event API before and after each published UTC window.
  • Verify whether a developer-controlled source publishes exact forge, weapon, race, or attribute changes.
  • Refresh codes status after each visible game update.
  • Move an event to ENDED only after its official end time passes or the developer changes its record.

How an Update Is Reviewed

  1. Record the Roblox API update timestamp and the date BloxDungeon checked it.
  2. Compare the official game description and developer-controlled channels with the prior review.
  3. Recheck code status and any exact values that an update could invalidate.
  4. Label incomplete evidence as pending instead of filling a table from copied claims.
  5. Update the affected guide, source note, and checked date together.

What Players Should Recheck After a Patch

Before spending materials or rerolls, check whether a claimed recipe, race effect, rune effect, or code is tied to the current version. General progression advice may remain useful, while exact item costs and effects can become wrong immediately after a balance change. The source policy explains the evidence labels used across the site, and the codes pagerecords the latest public code check.