Legacy Points are the clearest persistent progression exception in the Vaultbreakers Demo. The Demo store says ordinary progress does not carry to full release and may reset, while Legacy Points carry after launch. BetaDwarf separately says Demo progress carries into the October Alpha. Keep those statements separate: one describes a persistent currency or reward layer, and the other describes this specific Demo-to-Alpha transition.
Persistence comparison
Legacy Points
Public rule: carry after launch.
Use: persistent progression and reward access described through the Codex system.
Check: current earning source, balance, cap, and account display.
Demo progress
Public rule: ordinary state does not carry to release and may reset before launch.
Includes unless stated otherwise: mission, item, quest, character, recipe, and Haven state.
Check: any explicit in-client exception.
Demo to Alpha
Public rule: BetaDwarf announced carryover into the October 15–21 Alpha.
Limit: this is a dated test episode, not a promise for every later test.
Check: Alpha client and actual account state when it opens.
Earn and record Legacy safely
February Playtest notes connect Challenges with Legacy and Marks, while October notes add Challenge types and adjust Legacy rewards. The Demo store confirms the long-term Legacy promise but does not provide a permanent earning-rate table. Read the current Challenge or reward screen for the objective and amount.
Before completing a Challenge, note the client, date, objective, and displayed reward. After completion, verify the account balance or claim state. If the reward does not register, preserve the exact text and party state before repeating the activity. Do not estimate a missing value from an older patch.
Avoid publishing an optimal farm based on one test. Challenge pools, locations, enemies, rewards, and test windows change. A repeatable route needs the same current objective across enough observations to support it.
Distinguish Legacy, Marks, and Codex claims
Official February notes describe both Legacy and Marks as currencies used around Codex rewards. They also list abilities, perks, Chromas or skins, emotes, and Marks among possible rewards. October adds new Codex content. This establishes the system’s purpose, not a frozen store inventory.
Read the current screen in three stages: currency balance, reward cost, and claim status. A reward visible in the Codex is not necessarily unlocked. A currency balance is not the same as a claimed cosmetic or gameplay option. A reward from an older test may have moved, changed price, or become unavailable.
The February description says Codex rewards are intended to provide variation and options rather than inherent superiority. Compare the actual current effect before treating a reward as mandatory power.
Protect the correct account and client
Launch the public Demo from AppID 4488770 and use the Steam account on which you want progression recorded. An older Playtest library entry is a separate product relation and should not be used as proof that the Demo balance or reward state transferred.
Before the Alpha opens, take a simple record of the Demo’s Legacy balance and claimed rewards. When Alpha access becomes available, verify the official delivery flow and compare the same account. Do not assume the historical Playtest AppID is the Alpha client; the official announcement did not resolve that AppID as of this check.
If a value appears missing, first confirm product, Steam account, online state, and whether the reward was earned versus merely shown. Then use the current support or bug-report path with the exact client and time.
Decide what to prioritize
Prioritize a Challenge when its objective fits the content you can reach and the reward is clearly shown. Do not force an Alpha-only area, unavailable hero, or unstable server route to chase an older reward description.
Balance persistent progress with learning. A Challenge route that repeatedly loses equipment or blocks main-quest understanding may not be the best first goal. Finish onboarding, learn extraction, and build a replaceable loadout before optimizing a volatile test objective.
In co-op, compare Challenge lists. Players may share a mission goal without sharing every account objective. Agree whether the group leaves when one person completes a protected objective or continues for a shared milestone.
Resolve carryover questions
- “Will my Demo inventory launch with the game?” The store says ordinary Demo progress does not carry; do not assume inventory survives.
- “Do Legacy Points carry?” The Demo store says they carry after launch.
- “Does everything carry into Alpha?” BetaDwarf announced Demo progress carryover for the October Alpha, but verify the actual client and state when it opens.
- “Are Codex rewards permanent?” February notes describe claimed rewards and currencies as persistent, but verify the current reward and claim state.
- “Is the old Playtest balance the same?” No. Keep historical AppID 1851490 evidence dated and separate from Demo AppID 4488770.
- “Can I promise a farming rate?” Not without repeated current-client evidence for the same Challenge and reward.