The Codex is Vaultbreakers’ meta-progression layer for developing options across expeditions. February test notes describe choices and variation rather than a ladder that is inherently stronger at every step. October notes expand the system with perks, abilities, cosmetics, and Chromas. Because the game remains in testing, exact costs, unlock order, and individual effects should be read from the current client instead of an older screenshot.
Treat a Codex choice as a new option
Start by asking what behavior the choice enables. Does it alter a hero ability, improve a repeatable expedition job, add a cosmetic, or open a different path? A useful choice fits something you can deliberately do. Selecting the largest-looking number without understanding its trigger can leave the actual run unchanged.
The February description is an important boundary: variation is not meant to be automatically stronger. Compare choices by situation and opportunity cost. One option can suit solo Wolfswood exploration while another supports a coordinated party or a particular hero. Neither has to be a universal upgrade.
Separate Codex progress from Legacy Points
The public Demo explicitly identifies Legacy progression as carrying into the full release. Do not broaden that promise to every Codex state, item, currency, or unlock without an official statement. The official Demo announcement separately says Demo progress carries into the October Alpha, but that test-to-test transfer does not make ordinary Demo progress permanent at launch.
Before spending a scarce resource, read the current reset or persistence notice. Record which client is running and what the interface says. The Legacy Points guide covers the durable claim and its limits.
Choose for an observed expedition problem
Review the previous run. If ranged enemies repeatedly controlled the approach, prefer an option that helps reach, interrupt, defend, or reposition. If wounds ended the route, a cosmetic or narrow damage effect does not address the failure. If the party already has strong area control, another overlapping effect may be less valuable than recovery or mobility.
Test the result on the same hero, weapon, difficulty, enemy, and party size. Change one Codex choice or related variable at a time. Record more than damage: count resources spent, wounds taken, cooldown gaps, and whether extraction became safer.
Read prerequisites and branches before confirming
Inspect connected nodes, required resources, hero restrictions, and any preview of later choices. A selection can matter because it opens a route, not because its immediate effect is large. If the current client offers refunds or resets, verify their actual cost and conditions before experimenting; do not assume another test’s policy still applies.
Take a screenshot or note of the choice before committing, especially during Alpha. Patches can change text or layout. Keep account names and personal information out of shared images.
Keep cosmetics distinct from combat power
October notes include cosmetics and Chromas in the Codex expansion. A visual unlock can be a meaningful progression reward without changing expedition statistics. Confirm its category, affected hero or item, and where it is equipped. Do not describe a Chroma as an armor tier because its color or presentation resembles rarity.
When comparing progression routes, state whether the goal is playstyle access or collection. A player who wants a hero appearance may reasonably choose a cosmetic path even when it offers no combat effect. That is a preference, not an inefficient build.
Recheck after a patch or client change
Demo, Alpha, and historical Playtest observations must remain separate. At the start of a new client, read the Codex from the beginning, confirm transferred choices, and check whether descriptions, prerequisites, costs, or available heroes changed. Do not spend immediately based on muscle memory.
If the interface shows an unexpected reset, capture the build, prior state, current state, and any official notice before attempting destructive repair. Demo-to-Alpha transfer is officially announced; launch persistence is narrower and centered on Legacy progression.
Record a reproducible Codex entry
A useful record contains the choice name, category, exact current description, prerequisite, cost, hero or equipment scope, client, build, date, and observed effect. If it changes an ability, add the unchanged baseline and the encounter used for comparison. If it is cosmetic, add the equip location and avoid implying a stat change.
Do not copy a whole tree from an older test into the current page. Verify nodes individually and mark unresolved branches. That produces a smaller but trustworthy record while the game is still evolving.
Pair Codex choices with quests and challenges
Quests and Challenges can direct what you practice and which rewards you pursue. Before selecting a Codex path around them, confirm the active objective and current reward. A challenge type mentioned in October notes may not appear in the Demo, and a quest can be revised between tests.
Use the Quests guide for route and state handling, and the Challenges guide for tracking repeatable conditions without inventing a reward table.