How to Track Node War Attendance in BDO (Without Spreadsheets)

Guilds almost never die from losing wars. They die from attrition — and attendance is the stat that sees it coming. A roster that fields 45 on Tuesday and 32 three weeks later isn't unlucky; it's leaking, and by the time the shortage is visible at the fort it's been visible in the attendance data for a month. The catch: BDO gives officers no attendance data. If you want the one number that predicts guild health, you have to build the system that records it.

This is a guide to building that system well — what it needs to measure, the four ways guilds actually do it, and the policy habits that keep tracking from turning into surveillance. It's written for officers; if you're newer to the whole scene, start with what node wars are first.

Why the game won't do this for you

BDO's guild UI has no per-war participation history. The only artifact the game produces is the war results screen — a personal stats panel that appears when the war ends and vanishes when it's closed. It lists everyone who fought, which makes it the ground truth for attendance. But it's ephemeral: nothing in the game remembers it for you, and there's no way to pull it back up on Thursday to settle who was actually there on Tuesday.

So every attendance system in every guild reduces to the same two steps: capture the roster while it exists, and store it somewhere that accumulates. The four approaches below are just four answers to how much officer time those two steps cost.

What a good attendance system actually measures

Before the tooling, the design. Guild attendance systems fail more often from bad definitions than bad tools. A system worth running measures five things:

1. Per-war presence, not vibes. "He's around a lot" is how favoritism happens. Every war produces a yes/no for every member, recorded the night it happens.
2. A rolling window, not lifetime totals. Lifetime attendance punishes your veterans for last year's exams and hides a current slump behind an old streak. A window — the last ten wars is a common choice — measures who someone is now.
3. Eligibility, not just presence. A member who joined last week didn't miss the nine wars before that. Attendance percentage only means something when it's computed against the wars a member could have attended.
4. Intent versus presence — separately. Signups and attendance are different stats, and their gap is a third one: the no-show. A member who signs up and repeatedly doesn't appear costs more than one who never signs up, because comps got planned around them. If your system can't see no-shows, your comp planner is flying blind.
5. Excused absences as a flag, not a hole. Vacations, exams, and announced breaks should pause expectations rather than drag a number down. The member who told you they'd be gone kept their commitment.

The four ways guilds track it

1. Voice roll call + a spreadsheet

The classic. An officer reads the voice channel or the party list before the war, ticks names into a shared sheet, and repeats it every single war night. It works — thousands of guilds run on it — and it costs exactly what it looks like: fifteen to thirty minutes of one officer's evening, six nights a week, forever. The sheet also decays: the officer misses a night, a column gets sorted wrong, a name is spelled three ways, and by month three the "data" is folklore. Officer burnout is the number-one killer of attendance systems, and this method feeds on it.

2. Discord signup reactions or bots

One step up: members react to a war post or sign up through a Discord bot, and the signup list becomes the record. The problem is definitional — this measures intent, not presence. The member who reacted at noon and fell asleep at eight counts as attending. Signups are genuinely valuable (they're how you plan a comp), but treating them as attendance means your no-shows are invisible — and no-shows are precisely the roster problem you most need to see.

3. Results-screen screenshots, typed in by hand

This is the method most serious guilds converge on, because it keys off the ground truth: after each war, members (or an officer) screenshot the results panel, and someone transcribes who's listed into the tracker. Presence is now real — the screen only lists people who fought. The cost is the transcription: forty names a night, six nights a week, typed by a volunteer. It's the same burnout as method one with better data.

4. Automated screenshot reading

The last step is removing the typing. This is the part where we mention that we build exactly this — CritIQ is a free Discord bot where an officer posts the war results screenshot and OCR does the rest: every listed member is marked present for that war, attendance percentages update over a rolling window, signups are tracked separately so no-shows surface on their own, and vacation flags pause expectations for announced absences. The nightly officer cost drops to posting one screenshot. Whatever tool you use, the principle is the one this whole guide is built on: the screenshot is already the attendance sheet — nobody should be retyping it.

Turning the data into policy (without becoming the fun police)

Tracking is the easy half. What you do with the numbers determines whether the system strengthens the guild or poisons it:

• Publish the standard. A threshold nobody knows about isn't a standard, it's a trap. "We expect 50% over your last ten wars" is a sentence; put it in the rules channel.
• Apply it to everyone. The moment officers are exempt, the data is political and members are right not to trust it.
• Let the window do the forgiving. A rolling window forgets old absences on its own schedule — no case-by-case adjudication, no grudges. That's the point of it.
• Treat drift as a signal, not a verdict. Attendance sliding from 90% to 40% over a month is usually burnout, a schedule change, or losing-streak fatigue. The guilds that keep people catch it with a check-in at 60%, not a removal at 30%.
• Watch no-shows harder than absences. Low attendance costs a body; a no-show costs a comp slot someone else could have filled. Different problem, different conversation.
• Pair it with performance context. Attendance says who shows up; the results-screen stats and K/D trends say what happens when they do. Reading either without the other misjudges people.

Frequently asked questions

Does BDO track node war attendance in game?

Not in any usable historical form. The war results panel shows who fought tonight, but it disappears when closed, and the guild UI keeps no per-war participation history. Any attendance record that spans more than one night exists because an officer built it — the game won't do it for you.

What is a fair attendance requirement for a BDO guild?

Most competitive-but-sane guilds land somewhere around 50% of wars over a rolling window, with hardcore sieging guilds running higher and casual guilds lower. The exact number matters less than three properties: it's measured over a recent window (like the last 10 wars) rather than lifetime, new members get a grace period before it applies, and known absences — vacations, exams, real life — are flagged instead of counted against people.

Should Discord signups count as attendance?

No — signups measure intent, attendance measures presence, and the gap between them is its own important stat. A member who signs up and shows is healthy. One who never signs up is disengaged. The one who repeatedly signs up and then doesn't show is the real roster problem, because comps got planned around them. Track signups and attendance separately so no-shows become visible.

What is the best way to record who attended a node war?

The war results screen is the ground truth — it lists everyone who actually fought. The cheapest reliable system is collecting results screenshots after each war and logging the roster from them. Doing that by hand into a spreadsheet works but burns officer time every single night; tools like CritIQ read the screenshot automatically and mark every listed member present, so the logging step disappears.

How should a guild handle vacations and new members in attendance stats?

Both need explicit handling or your numbers lie. New members should only be measured against wars that happened after they joined — judging a two-week-old member on a ten-war window they were only present for half of manufactures a problem. Vacations should be a flag that pauses expectations, not a hole in the record; a member who told you they'd be gone is keeping their commitment, not breaking it.

How do I stop attendance tracking from feeling like surveillance?

Publish the standard, apply it identically to everyone including officers, and use the data to start conversations rather than end memberships. Attendance drift is usually a symptom — burnout, schedule change, losing streak fatigue — and catching it early is how you keep the member. Guilds get in trouble when the tracking is secret, selective, or used as a gotcha instead of a check-in.

The bigger picture

Every long-lived war guild eventually learns the same lesson: the fights are won on Tuesday night, but the guild is won in the boring infrastructure around them — fair standards, visible expectations, and somebody noticing when a regular quietly stops showing up. Attendance tracking is that noticing, systematized. Build it cheap enough that it survives officer turnover, define it fairly enough that members trust it, and it stops being an administrative chore and becomes the early-warning system for the only resource a guild actually has: people who keep showing up.