Auto Attendance Tracking Guide

Why Attendance Tracking Matters for Your Guild

Attendance is the foundation of fair guild management. Members who show up consistently should get priority on loot, raid spots, and officer positions. Members who don't show up shouldn't get the same rewards as those who do.

The problem is tracking attendance manually. Someone has to watch who joins voice chat, write down names, update a spreadsheet, and do this for every single event. Most guilds try this for a week and give up.

Throney's automatic attendance tracking solves this with a single Discord command. No spreadsheets, no manual counting, no missed records.

How Automatic Attendance Works

Throney's attendance system is built around one concept: officers are already in voice chat with their guild. Taking attendance should take one second, not five minutes.

The Basic Flow

1. Guild gathers in voice - Everyone joins the Discord voice channel for your event
2. Officer runs the command - Type /attendance in any text channel
3. Throney captures everyone - All members in that voice channel are logged instantly
4. Records are saved - Timestamped attendance linked to each member's profile

That's it. One command captures your entire raid roster. If you're using DKP, points are awarded automatically based on the event type.

Setting Up Attendance Tracking

Step 1: Create Event Types

Go to Management → Events in your Throney dashboard. Create event types that match your guild's activities:

• Archboss - Scheduled boss spawns requiring full guild participation
• Siege War - Territory battles that happen on a set schedule
• World Boss - Spontaneous boss spawns throughout the week
• Dungeon Run - Guild dungeon farming sessions
• Guild Meeting - Non-combat gatherings for planning and announcements
• Training - PvP practice sessions and new member orientation

Each event type can have a different DKP value if you're using the loot distribution system.

Step 2: Configure DKP Values (Optional)

If you're using DKP for loot distribution, assign point values to each event type. Common configurations:

• Siege War: 20 DKP (highest value, most important events)
• Archboss: 15 DKP (scheduled, requires coordination)
• World Boss: 10 DKP (important but less scheduled)
• Dungeon: 5 DKP (regular farming)
• Meeting: 3 DKP (non-combat participation)

When attendance is logged, DKP is awarded automatically based on these values.

Step 3: Train Your Officers

Every officer with the designated role can run /attendance. Make sure they know:

• Be in the voice channel with the guild before running the command
• Select the correct event type from the dropdown
• Run the command at the actual start of the event, not before
• For long events, consider running attendance at start and end

Advanced Attendance Features

Multi-Channel Events

Large guilds sometimes split across multiple voice channels. For siege wars with separate channels for tanks, healers, and DPS, officers can:

1. Run /attendance from each channel
2. Or have everyone gather briefly in one channel for the snapshot
3. Or use the dashboard to manually add members from other channels

Late Arrivals and Early Departures

Throney captures a snapshot at the moment the command runs. For events where timing matters:

• Run attendance at event start - Captures who showed up on time
• Run again mid-event - Catches late arrivals
• Manually adjust - Officers can add/remove members in the dashboard

Most guilds run attendance once at the start and consider that the record. Consistent late arrivals become visible in member stats.

Attendance Requirements

Set minimum attendance thresholds in your dashboard. Common requirements:

• Core members: 80% attendance at siege wars
• Active members: 50% attendance at any events
• Casual members: No requirement

The dashboard shows who's meeting requirements and who's falling behind. Use this data for roster decisions without guesswork.

Using Attendance Data

Loot Priority

Attendance directly affects DKP balances if you're using the loot system. Members who show up consistently earn more points and win more loot. The system rewards participation automatically.

Roster Decisions

When you need to cut roster or promote members to core positions, attendance data removes guesswork:

• Who actually shows up for siege?
• Who's been absent for the past month?
• Which applicants would improve on current attendance?

Identifying Activity Trends

The dashboard shows attendance trends over time. Spot problems early:

• Declining attendance - A once-active member going quiet
• Event type patterns - Members who show for PvE but skip PvP
• Seasonal patterns - Lower attendance around holidays

Best Practices for Attendance Tracking

Be Consistent

Track every event or don't track at all. Inconsistent tracking makes data meaningless. If you log boss runs but forget siege wars, attendance numbers become unreliable.

Set Clear Expectations

Tell members upfront that attendance is tracked and how it affects their standing. Many guilds include attendance requirements in their recruitment posts.

Use the Data Fairly

Attendance data should inform decisions, not be weaponized. Someone with 90% attendance missing one event isn't a problem. Someone with 30% attendance complaining about loot is.

Account for Real Life

Everyone has weeks where life gets in the way. Good guilds look at trends, not single events. A month of declining attendance is a concern; missing one raid isn't.

Attendance and Alliance Management

Running an alliance of multiple guilds? Throney tracks attendance across all guilds in your alliance:

• Unified events - Alliance-wide boss runs track everyone
• Guild-specific events - Each guild can have separate activities
• Alliance DKP - Shared or separate point pools, your choice
• Cross-guild visibility - Officers see attendance across the alliance

Coordinate up to 4 guilds from one Discord server with full attendance tracking for each.

Getting Started with Attendance Tracking

Attendance tracking is included with all Throney plans. After setup:

1. Create your event types in the dashboard
2. Configure DKP values if using loot distribution
3. Run your first /attendance at your next event
4. Check the dashboard to see records populate
5. Review attendance trends weekly

Within a week, you'll have more attendance data than months of manual tracking would provide. And it takes one command per event to maintain.