Vaultbreakers enemies are easiest to learn as battlefield roles: the opponent that forces movement, the one that punishes an exposed line, the one that controls space, and the one that protects or strengthens the pack. October notes name Pirate Scrat, Rusthook Sniper, Rusthook Fixer, Rusthook Shoota, Rusthook Captain, Junk Chopper Trike Scrat, Mayor Nibbit, and Trained Stoneback Bear. Which are present in the Demo versus the Alpha must be verified in the active client.
Use current names and preserve old aliases carefully
The creatures formerly called Changelings are renamed Chosen of Maldrakor in the October update. Use Chosen of Maldrakor for current guidance. “Changelings” belongs only in a dated note that helps players recognize an older video, patch, or discussion.
The same update describes smarter responses to player activity and clearer audio cues. Listen before entering a room or committing to a long action. If an alert sound occurs, look for the new angle rather than continuing to attack the target already in front of you.
Ranged pressure
Sniper and Shoota labels suggest threats that reward cover and line-of-sight control; confirm their live attacks before assigning priority.
Support pressure
A Fixer or Captain may change how the group behaves. Observe buffs, repairs, commands, or control instead of guessing from the title.
Mobile pressure
A Trike Scrat or fast beast can collapse distance. Preserve space and watch its ending position.
Heavy pressure
A Stoneback Bear or named opponent can demand shorter commitments and a clear retreat lane.
Observe one complete attack before committing
From a safe distance, watch startup, travel, tracking, number of hits, delay, and recovery. Use the shortest defensive answer, then a small punish. If the enemy continues after the apparent opening, update the sequence rather than blaming input. Repeat without changing weapon or hero until the pattern is clear.
For projectiles, note the firing line, sound, speed, and cover interaction. For charging enemies, mark where they stop and whether terrain interrupts them. For area attacks, watch the boundary and persistence. Do not turn one successful dodge into a universal timing claim across difficulties or builds.
Set target priority from the encounter
A ranged enemy behind open ground may be dangerous but expensive to reach. Use cover to remove its influence while handling a closer threat, or coordinate a safe movement ability. A support role can become first priority if it changes every other opponent. A heavy enemy may be left until the smaller sources of interruption are gone.
Say target names and positions in co-op: “Rusthook Sniper on the upper right” is more useful than “that one.” If the official name is unknown in the moment, use role and landmark. The party should know who is controlling the center and who is watching the flank.
Do not merge Demo and Alpha rosters
The public Demo covers part of Wolfswood and a limited progression slice. October notes describe Alpha additions beyond that scope. A name in the patch proves the developer discussed it for the update, not that every Demo expedition can reach it. Record the client, region, difficulty, and build with each sighting.
Similarly, older February or July enemies may have been revised, moved, or removed. Preserve their observations as historical until the current client confirms behavior. This is especially important for named events and bosses.
Learn groups as combinations
Two familiar enemies can form a new problem when their timings overlap. Identify which attack forces movement and which punishes the destination. Move so both remain on one side of the camera, interrupt the role that creates the overlap, and avoid a long combo until the pack is stable.
Terrain is part of the combination. A narrow doorway can control close enemies while blocking a Sniper, but a one-way room or electrical floor may remove that safety. Survey the area before triggering the encounter when possible.
Track wounds and resource cost
An enemy is not fully understood if the strategy wins but consumes all wound treatment and equipment condition. After combat, record ordinary health lost, wounds, potions, Ability Item cooldowns, and the party’s position. A safer strategy can be better even if it takes longer.
Use a retreat threshold. If the group cannot treat another wound or the portal route crosses the same enemy type, stop adding optional fights. The Healing and Wounds guide helps distinguish resource failure from damage alone.
Create a reliable enemy entry
A useful record includes the exact current name, dated aliases, client, build, region, difficulty, party size, visible role, attacks observed, audio cue, safe response, and unresolved questions. Add a screenshot only if it clearly shows the enemy without personal account data.
Do not publish a drop rate from a few defeats. Record individual drops with their conditions, then wait for enough current-client observations to support a pattern. An official patch may name an item or enemy without defining probability.
Escalate from normal enemies to named threats
Mayor Nibbit and other named opponents may use unique behavior even if their visual family is familiar. Start the observation process again. Do not assume a Rusthook title or Scrat body implies the same attack sequence as a basic variant.
For larger encounters and Vault threats, continue to the Bosses guide. It deliberately avoids exact strategies that have not been reproduced in the October client.