BDO node war attendance tracking: spreadsheets vs Discord bots

Attendance is the single piece of guild data that everything downstream depends on. DKP, payout shares, who keeps their slot in next week's lineup, who gets benched, who gets promoted out of the trial period — all of it traces back to the attendance ledger. Get this wrong and every other officer process inherits the same drift.

BDO guilds in 2026 use one of three approaches. None is universally best; each has a clear failure mode at a specific guild size.

Approach 1: the shared spreadsheet

An officer keeps a Google Sheet with columns for each upcoming node war and rows for each member. After war ends, they tick boxes for who showed up. The sheet feeds into a DKP tab via formulas; weekly totals drive the loot priority order.

Where this works: guilds under ~30 active members. The officer doing the data entry knows everyone by name and can usually fill in the row from memory after war. There's almost no setup cost; any officer can edit the sheet from any device.

Where this falls down: anywhere past 40 active members, the post-war data entry takes 30+ minutes and is error-prone — you'll add a member to the wrong row, mark someone present who wasn't, or miss the guy who joined voice five minutes late. Members can't see their own attendance without an officer sharing the sheet, which means questions like 'why am I 6th in DKP queue' become officer-time. And the sheet has no audit history — when someone disputes their attendance, you have nothing to point to.

Approach 2: manual bot commands

An officer runs /attendance commands during or after war: /attended @user, /no-show @user, /late @user. The bot writes the entry to a database; members can /my-attendance to check their own record. Most BDO Discord bots support some version of this.

Where this works: guilds where one or two officers are reliably on-comms during every war and have time mid-fight to type commands or — more realistically — a few minutes after war ends to scroll through the voice channel and tag everyone present.

Where this falls down: it's still manual. Officer time spent typing /attended commands is officer time not spent doing post-war analysis. And the data quality depends on whether the officer remembers to mark people who joined voice late as 'late' instead of 'present', which they almost always forget. A bot-managed manual ledger is faster than a spreadsheet but inherits the same human-attention bottleneck.

Approach 3: voice-channel snapshots

The bot is configured to know which voice channels matter for a given event. At war start (and at one or two snapshot times during the war), the bot reads who's currently in those channels and writes a presence row. After war, the officer sees a clean list of who was actually in voice when fighting was happening — no manual data entry, no missed names.

Where this works: any guild that uses voice for war (which is every BDO guild). Setup is one-time — link the platoon's voice channels to the event in the bot's config — and from then on attendance is automatic. The data is also more accurate than a manual ledger because it's not relying on an officer to remember who was where.

Where this falls down: members who don't join voice (uncommon but happens) won't be marked present, even if they were in-game contributing. Most bots handle this with a manual override — officer can mark someone present after the fact — but the default is voice-presence-equals-attendance and that's a policy choice the guild has to make explicit.

What it actually costs in officer time

Rough numbers from the BDO guilds I've talked to running each approach (60-100 active member range, two node wars per week):

| Approach | Setup time | Per-war officer time | Member-facing transparency |

| --- | --- | --- | --- |

| Spreadsheet | 1 hour | 30-45 min post-war | Low — officer must share manually |

| Manual bot commands | 15 min | 15-20 min post-war | Medium — members can self-check |

| Voice snapshots | 10 min once per event | <2 min review | High — bot exposes the data publicly |

Voice snapshots win on every axis except the one where members don't use voice. Even there, the manual-override workflow is faster than the alternatives because the officer is correcting a partially-populated dataset rather than building one from scratch.

How to actually move off spreadsheets

Three steps that minimize the disruption:

1. Pick a tool that supports voice-channel snapshots. CoGM does, with per-event channel config and snapshot scheduling. Geary doesn't (it's gear-focused). Most general-purpose Discord bots don't either.

2. Run the spreadsheet AND the bot in parallel for two weeks. Reconcile after each war — when they disagree, figure out which is right and adjust your bot config (usually it's a voice channel that wasn't linked, or a member with a Discord-account mismatch). Two weeks is enough to surface the edge cases.

3. Cut over fully on week three. Stop maintaining the spreadsheet. Move DKP / payout calculations to read from the bot's data. The transition is over once members stop asking 'is the bot or the sheet authoritative.'

Members usually like this transition more than officers expect — the spreadsheet was opaque to them and the bot is queryable. The officers who run the spreadsheet sometimes resist because they've owned the source of truth and the bot diffuses that ownership; that's a feature, not a bug.

The bigger pattern

Attendance is the leading indicator that a guild has outgrown its tooling. If your officers are spending more than ~15 minutes per war on attendance entry, you're at the edge of what spreadsheets can handle. The guilds that grow past 100 active members all have automated attendance — there's no version of doing this manually that scales.

If you want to try voice-channel attendance, create a free CoGM community and link your platoon voice channels in event settings. The free tier covers the snapshot mechanic; DKP integration is on the paid tier when you're ready to consolidate the workflow.