Debt Hunt’s public Roblox state is moving quickly enough that a title alone is not a patch note. On September 2, 2026, the Games API returned the name [REVERT] Debt Hunt 🐺 and an update timestamp of 2026-09-02T08:12:58.9347816Z. Search and chart surfaces viewed around the same time still showed an [UPDATE 1] prefix. That conflict confirms a public-state change, but it does not reveal which mechanic was reverted.
This single timeline records only changes that can be tied to a first-party Roblox surface or a clearly labeled community report. It does not create separate event or patch pages from cached titles, and it does not turn third-party descriptions of a lobby into official release notes.
Latest verified public snapshot
2026-09-02 - REVERT name and Alpha state confirmed
Type: Official public-state check
Roblox’s Games API returned [REVERT] Debt Hunt 🐺, Universe ID 9063977758, root Place ID 119116892854064, creator T0pH4t_Studios, and the Survival/Escape classification. The description still says the experience uses procedural generation, asks players to earn money to pay the Debt Hunt collection agency, introduces a monster hunt at sunset, credits the original NZTeam concept, and warns that the game remains in Alpha.
- API updated time: 2026-09-02T08:12:58.9347816Z.
- Public places returned: TestPlace, the root Debt Hunt place, Game, and Tutorial.
- Enabled badges returned: 21.
- Search and chart caches still showing an UPDATE 1 prefix were treated as stale or conflicting display evidence, not as a current patch specification.
Source: Official Roblox Games API
What the REVERT label does and does not tell you
The label tells you that the creator changed the public experience name and chose to signal a revert. The API timestamp tells you when Roblox last recorded a universe update. Neither field names the files, lobby screens, balance values, item tables, difficulty modifiers, or objectives affected.
If your current lobby differs from a video recorded under UPDATE 1, trust the live prompts for controls and objectives. Keep the older video useful for broad route decisions only when those decisions still reproduce. Do not claim that a tutorial, item, or feature was removed simply because the title changed.
The publicly listed Tutorial place proves that a place with that name exists in the universe. It does not prove every player is routed through it, which steps it contains, or whether its content survived the revert unchanged.
How to read a Debt Hunt update safely
Start with the official experience description and Games API. Compare the name, description, creator, root Place ID, and updated timestamp. Then check the place inventory and badge list for additions, removals, enabled-state changes, or description changes. A new badge can establish a new challenge topic, but it cannot by itself prove an entire mechanic or reward table.
Next, compare the live interface. Record the server join time, visible title, lobby layout, tutorial prompts, debt display, difficulty options, and any new objective wording. One server may lag behind a universe update, so a single mismatch should be rechecked in a fresh public server before it becomes a definitive entry.
Finally, use community videos or guides to understand player impact. Label what they observed and the date. If two current sources disagree, keep both claims separate until first-party text or a reproducible live test resolves them.
Stable facts versus update-sensitive facts
Stable identity currently includes the universe, root place, creator group, and official Roblox URL. The broad loop—procedural generation, earning money to pay debt, and danger at sunset—is also written in the first-party description.
Update-sensitive facts include the public title prefix, lobby flow, tutorial routing, codes interface, debt amounts, day limits, control prompts, item names and prices, DarkMarket inventory, monster behavior, difficulty differences, badge statistics, and active events. Those details need a check date and should not be carried forward merely because an old page still ranks in search.
Live popularity fields such as current players, visits, favorites, past-day badge awards, and total awards are snapshots. They can be useful for confirming that the universe is active, but they are not permanent site statistics and are intentionally not frozen in this guide.
Current badge and place signals
The official badge endpoint returned 21 enabled entries on September 2. The set supports four difficulty clears, several special win conditions, camera and resource activities, and long-term progression. Open the Badges Index for exact names and descriptions. Strategies are kept separate from the official text.
The places endpoint returned four public records. Their names indicate development, root, game, and tutorial roles, but only the root place’s description supplies gameplay text. A place name should never be expanded into an imagined walkthrough.
If a future check adds or removes a place or badge, record the exact API change first. Explain player impact only after the live experience or a creator announcement makes that impact visible.
Codes and announcement status
Current code sources conflict. Some third-party publishers repeat a claimed code and reward; others report that no active code can be verified. No accessible creator-owned announcement resolved that disagreement during this check. The Codes hub therefore publishes no disputed string as working.
The same standard applies to patch notes. A third-party “Update 1” page can help a player recognize a lobby screen, but its detailed claims remain community-reported unless the developer or current game confirms them. Cached Roblox chart text is a timestamped clue, not a changelog.
What to do after a visible change
Read the current objective before using an older route. Recheck control prompts, the debt display, difficulty label, shop access, and sunset warning. Run a short Easy attempt to confirm that the basic loop still behaves as expected. Avoid spending a long challenge run on a mechanic that may have moved.
If an item value or shop option changes, update your break-even decision rather than looking for a permanent tier. If a monster response changes, return to avoidance while you reproduce the new cue. If a badge description changes, follow the official wording and treat hidden conditions as unknown until awarded.
Updates FAQ
What is the current official name?
The Games API returned [REVERT] Debt Hunt 🐺 on September 2, 2026. A cached chart prefix may differ until Roblox refreshes every surface.
What did REVERT remove?
The public name and timestamp do not say. Any list of reverted mechanics needs a creator announcement or current in-game comparison.
Is Update 1 still live?
The conflicting public labels do not answer that precisely. Treat the current server’s lobby and objectives as authoritative, and use older Update 1 guides only for steps you can still reproduce.
Where are separate patch-note pages?
All verified status entries live on this one hub. A separate child page would imply more official detail than the current public record supports.
Sources checked
- Official Roblox Games API, checked September 2, 2026.
- Official Roblox places API, checked September 2, 2026.
- Official Roblox badge list, checked September 2, 2026.