Vaultbreakers Progression

Vaultbreakers Progression

Separate Vaultbreakers mission progress, Demo carryover, Legacy Points, Marks, Codex rewards, quests, Challenges, and Haven upgrades.

4 guides
3 start here
Progression guide hub
ProductBase game AppID 306910 with Demo 4488770 and public-test progression labeled separately VersionOctober 2026 Demo and announced Alpha; persistence rules are date-sensitive PlatformSteam on Windows

Vaultbreakers progression has several layers that should not be combined into one promise. Ordinary Demo state does not carry to full release and may reset before launch. Legacy Points are the stated exception that carries after launch. BetaDwarf also says Demo progress carries into the October Alpha, but that is a separate test-to-test promise. Quests, Challenges, Codex rewards, Haven upgrades, equipment, and character state each need their own current rule.

Safest rule: treat ordinary Demo progress as temporary unless the current interface identifies a persistent reward. Preserve Legacy Points as the explicit launch exception, and do not turn Demo-to-Alpha carryover into a promise for every later test.

Progression layer index

Layer
Current public rule
What to verify
Ordinary Demo state
Does not carry to full release and may reset before launch.
Exact reset timing and which state enters the October Alpha.
Legacy Points
Demo listing says they carry after launch.
Current earning sources, reward wording, account display, and any cap.
Codex and Marks
February Playtest notes describe persistent reward claims through the Codex.
What the Demo exposes now and which rewards remain claimable.
Quests and Haven
Demo includes onboarding and main quests through the first Vaultbreak plus an upgradable Haven.
Client-specific quest order, unlocks, buildings, and reset behavior.

Separate run progress from account progress

Mission progress includes the equipment, materials, quest items, discoveries, and extraction result tied to the current expedition. Haven progress includes storage, NPCs, buildings, crafting access, and other preparation systems. Account-facing meta progression includes Legacy, Marks, Codex claims, or another reward that the current interface explicitly identifies as persistent.

Do not infer persistence from where a reward appears. A material stored in Haven can still be part of ordinary Demo state. A cosmetic shown in the Codex can still require a current claim step. Read the reward text and the official carryover statement that applies to the product you are using.

After each important unlock, record the screen name, exact wording, date, client, and whether the reward is merely available, earned, or claimed. This makes it possible to recover from a reset question without treating every progress bar as permanent.

Use Legacy Points and Codex carefully

The Demo store states that Legacy Points carry after launch. February Playtest notes say Challenges award Legacy and Marks used to claim Codex rewards, and describe those rewards and currencies as persisting between tests and after launch. October notes add Codex content and adjust Legacy and Challenge rewards.

Those statements establish a durable progression concept, but they do not prove that every February reward, cost, menu, or earning rate is unchanged in the Demo. Open the current Codex and Challenge screens when they become available. Confirm the reward’s current cost, claim state, and whether it is tied to Legacy, Marks, or another requirement.

Use the Legacy Points Guide for the precise carryover boundary. Avoid spending based only on an older reward list. The Codex was described as offering options and variation rather than inherently stronger rewards; evaluate the current effect instead of assuming every unlock is a power upgrade.

Advance quests without losing the route

The Demo includes onboarding and main quests through the first Vaultbreak. Follow the primary quest icons and current objective text. July notes say the early order was revised to introduce crafting, shops, storage, NPC upgrades, and Codex systems more naturally, which means an older step order can be obsolete.

Before leaving Haven, identify the quest item or interaction that marks success. In the mission, check the objective after every major interaction rather than carrying an item deeper without knowing whether it registered. If progression stalls, confirm inventory and storage, the current scene, party ownership, and whether the action was performed in the correct location.

Official notes have fixed lost quest items, full-inventory reward failures, tracking errors, and blocked quest states. If a current objective does not advance, preserve the exact quest text, client, party state, and last successful step before retrying or using the in-game bug report.

Treat Challenges as dated objectives

Challenges can award progression and have been expanded with area, enemy, and Ability-related objectives. Their goals and rewards are volatile. Read the current objective, region, client, and expiry or test window before planning a route.

Do not assume one player’s Challenge list is universal. A party can cooperate on the mission while holding different account objectives. State which objectives overlap and which require separate actions. After extraction, confirm progress on the Challenge screen rather than relying on a combat notification alone.

Leaderboards or ranked results need the exact test and region. They should not be used to promise a launch reward unless the current official description does so.

Choose Haven upgrades by the bottleneck

Public notes connect Haven progression with storage, backpack space, healing, wound recovery, experience, gold, interaction speed, crafting, NPCs, and building bonuses. Requirements and benefits have changed between tests, so the live description must drive the choice.

Choose the upgrade that removes a repeated constraint. Storage helps when protected materials block equipment space. Backpack capacity helps when objectives end because inventory fills. Healing or wound support matters when those resources set the retreat point. Crafting access matters when a known recipe can replace repeatedly lost gear.

Do not mistake a convenient test upgrade for a final launch tree. Record the current client and date when sharing an upgrade path.

Plan progression in solo and co-op

Solo players can keep one objective and retreat rule. In co-op, compare quest credit and Challenge goals before the mission. Choose a party leader, make sure every player sees the intended objective, and agree whether the run ends after one player’s protected item or after a shared milestone.

The Demo supports the player plus up to two friends, but official store text does not fully define shared quest credit, loot ownership, or reconnect behavior. Observe those rules in the current client. If only one account advances, do not generalize until the same step is repeated.

Recover from progression mistakes

  • Confused Demo-to-Alpha carryover with launch persistence: keep the two promises separate.
  • Assumed every Haven item is permanent: ordinary Demo state still follows the reset warning.
  • Spent currency from an old Codex list: use current reward, cost, and claim text.
  • Quest stopped advancing: confirm objective, location, inventory, storage, party state, and client before repeating.
  • Party goals diverged: state each quest and Challenge before entering the mission.
  • An older route unlocks systems in a different order: follow current primary quests and markers.

Official sources

Recommended guides

Choose the guide that matches what you want to do next.

All Progression guides

4 focused guides with steps, checks, and current caveats.