How to Run a Node War in BDO

To run your first node war in Black Desert Online, you need five things: a tier you can honestly compete in, a declared war (a planted fort in Construction mode, or an officer application in Occupation mode), a confirmed roster on voice comms, one shot-caller, and a plan for reviewing the results afterward. Everything else — structures, comps, rotations — hangs off those five.

Our node war explainer covers the system from a player's seat: what node wars are, how the modes work, what you win. This guide is the other side of the table. You lead or officer a guild, your members keep asking "when are we warring?", and you want the first one to not be a disaster. Here's the playbook, in the order you'll actually use it.

Step 1: Pick your tier honestly

The single most common first-war mistake happens before the war is even declared: a leader signs the guild up for a bracket the roster can't carry.

Start at T1. T1 always runs Occupation mode — the one-hour, king-of-the-hill format played across a whole region — and its entry gear floor is the most accessible in the system. The format rewards exactly the things a new war guild needs to learn anyway: positioning, rotation, and listening to one voice. T2 adds a gear cap and (depending on the week) Construction mode's two-hour fort siege; T3 is uncapped and belongs to established rosters. There is no prize for skipping grades.

The honest test: look at your active roster and ask how many members are at or above the tier's recommended gear floor and reliably online on a weeknight and willing to sit in voice. That number — not your member count — is your war roster.

Step 2: Understand what "declaring" means for your mode

How you enter a war depends on the mode, and the mode depends on the tier:

• Occupation mode (always T1; T2/T3 in Occupation weeks): an officer applies the guild into that day's node war. Based on how many guilds applied, the system spawns forts across the region. Your guild then builds a nest — command post, flame towers, hwachas, an elephant — wherever in the region you choose.
• Construction mode (T2/T3 in Construction weeks): you commit by planting a fort in the node territory on the day of the war. When the window opens, every planted fort is live on the same battlefield and the last one standing wins.

Two scheduling realities to plan around: different nodes are available each day, and the roster cap varies by node — not just by tier. Before you declare, check the cap on the specific node you're eyeing and make sure your intended roster fits. For T2 and T3, remember the mode itself is set weekly by whichever guild holds Mediah, so check what this week actually is before promising your members a fort fight.

Step 3: Build the roster before the night, not during it

The difference between a guild that wars and a guild that shows up to wars is a signup process. It doesn't need to be fancy — it needs to exist, and it needs to happen before war night.

• Post the war in Discord with a hard RSVP. "Maybe" is a no. You're building a roster against a node cap; you need real numbers.
• Collect class and spec with the signup. You can't balance a comp you can't see. Even a simple list of who's bringing what lets you spot a hole before 8:55 PM.
• Enforce the gear floor kindly but firmly. A member below the tier's recommended floor dies fast and feels terrible doing it. Give them a gear-up path and a bench slot, not a silent decline.
• Make voice comms non-negotiable. Node wars are coordinated in real time. A member who won't join voice is a member who can't follow the call — and one drifting player can collapse a rotation.

A note on comp

Don't overthink your first comp — but don't ignore it either. The durable shape every node war comp builds toward is a frontline that can engage and survive, damage dealers who follow the engage, and ranged and support players who keep both alive. The specific classes that fill those roles shift patch to patch, so ask what's working in your bracket rather than copying a year-old tier list. What matters for war one is that someone is assigned to each job — not that every pick is optimal. (If you're building signup sheets or comp graphics for your Discord, our free class icon pack — all 32 classes as transparent PNGs — makes them a lot more readable.)

Step 4: Assign the three jobs that decide the night

Before the war starts, three roles need names attached. Not volunteers mid-fight — names, in advance.

1. The shot-caller. One voice, one plan. They call engages, disengages, rotations, and the final hold. They do not need to be your best player — they need to be decisive and calm, and everyone else needs exactly one instruction: follow the call. If the shot-caller is wrong but everyone follows, you lose a fight and learn something. If half the roster freelances, you learn nothing.
2. The build lead. Someone owns the structures. In Occupation, that's the nest: where the command post goes, how the flame towers and hwachas cover the approaches, where the elephant sits. In Construction, it's the fort perimeter: barricades funneling attackers into hwacha kill zones, recovery centers placed where your roster actually respawns. Structure placement decides who survives the first push — don't leave it to whoever happens to be holding materials.
3. The scribe. Someone screenshots the war results panel before it closes and posts it in Discord. That screenshot is your attendance sheet, your K/D log, and your improvement data all in one. Wars where nobody captured the results screen may as well not have happened, as far as your ability to improve goes.

Step 5: Run the night on a clock

A war night that starts at the war's start time is already late. Here's a run of show that works:

Before the window opens

• T-30 minutes: voice opens. Members trickle in, gear gets checked, consumables get confirmed — elixirs, food, repair kits. Anyone missing something still has time to fix it.
• T-15 minutes: the brief. The shot-caller states the plan in two minutes or less: where the nest or fort is, what the opening looks like, what the win condition is tonight. Long briefs get forgotten; short ones get followed.

