Bunker vs Verity servers support up to six players, but a larger group is not automatically safer. The useful advantage is simultaneous attention: one player can repair or build while another holds a gun line and a third watches a side approach. Agree on the shell, purchase priorities, and short callouts before the raid so extra players do not produce duplicate buys and unguarded lanes.
Assign roles by team size
These are tactical assignments, not claims about special classes. Players can swap jobs between waves. Current public material does not reliably establish shared currency, build ownership, repair permissions, or enemy scaling by player count, so test those mechanics on a cheap first structure before planning around them.
Plan the bunker as one team
Choose one controlled main approach, then decide which other sides need observation rather than full investment. The builder closes gaps and maintains the movement route. The main defender positions where personal gunfire covers leaks without blocking the turret. The scout watches side and rear pressure and calls it before the wall is already broken.
Do not let every player place an isolated turret. Overlapping fire on the lane enemies actually use beats several disconnected defenses that each shoot briefly. Keep enough spacing for players to pass, reload, and return underground. A perfect-looking interior that teammates cannot cross during a breach is a failed co-op layout.
Before the raid, each player confirms: gun slots filled, firing position known, fallback path open, and repair or response role understood. One player announces the start. This avoids the common failure where someone activates the raid while another is inside a menu or holding an unfinished placement.
Communicate with short, useful calls
Use calls that name location, problem, and action: “south lane, wall low, repair”; “rear, fast pack, rotate”; “main turret blocked, move prop”; “large target front, clear small pack first.” Avoid long explanations during combat. Save shopping arguments for the preparation window.
The scout should report the first change, not every enemy. A new direction, digging behavior, damaged fallback, or turret that has stopped firing matters. A stream of obvious observations can hide the one call the builder needs.
When a major target arrives with regular Verities, agree on focus. Current walkthroughs repeatedly warn that smaller enemies can slip past while everyone shoots the large one. Let one or two players hold pack control, while the strongest single-target weapon and suitable turret pressure the durable threat.
Coordinate money without assuming a shared wallet
Ask each player what their current balance and available unlocks actually allow. The resource lead can propose priorities even if wallets are individual: complete the shell, ensure one working automated lane, preserve repairs, then add the missing damage role. No one should buy a second copy of a narrow tool before the team checks what already exists.
Current guides describe Coins as the normal building and combat currency, while Crystals feed the Egg Shop and Tech Parts use separate reward and shop paths. Keep those systems separate in voice chat. “I have 500” is ambiguous; say which currency and what purchase it supports.
Paid items should never be assigned as mandatory roles. A team can build around coin weapons and ordinary turrets. If someone owns a premium gun, treat it as extra coverage rather than the foundation of a strategy everyone else cannot reproduce.
Recover when the defense breaks
When one wall begins failing, the nearest defender calls the lane and clears the pack while the builder moves only if the current phase permits repair. The flex player covers the builder’s former angle. Do not have all players pile into the same doorway; that blocks movement and leaves other approaches unseen.
If underground retreat is necessary, keep one player watching the route back up when safe. Some current walkthroughs show Verities digging into underground rooms, so closing the hatch does not end the wave. Regroup, reload, identify where enemies entered, and return to the working defense when possible.
After the raid, diagnose the first failure as a team. If the first breach was a side lane, add sight and coverage there. If turrets were idle, fix angles rather than buying more. If ordinary packs slipped by during a durable target, formalize the pack-control role. Change one cause at a time so the next run proves whether the adjustment worked.
Solo habits that still matter in co-op
Every player should know the Beginner Guide loop, because teammates can leave or disconnect. Keep the structure compact enough that two remaining players can still operate it. Mark the main entrance and fallback clearly rather than relying on one builder’s memory.
Each player should also understand Controls on their device. A teammate who cannot cancel placement, exit a shop, or recognize the raid-start button can trigger the same failures as a weak wall. Practice those actions before difficult waves.
Co-op FAQ
How many players can join?
The Roblox Games API reports a maximum of six players for this experience. That does not prove a six-person shared economy or a specific difficulty multiplier.
What is the best two-player split?
Use a builder/repair role and a defender role. Both can shoot, but one remains responsible for structure and the other for keeping pressure off that work.
Are Coins shared?
Current reliable sources do not settle wallet sharing, structure ownership, or repair permissions. Test with one cheap item and one repair before committing the group’s plan.
Should everyone use the same gun?
No. Cover different jobs when possible: sustained pack pressure, harder single targets, and breach response. Always read current gun cards because balance and unlocks can change.
Sources checked
- Roblox Games API identity and server capacity
- Current layout and role synthesis
- Current survival role guide
The six-player capacity is official. Role division is community corroborated strategy. Wallet, ownership, repair, and scaling behavior still need direct in-game testing.