Loop [ALPHA] Progression

Progression in Loop [ALPHA] is organized around changing Days, the missions presented in the current run, collections you can gather, opportunities to escape, and badges that mark specific outcomes. The official description confirms those systems, while official Roblox badges establish concrete milestones at Days 5, 10, 25, and 50. The public material does not yet provide a complete mission pool, collection map, save policy, or guaranteed EXIT route.

Treat progression as a sequence of verified decisions rather than a fixed walkthrough. At the start of each Day, read the current objective, identify one return landmark, and decide whether this run’s priority is survival, mission completion, a Collection, an EXIT, Coins, or a badge condition. Recheck that priority whenever the Day changes.

Day milestone index

Build a progression loop that survives randomization

At the beginning of a Day, capture the visible Day number and exact mission text. Choose a landmark near the start or a route junction, then explore in loops that return to it. When you find a Collection, EXIT, Item, or entity cue, note the direction from that landmark instead of assuming the room will occupy the same place next time.

Before the transition, compare the mission state, Inventory, Coins, and any visible Collection record. After the transition, compare them again. This reveals what actually persisted in your current build without guessing from the badge list. If something disappears, repeat once with a low-value example before calling it a universal reset rule.

Missions are the current run’s source of truth

The official experience description says to complete missions, but it does not publish a complete mission catalog. Read the live wording literally. Identify the action verb, target, quantity if shown, location clue, and completion signal. A mission that says find, interact, survive, collect, or escape can require different route and risk decisions.

Use the Missions guide when an objective appears stalled. It helps you separate a missing interaction from a progress-display delay, a wrong target, or a changed Day. Never fill a mission index with names or rewards that have not been observed in this experience.

Collections need confirmation, not just contact

“Collect collections” is official wording, but the public description does not define the total, location rules, persistence, or rewards. When you find a candidate, note its visible name or appearance, landmark, Day, and the feedback after interaction. Then inspect the current record or interface to confirm that the discovery registered.

The Collections guide provides a card-style record that works without claiming a complete map. If a location changes, preserve the clue and Day context rather than presenting the old coordinates as permanent.

Escape is a distinct progression outcome

The official EXIT badge says “Escape through the EXIT.” That proves a named EXIT and a successful outcome, but not a fixed door, guaranteed Day, or universal opening condition. When you find an EXIT, first mark the route back. Then compare its visible state with the current mission and nearby interactions before committing the whole team.

The Escape guide separates discovery, activation, approach, and confirmation. If a run ends without badge credit, record who crossed, the Day, party state, and result message instead of immediately assuming the EXIT was fake.

Badges as goals, not hidden mechanic documentation

The official universe exposes 17 enabled badges. Their descriptions are reliable for the written conditions, including milestones, friend play, named entity events, Flashlights, solo purchases, and Coins. They are not a complete explanation of the underlying systems.

Use the Badges index to choose one objective that matches your current understanding. A new player should normally learn Day transitions and mission completion before attempting Pure Skill or Pocket Full, because those challenges add restrictions and can turn ordinary recovery decisions into failures.

Solo versus co-op progression

Pure Skill and Pocket Full explicitly say Solo play only, so mode matters for at least those checks. Start those attempts alone and avoid joining or inviting players mid-run unless current in-game evidence confirms eligibility remains. For normal progression, solo players should use shorter exploration loops and set an earlier retreat threshold.

The Not Alone badge confirms a friend session is recognized. In co-op, compare each player’s mission, Collection record, Inventory, Coin balance, and escape result. Do not assume one player’s interaction awards progress to the team. Assign a route caller, objective reader, and rear watcher, but keep roles flexible when the Day changes.

Recover from unclear or missing progress

If a mission or badge does not advance, verify the exact condition before repeating the whole run. Check whether the requirement says reach a Day, complete an action, hold an amount before a Day, play solo, or play with a friend. Confirm that you are in the official experience and that the current UI showed a successful action.

For possible Alpha bugs, record the UTC date, server state, Day, party mode, exact objective text, action, and result. Rejoin only after considering whether your current run state may be lost. One failed award is a reportable observation, not proof that the condition has permanently changed.

Progression mistakes to avoid

• Treating Day numbers as a fixed map or enemy schedule.
• Following an old EXIT route without reading the current mission.
• Assuming a Collection registered because the object disappeared.
• Mixing solo-only badge attempts with a friend session.
• Spending Coins before deciding whether Pocket Full is the run goal.
• Buying an Item or Upgrade during a Pure Skill attempt.
• Turning the Games API updated timestamp into fictional patch notes.

Progression FAQ

Does progress save between sessions?

Current public first-party text does not explain the full save model. Compare low-risk state before and after a normal exit or rejoin in the current Alpha and avoid promising persistence from one observation.

Is Day 50 the end?

Day 50 is an official badge milestone. The badge does not say it is the final Day, a completion screen, or the end of all available content.

Do I have to escape to advance a Day?

That relationship is not defined in the public badge and description text. Read the live objective and transition feedback for the current Day.

What is the best order for the guides?

Learn Days and Missions first, then Collections and Escape, and use Badges once you can deliberately reproduce the relevant system. Challenge goals should come after ordinary survival.

Evidence status: Day milestone conditions, EXIT wording, 17 enabled badges, and the existence of missions and collections are Official as checked September 16, 2026. Generation rules, mission pool, Collection locations, save behavior, and party credit need in-game testing.