How to run a Black Desert Online node war: a guild officer's playbook
Most BDO wars are decided days before anyone zones in. The hour-by-hour stuff matters, but the real work happens in the days leading up: who's playing, what they're playing, where the gaps are, and what your enemy looks like this season. This is the playbook we use to run wars without burning out the officer team.
Recon starts when the schedule drops
The minute the official war schedule comes out, the first thing to do is figure out who you're hitting. Scout enemy guilds with the same kind of attention you'd put on an end-game boss. You want:
- The roster size and who's actually active
- Their gear floor (what's the lowest GS still showing up to wars)
- Class spread, especially how many of their high-impact classes are in
- Their typical role distribution (heavy mainball? cannon-heavy? do they bring an elephant?)
- Recent results and trends
This isn't optional intel. Walking into a node war without knowing what shape your opponent is in is how you get rolled in the first ten minutes. Track enemy guild rosters automatically if you can, because manual scouting is a part-time job nobody on your officer team wants.
The week-of attendance push
Three days out, post the war and start collecting signups. The mistake guilds make here is treating the signup as an honor system. People forget. Day-of attendance is always lower than your sheet shows.
A few things that actually move attendance numbers:
- Discord reminders 24h and 1h before the war. Most members aren't in your Discord 24/7. They need the ping.
- Public attendance tracking so members can see their own streak. People don't want to be the person whose attendance dropped.
- Officer DMs to anyone who's been quiet, two days before. Not pressure, just a check-in. Half the time you'll get an absence reply you would have missed.
If you're running DKP or attendance-based loot, the signup-show-up gap directly affects your loot pool. Worth tracking.
Assigning roles before the war, not during
Walking into a node war and assigning roles in the first five minutes is how you waste the first ten. Lock the comp the day before:
- Mainball — your main DPS ball. The bulk of your kill-feed comes from here.
- Flex — DPS that can shift between mainball pressure and small-skirmish responses.
- Cannon team — fort defense and offense. Underrated, often unstaffed.
- Elephant rider — if you have one, gear and skill matter more than people realize.
- Shai — buffs and protection on the ball. Don't run wars without them past a certain bracket.
- Defense — staying back, holding fort, picking off pushes. Less glamorous, just as important.
Two practical tips:
- Have a B-comp ready. Members no-show. Always. If your A-comp falls apart in the last hour, you want a known B-comp instead of officers re-rolling on the fly.
- Track who plays which role well. Some classes can run mainball or flex, but the same player isn't always equally good at both. Note this somewhere durable, not just in your head.
Comp checks (the hour before)
The hour before a war is your last chance to catch problems. Run through:
- Gear floor — does everyone signed up actually meet the threshold for this war? T1 wars run with a different floor than uncapped. Mismatches are a fixable problem if you catch them an hour out, not five minutes in.
- Class spread — too many of one class is a problem in BDO. Specifically, too many sorcs without enough disengage tools, too many wizards without enough peel.
- Voice check — confirm the shotcaller is in voice and ready. Confirm everyone else has voice working before the war starts.
- Trade routes / consumables — quick reminder in chat. People forget elixirs at the worst times.
The day-of routine
The shotcaller calls the war. Officers are running side-systems:
- One officer is on attendance — taking a snapshot when the war starts and one mid-war. Voice channel snapshots beat manual tracking by a mile.
- One officer is on adjustments — if the comp falls apart, they're moving people. The shotcaller is too busy.
- One officer (if you have the bench) is on Discord — answering questions from members who aren't in voice, fielding the "is X happening" pings.
Sounds like a lot of overhead. It is at first, then it runs itself.
Post-war analysis (where most guilds stop too early)
The war ends. Most guilds say "good game" and call it a night. The guilds that win consistently spend an extra 30 minutes here:
The data dump:
- Per-player K/D for the war
- Who actually showed up vs who signed up
- Which roles performed and which didn't
- What classes the enemy ran, what worked against us
The conversation:
- One ping to the officer channel, not 30
- One specific learning per war, not a list of grievances
- One call-out for a player who showed up and crushed it (publicly)
If you can get to "here's what we'll do differently next time" within 24 hours of the war, you compound improvements. If it takes a week, the lesson is gone.
What you'll actually look at the morning after
The questions that matter the day after a war:
- Did we hit the comp we planned, or did we patch it together?
- Was the gear floor real, or did we let people in below it?
- Where did the enemy break us first?
- What's the smallest change that would have flipped the result?
They're tied to specific data: K/D timelines, when the ball broke up, which player went down at which minute. If you have the data, you can answer these in 10 minutes. If you don't, you're guessing.
Common mistakes that lose wars
A short list of mistakes we see over and over:
- Letting under-geared members into wars they're not ready for. Nobody wants to bench someone, but the war goes worse for everyone.
- No B-comp. When the A-comp falls apart, the response is panic. Plan for it.
- The shotcaller is doing five jobs. They should call the war. Period.
- Skipping the post-war debrief. "Good game" doesn't make you a better guild.
- No real attendance tracking. Members notice when their effort isn't recognized.
- Trusting one big spreadsheet. Spreadsheets work until they don't, usually right when you need them most.
How CoGM helps
We built CoGM because Rami runs a BDO guild and got tired of doing all of this in 8 different tools. Roster sync pulls alliance + enemy guild changes from BDO every 10 minutes, so the recon work happens on its own. Members upload gear screenshots and the OCR drops AP/AAP/DP into a per-player chart you can sort by role. Event signups run in Discord with role slots and automated reminders. Voice channel snapshots handle attendance. PvP analytics give you K/D timelines and AI fight analysis, so the post-war report writes itself.
Start a free CoGM community. Pro is $10/mo per community with a 14-day trial when you want it.
Related guides
8 min read
BDO siege and node war roles explained: mainball, flex, cannon, elephant, shai, defense
What each siege role actually does, which classes fit, the gear floor for each, and the mistakes that show up war after war.
9 min read
Tracking BDO gear progression for a guild: AP, DP, AAP, and what numbers actually matter
Which BDO stats officers actually need to track for a guild, the gear floors per role and content tier, and how to keep tabs on 100+ members without losing your mind.
Ready to level up your guild?
CoGM is the free, all-in-one platform for managing gaming communities.
Get Started Free