Loop [ALPHA] is currently marked Alpha by its developer. The official description warns about bugs, balance issues, unfinished content, and systems that can change. This status page records only changes that can be tied to the official Roblox experience, creator-owned public information, or repeatable live observations. It does not guess at patch contents from a timestamp.
The canonical Games API reported updated: 2026-09-16T10:04:31.9286524Z when checked on September 16, 2026. That value confirms that Roblox recorded an update to the experience entry. It does not identify which rooms, missions, entities, items, values, or interface elements changed.
Current official status
The official experience describes a liminal roguelike where every Day can differ. It names missions, collections, escape, entities, and survival as core goals. The public API identifies the creator as Gazing at the Moon, the root Place ID as 97694772546348, the Universe ID as 10749778558, the genre as Survival / Escape, and the maximum server size as 30.
Those fields define identity and broad scope. They do not prove that a particular mission, entity behavior, Item price, Coin reward, room order, or EXIT condition exists in every server. Player-facing guide pages therefore keep exact mechanics dated and qualified.
Verified status timeline
2026-09-16 - Official Alpha status and API record checked
Type: Official status review
The canonical Roblox Games API continued to return the name Loop [ALPHA], root Place ID 97694772546348, Universe ID 10749778558, creator Gazing at the Moon, and an updated value of 2026-09-16T10:04:31.9286524Z. The official description still warned that the game is in Alpha and that everything is subject to change.
- The API timestamp proves the experience record was updated.
- No creator-authored public changelog was found that explained the exact changes associated with that timestamp.
- Existing mechanics should be rechecked in the live build, but no specific buff, nerf, addition, or removal is claimed here.
Source: Official Roblox Games API
How to use the updated timestamp
Treat the timestamp as a trigger for review. When it moves, reopen the official description, compare the badge list, and test the parts of the game you rely on. Start with visible and repeatable fields: mission wording, Day transition, Inventory, shop or purchase panels, Coin balance, EXIT state, and the cue-and-response sequence for known entities.
Do not publish “new update” claims that merely repeat the timestamp. Roblox can update metadata or backend records without providing a public feature list. Conversely, a meaningful server-side change may not be understandable from one API field alone.
What counts as a confirmed update
A creator-owned announcement that clearly names Loop [ALPHA] and describes a change is first-party evidence. A change visible in the live game can be marked In-game verified when the observer records the date, Day, solo/co-op state, and repeatable before/after result. Agreement across two independent current walkthroughs can support Community corroborated wording when first-party notes are absent.
A search snippet, copied list, isolated comment, or unexplained video title is not enough for a definitive mechanic change. It may point to something worth testing, but it should not overwrite the current guide until the result is clear.
What to recheck after an Alpha change
Begin with the Beginner Guide route: current objective, menu labels, Day display, mission feedback, and escape result. Then inspect the Entities Dex for cue or behavior changes, Items for prices and persistence, and Progression for milestones or badge text.
For a group, compare multiple players’ mission state, Inventory, Coins, and escape credit. For solo, test one low-risk interaction at a time. Record exact wording and avoid changing several variables in the same attempt.
Report a suspected change clearly
Include the UTC date, official experience URL, server state if visible, Day, solo/co-op condition, exact action, observed result, and whether it repeated. If the report concerns an entity, add the cue, location description, and what ended the encounter. If it concerns an Item, add the displayed name, price, effect text, and what persisted after transition.
Separate observation from interpretation. “My Coin balance changed from X to Y after this interaction” is an observation. “The developers secretly nerfed every Coin source” is an interpretation that needs wider evidence.
Update mistakes to avoid
- Calling the API
updatedvalue a patch date with known contents. - Copying a changelog from a different game named Loop.
- Using a badge award count as a spawn rate or difficulty percentage.
- Treating one changed Day as a permanent map redesign.
- Replacing official names with a community nickname without showing the game term.
- Publishing a price, damage value, or timer without a current version and repeatable check.
- Hiding the fact that a result came from solo or co-op play.
Update FAQ
What changed on September 16, 2026?
The official API proves that the experience record had an updated timestamp on that date. No public first-party changelog checked here explains the specific change, so this page does not invent one.
How often should guides be rechecked?
Recheck when the official description, API timestamp, badge list, or creator announcement changes, and whenever the live interface disagrees with a dated guide. Alpha systems deserve more frequent verification than stable identity fields.
Are community videos useful after an update?
Yes, for seeing interfaces, room sequences, and behavior worth testing. Compare the upload date and current live build, and do not treat a single video as a complete or official changelog.
Where should I start after a major change?
Verify the first Day, one mission, one Inventory interaction, one Coin change, and one EXIT or failure transition. Those checks reveal whether the core loop changed before you risk a long run.
Evidence status: Name, IDs, creator, genre, server capacity, official description, Alpha warning, and the dated API updated field are Official. Specific September 16 patch contents remain unverified because no first-party changelog was found.