Vaultbreakers Combat Guide

Vaultbreakers combat rewards preparation, positioning, timing, and knowing when a fight is not worth taking. The live Demo gives you a PvE environment to learn enemy cues and the extraction loop. The October Alpha adds PvPvE pressure, but its player-versus-player tactics and risk rules should be verified after that client opens rather than copied from older tests.

Combat decision loop

Read the battlefield before damage numbers

The official store description makes an unusual priority clear: not every fight should be taken. That means route choice is part of combat skill. Before attacking, identify how many enemies are active, where additional patrols could join, which terrain limits movement, and whether an environmental mechanic can help or hurt you. A strong item does not repair a fight begun in a bad position.

Use audio as well as sight. The October notes say the Chosen of Maldrakor—the current name for enemies previously called Changelings—were updated to react to player activity and noise, while new audio was added so players can hear them approaching. The same notes improve cues for poison, corruption, Darkness, bosses, and abilities. If a cue is hard to separate from music or party chat, adjust audio levels before assuming the attack has no warning.

Keep the center of the fight readable. Against a group, move so threats occupy a similar side of the screen rather than surrounding you. Against a single dangerous enemy, avoid backing into an undiscovered area. A temporary retreat that preserves information and resources is better than forcing damage while another target enters from off-screen.

Choose a difficulty for the job

The July technical test documented Adventure and Core as PvE choices and showed Breaker as unavailable there. Official mode descriptions present Adventure as the safer growth route, Core as higher risk and reward, and Breaker as the PvPvE option. The October notes say Breaker grants triple Gold and adjust when higher difficulties unlock, but the Alpha has not opened as of this page’s check.

Use the Difficulty Guide for the current comparison. In the Demo, read the descriptions shown by the live client and choose the level that lets you recognize mistakes. If incoming damage removes your opportunity to learn a sequence, step down or improve preparation. If enemies disappear before their mechanics matter, move up when the client allows it. Difficulty should serve the task: learning, farming verified materials, completing a quest, or testing a coordinated party.

Do not transfer reward values between clients. A July Playtest mission duration, loot rule, or unlock requirement can be useful history without being the Demo’s current rule. Attach any exact value to the dated patch and product where it appeared.

Manage health, wounds, consumables, and shields

Healing and wound recovery are separate enough in official notes that you should inspect both on the current interface. Do not assume that restoring health removes every wound or that every healing item has the same use window. Read the item tooltip, observe cast or activation behavior, and test in a low-risk situation before depending on it during a boss or extraction attempt.

October’s consumable pass says most potions can be used immediately, potions share a longer cooldown, and the interface gives clearer feedback while a consumable is unavailable. That makes potion selection a loadout decision rather than an invitation to rotate through several healing items. Choose a purpose before the mission: emergency survival, a shield, stealth, or another supported effect. Avoid quoting the exact cooldown or shield values as permanent; those are balance numbers from the October test notes.

Shields also received a correction so a shield point is treated like a health point with respect to Armor and Magic Resistance. Use that as a current patch fact, not a universal launch guarantee. When comparing a defensive tool, record the current client, hero, relevant defenses, enemy, difficulty, and whether the shield actually changed the number of hits you survived.

Build around observable roles

Vaultbreakers supports weapons, armor, perks, Artifacts, Ability Items, potions, and other crafted or found tools. The useful way to assemble them is by role. Give each slot a purpose you can state: reliable basic damage, movement, crowd control, emergency defense, wound recovery, or help against a specific environmental problem. If two tools do the same job, compare their opportunity cost rather than stacking them automatically.

The Gear hub explains current item categories and crafting. It deliberately avoids a best-in-slot list because acquisition, stat rolls, thresholds, and balance are changing across tests.

Extract before the run turns against you

Extraction is not merely the last interaction. Plan it from the start. Note where the current map exposes extraction information, how the portal is presented, what the party must do, and which route avoids unnecessary fights. July notes described clearer portal visuals, audio, and interaction text, plus a fix that transported all eligible players; confirm the current Demo behavior before relying on an older portal count or party rule.

Set a withdrawal condition before entering a dangerous area. Examples include losing a key recovery item, taking wounds your current supplies cannot address, breaking essential equipment, separating from the party, or collecting an objective whose value exceeds the next fight’s likely reward. A fixed rule protects you from extending a successful run just because the last encounter went well.

In the Alpha, rival players add uncertainty. Do not assume that a green health bar, name color, or old hostility timer works exactly as it did in July. Recheck the Alpha interface, the queue description, and the current patch notes. Until then, the Demo is the correct client for learning PvE enemy behavior without opposing players.

Common combat failures

• Repeating a long attack into an enemy string: shorten the response and identify the real end cue.
• Fighting every patrol: compare the objective and extraction route before spending resources.
• Treating an old numeric patch value as current: check the Demo or Alpha client and date the result.
• Carrying duplicate consumables without a role: select one emergency answer and one different utility when the current loadout permits it.
• Separating from co-op partners: regroup before triggering a named encounter, Vault, or extraction decision.
• Blaming damage alone: inspect equipment condition, wounds, defenses, environmental hazards, and difficulty.

Sources checked

• Vaultbreakers base Steam description
• Vaultbreakers Demo on Steam
• October 2026 patch notes
• July 22, 2026 technical-test notes