Buy the permanent improvement that fixes the last repeatable failure, then rerun before spreading resources across unrelated systems.
Official patch reference
Use the Bunker to correct repeated run failures
Hands-on coverage describes the Bunker as the between-run hub for permanent upgrades, equipment, shops, missions, and rescued characters. It can feel dense because several progression systems arrive in the same place. The easiest way to prioritize it is to carry one clear diagnosis back from the previous run.
If hits remove the clock, improve survival or starting stability. If the route is safe but stalls, improve the part of the build that creates pressure. Patch v1.0.13.0 fixes the saved Time Machine loadout becoming unadjustable after a reset through Gabriella, so update before repeating an older workaround.
Fix a measured blocker
Spend against the reason the last run ended, not the most visually prominent upgrade.
Unlock useful functions
A rescued character or new station can widen future choices more than a small stat gain.
Keep one main route
Repeat a familiar route long enough to judge whether the purchase changed the outcome.
Retest saved loadouts
The Gabriella reset issue received a fix in v1.0.13.0; update before following old avoidance advice.
Do this first
- 1Record the failure
Clock loss, target pressure, route safety, or equipment clarity.
- 2Choose one category
Prefer the permanent option that directly addresses that failure.
- 3Update before resetting
The Gabriella saved-loadout issue was fixed in v1.0.13.0, so retire older avoidance advice after updating.
- 4Rerun the route
Do not buy a second category until the first change has a visible effect.
Priority framework
| Observed blocker | Priority direction | Avoid |
|---|---|---|
| Hits remove too much time | Survival / starting-time support | Pure damage reflex |
| Safe route stalls | Pressure or equipment improvement | More defense without need |
| Opening repeats slowly | Early-run consistency | Late-route specialization |
| Choices are confusing | Unlock clarity and Handbook use | Spending across every system |
Use this flow
- 01Return to Bunker
- 02Name the blocker
- 03Buy one relevant improvement
- 04Repeat route
- 05Compare clock / reach / safety
Related video
Ascend to ZERO - Gameplay Walkthrough part 1 (PC, Xbox)
TanJinGames
A recent English-labeled first-part walkthrough surfaced in the live video search.
Why it is useful: Players who prefer a conventional walkthrough format across PC and Xbox.
Watch on YouTubeCommon mistakes
Do
Change one decision, measure the result, and keep the source trail visible.
Avoid
- Publishing upgrade names without current-build proof
- Spending across every available category
- Changing route and upgrades together
- Assuming permanent power fixes route decisions
FAQ
Which Bunker upgrade should I buy first?
Start with the option in your current menu that directly addresses the last repeatable failure, then rerun before spreading resources across unrelated systems.
Does Bunker progression persist?
Independent hands-on coverage describes Bunker upgrades as permanent improvements for later runs.
Sources
Independent hands-on account of timer management, Time-Stop, builds, Bunker progression, and difficulty.
Independent review used to cross-check controls, gadget input, equipment categories, and the Chrono Child starter example.
Ascend to ZERO: A Time-Bending Roguelike Sharpened to the Last Second
Xbox Wire / Flyway Games / accessed 2026-07-16
Detailed first-party explanation of the opening timer, Time-Stop, auto-attacks, growth, difficulty, Handbook, and late-game routing.
Official patch covering final-boss progression, Stage 3 rewards, Blossom Blade bleed crashes, item acquisition, and current known issues.
Official patch covering progression, inventory, Handbook, Tech Chips, stats, Linux stability, Score Shop rewards, and temporary leaderboard removal.
Ascend to ZERO Patch Notes - v1.0.13.0 (+v1.0.14.0)
Flyway Games / Steam / accessed 2026-08-02
Official combined v1.0.13.0 and v1.0.14.0 post adding inventory name sorting, fixing stability and progression issues, relaxing two Handbook achievement requirements, and rebalancing boss behavior in Stages 2, 3, and 4. The post does not provide a separate player-facing v1.0.14.0 change list.