During the war

• Build phase: the build lead directs; everyone else hauls and places. In Occupation, get the nest defensible before you go looking for fights. In Construction, an unfinished perimeter is an invitation.
• Fight phase: the shot-caller's game. In Construction, that means managing push timing while keeping enough bodies home to hold your fort. In Occupation, it means choosing which forts to contest, when to rotate, and — critically — when to stop rotating and commit to the hold.
• The final hold (Occupation): remember the last remaining fort runs on a hidden random timer bounded between the 40-minute mark and the hour. If you're holding late, you don't get a countdown — you hold until the war tells you it's over. Brief your roster on this before the war, because the first time a guild experiences the hidden timer without warning, half of them think the game is broken.

The last five minutes matter more than the first fifty-five

Whatever happened, end the night on voice with two sentences: one thing that worked, one thing to fix next war. Then let people go. Post-mortems longer than five minutes on war night turn into blame sessions; save the real review for daylight.

Step 6: Close the loop after the war

This is the step that separates guilds that improve from guilds that repeat their first war forever.

• Log attendance. Who signed up, who showed, who no-showed. Over weeks, attendance is the stat that predicts guild health better than any combat number — we wrote a whole piece on tracking node war attendance and why it matters.
• Log the combat stats. Kills and deaths per member, from the scribe's screenshot. Read them with context — raw K/D judges engagers and supports unfairly, and our K/D benchmarks guide covers how officers should actually interpret the ratio. If you want to understand every column on that results panel, see our stats explainer.
• Watch trends, not nights. One bad war is noise. The member whose deaths climb four weeks straight, or whose attendance quietly fades — that's signal, and it's invisible unless you're logging.

Most guilds run this loop with screenshots and a shared spreadsheet, and that works. Some use bots like CritIQ (full disclosure: we make CritIQ) to read the war screenshot automatically and turn it into attendance records, per-member K/D, and trend dashboards. Either way, the principle stands: the guilds that track results are the guilds that improve.

First-war mistakes leaders make

• Declaring above your bracket. Losing 0–40 at T2 teaches your roster nothing except that node wars aren't fun. Win at T1 first.
• No named shot-caller. "We'll figure it out in the fight" is how twelve people push in six directions.
• Treating the build phase as downtime. The first push arrives whether your hwachas are placed or not.
• Benching people silently. If someone doesn't fit the night's roster, tell them why and when they'll rotate in. Silent benches bleed members.
• Skipping the results screenshot. No screenshot, no data, no improvement. Make the scribe role real.
• Reviewing at midnight. Hot takes after a loss cost more than the loss did. Two sentences on the night; the real review tomorrow.
• Quitting after a bad month. Every established war guild was once a new war guild getting rolled. The ones still standing kept declaring.

Frequently asked questions

What tier should a new guild start node wars in?

Tier 1. T1 always runs Occupation mode, the entry gear floor is the most accessible, and the format rewards coordination over raw gear. Win consistently at T1 before you think about T2 — jumping brackets early is the fastest way to burn out a new war roster.

How many members do I need to run a node war?

It depends on the node — the roster cap varies node by node, not just by tier. Small rosters are viable at T1, and a coordinated small group beats a disorganized full roster. Check the cap for the specific node you want before declaring, and bring the most coordinated players you have rather than the most players.

How do I actually declare a node war?

It depends on the mode. In Construction mode, you commit by planting your fort in the node territory on the day of the war. In Occupation mode, an officer applies the guild into that day's node war. T1 is always Occupation, so a first-time guild will almost always be applying in rather than planting a fort.

Do I need a shot-caller for node wars?

Yes. One voice, one plan. A node war without a shot-caller is a collection of solo players wearing the same guild tag. The shot-caller does not need to be your best PvP player — they need to be decisive, calm, and loud enough to be followed. Pick one person before your first war and give everyone else one instruction: follow the call.

What should I track after each war?

At minimum: who showed up, kills, and deaths — screenshot the in-game war results panel before it closes. Over weeks, attendance and per-member trends tell you far more than any single night. The guilds that log results and review them are the guilds that improve.

What happens if we lose our first node war?

Nothing bad. Every participating member still earns silver — winners just earn more — and your guild walks away with a results screen full of information. Most guilds lose their first several wars. Review what happened, fix one thing per week, and treat the first month as paid practice.

The bigger picture

Running node wars changes what a guild is. Before your first war, a guild is a chat channel with a shared tag; after a month of weekly wars, it's a team — with a caller people trust, a build routine, inside jokes about the nest that got flattened in week two, and a results channel that shows the K/D curve bending upward. The playbook above gets you through war one. Repeating steps 3 through 6 every week is what gets you the rest. Declare the war.

More from this series: what node wars are, how Saturday sieges work, and how to read the war results screen.