The public Vaultbreakers Demo supports solo play or co-op with up to two friends, making a maximum party of three. Its playable mode is PvE and covers part of Wolfswood through the first Vaultbreak. The base game advertises both PvE and PvPvE, while October notes describe broader Alpha social and party systems. Use the Demo to learn coordination without assuming every Alpha server or matchmaking behavior is already live.
Build a party around three clear jobs
Before departure, compare heroes, recovery, weapons, Ability Items, and active quests. You do not need fixed classes. Assign moment-to-moment jobs instead: one player opens or holds close pressure, one watches ranged or flanking enemies, and one preserves the next recovery, control, or objective interaction. Roles can rotate as cooldowns and wounds change.
State the run’s primary purpose. A quest, first Vaultbreak, route-learning session, gear test, or Legacy goal creates a shared extraction decision. Without that agreement, one player may push toward an objective while another stops at every optional encounter.
Before the run
Confirm party of one to three, active objective, equipment condition, wound treatment, and who calls extraction.
During combat
Name priority enemies and positions, stagger major abilities, and keep every player on one side of the threat.
At transitions
Regroup before buildings, one-way routes, Vault interactions, teleporters, and portals.
After success
Secure rewards in Haven, compare quest credit, restock, and agree on the next run before re-queueing.
Invite and verify the correct client
All players should launch the public Demo AppID 4488770 for the current free slice. The unreleased base-game AppID and historical Playtest are separate products. A friend owning or wishlisting one does not prove access to another. Confirm game title, build, and update status before troubleshooting party creation.
Use the current Steam and in-game invite flow. October Alpha notes mention expanded Steam friend integration, but the live Demo interface is the authority for its available buttons. Do not install an unverified client or trade for supposed access when an invitation fails.
Make combat information short and specific
Use enemy role plus landmark: “Sniper above the farm,” “bear entering left,” or “Chosen behind us.” Say when a major shield, control, wound-recovery action, or potion is unavailable. Because October potions share a cooldown, a player who just used one cannot promise a second specialized response immediately.
Avoid overlapping every powerful ability. One player creates the opening, another uses the payoff, and the third watches for a new angle. If control already holds a pack, preserve the second control for reinforcements or retreat.
Share route and quest state deliberately
At each major junction, confirm direction and objective progress. A party member who sees a quest update should say so; the others should check whether their trackers advanced. Do not assume pickups, kills, interactions, or rewards are always shared until the current client demonstrates it.
Before crossing a one-way portal or starting a Vault event, count the party and check health, wounds, cooldowns, backpack space, and equipment condition. A teammate still sorting inventory can be left without a safe path if someone activates the transition early.
Handle loot without stalling the group
Move to safety before opening comparison screens. State when an item is important for the run’s purpose, but do not build a universal ownership rule from one group’s preference. If the client allows transfer or dropping, verify its current behavior before planning around it.
Leave room for quest objects and meaningful discoveries. A party that fills every backpack with replaceable supplies will spend more time sorting and may be unable to secure a rare recipe or gear piece. When a valuable result is found, reassess the extraction threshold together.
Recover as a team
When one player needs to heal or treat a wound, the others should control sightlines and stop advancing. Ordinary lost health and wounds are different layers, and using the wrong item can start a shared potion cooldown without fixing the limitation. Call the treatment and remaining supplies.
If someone is repeatedly downed or separated, change positioning before changing the whole loadout. Shorten attack commitments, keep enemies on one side of the camera, and use a nearer fallback landmark. The Healing and Wounds guide provides a common diagnosis vocabulary.
Make extraction one party decision
Agree on triggers in Haven: main objective complete, important item found, wound treatment exhausted, gear badly damaged, or a real-world time limit. When one occurs, the default becomes leaving. A player who wants another optional fight should explain its value and route rather than silently pulling enemies.
At the portal, announce the interaction, visually count everyone, and follow the current client’s prompts. Historical group-extraction timings should not override Demo behavior. The Extraction guide covers portal preparation and mode boundaries.
Know what solo play changes
Solo is officially supported. It removes party communication and overlapping cooldowns, but it also removes the second pair of eyes, rescue options, and role coverage. Bring a loadout with an ordinary combat answer, emergency movement or control, correct recovery, and enough inventory space.
Use terrain to narrow enemy angles and choose a conservative extraction threshold. Solo is not evidence that party systems are broken, and co-op is not required to experience the Demo’s first Vaultbreak.
Keep PvPvE and cross-platform claims out of Demo advice
The Demo is PvE. Alpha is expected to add PvPvE and expanded Haven social behavior, so those systems need separate live verification. A party strategy against AI does not establish spawn, loss, portal, or matchmaking rules against other players.
The official current platform is Windows PC through Steam. Controller support does not confirm a console version, crossplay, cross-save, or a console party network. Do not promise any of those features without a first-party announcement.