# Take attendance of a guild fight in Discord voice

Source: https://www.nocapbots.com/docs/attendance/track-a-fight
Last updated: 2026-11-08

> Run `/attendance-start` before the fight and `/attendance-stop` after it, or let attendance follow Voice Relay. Each fight is saved with everyone who was in voice and for how long, and downloads as a CSV for your payout sheet. Attendance is in beta and free.

## Track your first fight

1. **Invite the Callout bot.** Attendance listens through the same bot as Voice Relay, so if the relay works, you're set. It never joins voice for attendance and asks for no extra permissions — see [permissions](https://www.nocapbots.com/docs/permissions.md).
2. **Start before the fight.** Type `/attendance-start` in any text channel, with a name if you like: `/attendance-start name: Node war`. Everyone already in voice is counted from that moment.
3. **Fight.** Joins, leaves, party moves and deafens are noted as they happen. The Fights page on the dashboard fills in live.
4. **Stop and save.** Type `/attendance-stop`. The reply links to the saved fight, and everyone who can see attendance gets a notification.
5. **Export.** Open the fight on the dashboard and download the CSV: one row per member, with minutes, share of the fight and whether they counted.

## Let it follow Voice Relay

With **Follow Voice Relay** on (it is by default), a fight starts when the relay goes live and stops when it does, counting the relay's own channels: the shot caller channel and every party channel. A relay that stops and starts again within two minutes carries on the same fight, and a party channel added to the running relay — see [configuration](https://www.nocapbots.com/docs/voice-relay/configuration.md) — counts from when it's added. A fight you started by hand is never ended by the relay.

## Commands

| Command | Who | What it does |
| --- | --- | --- |
| `/attendance-start` | Starter role | Starts a fight, with an optional name. |
| `/attendance-stop` | Starter role | Stops and saves it, and replies with a link to the list. |
| `/attendance` | Anyone | The running or last fight, and your own time in it. The starter role also sees the totals. |

The starter role is the one you picked for Voice Relay; Manage Server can always start and stop. The rest of the relay's commands are in [commands](https://www.nocapbots.com/docs/voice-relay/commands.md).

## On the dashboard

- **Fights** shows the running fight, a button to start or stop one, and every saved fight.
- **Members** adds up each member over the last 7, 30 or 90 days, with a CSV of that too.
- **Settings** picks which channels and roles count and the share of the fight that counts — see [how attendance counts](https://www.nocapbots.com/docs/attendance/counting-rules.md).

Officers who run payouts don't need access to anything else: give them the **Attendance** permission on the Members page — see [managers](https://www.nocapbots.com/docs/managers.md#permissions).

## If the bots restart mid-fight

A running fight is saved every minute. If the engine stops during one, the fight ends at the last minute saved and is marked **cut short by a restart**. Start a new one to carry on.

> **Tip: Name your fights.** The name shows in the list, in `/attendance` and in the CSV's file name, so "Node war" beats "Fight" when you add up payouts at the end of the month. You can rename a fight afterwards.

## Related guides

- [How Attendance counts who was at a fight](https://www.nocapbots.com/docs/attendance/counting-rules.md): How Attendance decides who counts: share of the fight, short drops, party moves, deafened time, roles, channels and what is stored.
- [Managers: share the dashboard with your officers](https://www.nocapbots.com/docs/managers.md): Invite managers to a NoCap Bots server by email or Discord username and choose what they can touch: configuration, billing or other managers.
- [Voice Relay slash commands](https://www.nocapbots.com/docs/voice-relay/commands.md): Every Callout slash command: /start, /stop, /status, /ping, /start-cross-server and /stop-cross-server, and who can use them.