How to track who actually showed up to a Discord event
Discord's scheduled events have an Interested button and nothing after it. You can see who said they would come. You cannot see who joined the voice channel, who turned up half an hour late, or who never came at all - and for raids, scrims, classes, rehearsals and community nights, that is the list that matters. Events, a free part of VoiceChannels, takes that attendance for you, from voice, without anybody typing a command.
Interested is a promise, not attendance
The bot reads each event's Interested list as the roster - the people you are expecting - and treats joining the event's voice channel as checking in. There is no reaction to press and no command to remember: being in voice is being there. Anybody can still come without pressing Interested, and they are counted too.
What the attendance says
| On the attendance | Means |
|---|---|
| ✅ Came | On the Interested list, and in voice by the time check-in closed. |
| 🕒 Late | On the list, but arrived after check-in closed. |
| ❌ Didn't come | On the list, and never joined - or not for long enough, if you set a least time in voice. |
| 👋 Walked in | Came without pressing Interested. |
Beside each name is the time spent in the event's voice channel, in hours and minutes, added up over every visit - somebody whose connection dropped twice is counted once, with the total.
Set it up in two steps
- Run
/setupin your server and press 📅 Events - or open Events on the dashboard. - Pick the text channel the boards go to, then press Turn on. The bot needs View Channel, Send Messages and Embed Links there, and View Channel on each event's voice channel so it can see who is in it.
Then schedule events the way you already do: Create Event, with a voice or stage channel as the location. Nobody has to press Start - the bot goes by the scheduled time. The event check-in guide shows each screen.
What happens on the night
- 15 minutes before the start - or at once, if somebody starts the event early - the check-in board goes up in your Events channel, listing everybody on the Interested list as not here yet. As each of them joins the voice channel, the board moves them to Here.
- 10 minutes after the start, check-in closes. Everybody on the list who has not come is marked, and a “need a sub” post asks for as many people as are missing.
- Anyone from the list who turns up after that is marked late, not missing.
- Once everybody has left and the channel has stayed empty for 10 minutes - sooner, if Discord has ended the event or its scheduled end has passed - the board is edited into the attendance. An event that never empties is closed 12 hours after its start.
Every one of those times is a setting; the numbers above are what a server gets until it changes them.
Keep a record you can look back on
- The board itself becomes the attendance - one message per event, edited in place rather than a stream of posts.
- Pick a channel for an attendance copy on the dashboard - a staff-only channel, say - and every finished attendance is posted there as well.
- The dashboard's Events page keeps the history: each event with how many came, were late, did not come or walked in. Open one to see every member by name, with their time in voice.
- A recurring event gets its own board and its own attendance every time it comes round.
Tune it to how your server runs events
/setup keeps to the essentials: the channel, on or off, and whether to post for subs. Everything below is on the dashboard's Events page, which also walks through an evening in your own timing.
| Setting | Default | When to change it |
|---|---|---|
| When check-in opens | 15 minutes before the start | Earlier for events that form up beforehand, so people check in while they gather. |
| When check-in closes | 10 minutes after the start | Right at the start for a strict start time, later for a relaxed one. |
| Least time in voice that counts | None - any time counts | Raise it so somebody who looks in for a minute is not counted as having come. |
| How long an empty channel waits | 10 minutes | Longer if people step out between rounds and come back. |
| Longest an event runs | 12 hours | Shorter if your events never run that long. |
| “Need a sub” post | On, when 1 or more are missing | Off if you never take substitutes, or wait until more places are empty. |
| Pings | None | A role as check-in opens, the listed members not in voice yet, and a role for the sub post. |
| Which events | Every voice and stage event | Only the events held in channels you pick. |
| Attendance copy | None | A second channel - a staff log, say - that gets a copy of every finished attendance. |
Big events: hold it at a generator or a pool
Set an event's location to a VoiceChannels Join to Create generator, or to an auto-scaling pool, and every room it opens during the event counts as the event's. Joining is the check-in, and time in any of those rooms adds up - so a raid can split into squads, each in a room of its own, without anybody falling off the attendance.
No board? Check these
- Events is turned on, with a channel picked.
- The event's location is a voice or stage channel - an event held anywhere else has nothing to check in to.
- The bot can see that voice channel.
- If you limited Events to some channels, the event is held in one of them.
- Its check-in had not closed when Events was turned on - an event already past that point is skipped.
When something stops Events, the Events screen says what. Every timing, permission and message in full is on the Events feature page.
Take attendance at your next event
Events is free on every server, and it takes two steps to set up.
Add to Discord