Days are the central progression frame in Loop [ALPHA]. The developer says every Day can be different, and official badges reward reaching Day 5, Day 10, Day 25, and Day 50 for the first time. Two solo challenges also use Day 20 as a boundary: Pure Skill requires no Upgrade or Item purchases, while Pocket Full requires at least 10,000 Coins before reaching that Day.
These milestones prove reachable Day numbers, not a fixed map, mission, entity, or difficulty schedule. Build a process that survives variation.
Use the official milestones
Start every Day with the same checklist
Capture the visible Day number, exact mission text, starting Inventory, Coin balance, and one return landmark. Compare the environment with the previous Day, but do not assume repeated scenery means repeated objectives. If the mission or interface changed, let the current wording control the route.
Choose one priority: mission, Collection, EXIT, ordinary survival, or a badge condition. A clear priority prevents an optional pickup or entity experiment from derailing a milestone run.
Close every Day with a state comparison
Before the transition, inspect mission completion, Inventory, Coins, Collections, and any EXIT result. After the transition, inspect them again. Record what persisted and what changed. This is the safest way to learn the Alpha’s current save and carry rules without filling gaps from assumptions.
If the transition happens unexpectedly, write the last action and result. One surprising transition is an observation; repeat it before declaring a universal trigger.
Plan from Day 1 to Day 5
Use these Days to learn controls, mission feedback, route landmarks, and the difference between a pickup, Collection, and Inventory entry. Avoid combining badge experiments with long exploration. The Day 5 badge provides a concrete first success even if you do not escape.
When an entity ends a run, use the named page in the Entities Dex and change one response on the next attempt. Do not rebuild the entire route around a single random encounter.
Plan from Day 5 to Day 10
Review your recurring failure. If route loss is the problem, shorten branches. If mission state is unclear, read the exact action and completion signal. If resources are the issue, test one purchase or persistence rule in an ordinary run.
Day 10 is a good point to stop copying a walkthrough and rely on your own landmarks. Current videos can show the visual rhythm of Days, but the developer’s “every Day is different” statement means their sequence is not a guaranteed route.
Handle the Day 20 boundary
Choose Pure Skill, Pocket Full, or neither before the run. For Pure Skill, remain solo and purchase no Upgrades or Items. For Pocket Full, remain solo and visibly hold at least 10,000 Coins before the transition into Day 20. The public wording does not explain edge cases such as gifts, free items, or delayed badge awards.
Keep a Day-by-Day log. If the badge fails, the log is more useful than repeating the entire run without knowing which interaction mattered.
Plan for Day 25 and Day 50
Long runs magnify unclear persistence and update changes. Before committing, understand ordinary mission feedback, your current Inventory behavior, Coin risk, and when you will abandon an entity test. Review the official Updates page if the game behaves differently from an older session.
Day 50 is an official badge milestone, not proof of an ending. Continue or stop based on the current game state and your goal rather than expecting a final screen from the badge title.
Solo and co-op Day tracking
Solo gives one clear mission and resource record, and is required for the two Day 20 challenges. Co-op requires screen comparison. At every transition, ask whether all players see the same Day, mission, Inventory result, and Coin balance.
If someone joins late, record that before interpreting credit. The public evidence does not explain late-join or reconnect behavior.
Day progression mistakes
- Treating a milestone as a fixed content schedule.
- Assuming Day 50 is the final Day.
- Starting a solo-only challenge with friends.
- Checking the Pocket Full balance after reaching Day 20 instead of before.
- Buying an Upgrade or Item during Pure Skill.
- Ignoring Inventory and Coin state at transitions.
- Calling one unusual Day an update or bug without repetition.
Day FAQ
Are Days randomized?
The official description says every Day is different. It does not publish the generation pool or guarantee that every element changes.
Does progress save if I leave?
No complete public first-party rule explains session persistence. Test a low-risk state in the current build and record the exact transition.
Is Day 20 an official badge?
There is no simple Day 20 milestone in the checked list, but Pure Skill and Pocket Full use Day 20 as a solo challenge boundary.
Can friends help with Day milestones?
The general milestone descriptions do not say solo-only, but exact group and award behavior still needs live confirmation. Pure Skill and Pocket Full explicitly require solo.
Evidence status: Changing Days, milestones at 5/10/25/50, and the two Day 20 solo conditions are Official. Transition triggers, generation, difficulty, save behavior, and party credit need in-game testing.