Attendance uses a voice or stage channel configured on the guild (Settings → Channels → default attendance channel) or overridden per event on the web. The bot compares who is in that channel at tracking time with RSVP rows for the event (or for a specific recurring occurrence).

Rules (manual and auto)

• RSVP attending and in channel → attended.
• RSVP attending but not in channel → no_show (member may get a DM).
• RSVP not_attending but in channel → attended (declined) — shows up separately from a normal attended RSVP.
• No RSVP row but in channel → attended (no RSVP) — for members who showed up without replying.
• Other statuses (e.g. tentative) are not changed by voice tracking.
• Members on leave of absence (✈️ on the roster) with tentative, not attending, or no RSVP are set to leave of absence when tracking runs.
• When DKP is enabled for the guild, members marked attended, attended (no RSVP), or attended (declined) receive the event’s DKP award (guild default or per-event override) once per occurrence. The attendance DM includes +X DKP and the updated balance. See Loot / item distribution — DKP.

Statistics & reporting

Guild Statistics (Stats permission) and the member detail pane break out Attended, Att. no RSVP, and Att. declined separately from not attending, no show, and leave of absence — in member tables, category pie charts, and the weekday bar chart. Only events with Count toward statistics enabled (default) are included; optional or practice events can be excluded on create or edit. Staff can also set these statuses manually on the event page roster.

Auto attendance (web)

Guild settings → Events: enable auto attendance and set delay minutes (1–120, default 5). After each event occurrence’s start time plus the delay, the server runs the same voice check once per occurrence (recurring events get one run per week/day/etc.). Uses the event’s voice override or the guild default. Idempotent — each occurrence is only processed once.

Event setup: Calendar & events.