Run events and record attendance

Clan Labs events connect a structured community record with a Discord announcement. Hosts can use a configured event type or a permitted custom name, choose an approved Roblox location, and finish or cancel the event.

Create and announce an eventCopy link to Create and announce an event

Use the dashboard or /host create:

1. Select a configured event type, or enter a custom name where allowed.
2. Choose an approved Roblox location.
3. Confirm the host and optional co-host.
4. Select an allowed Discord mention role if needed.
5. Add concise notes where supported.
6. Create the event and confirm the Discord announcement appears in the configured channel.

The default host requirement is Officer. Events are unavailable when the community plan or trial state blocks the feature.

An event takes a snapshot of its type configuration when created. Later changes to that reusable event type do not silently change the event’s awards.

Finish an eventCopy link to Finish an event

Use /host finish or the Clan Labs event action. Select the event, provide attendance, and attach the required proof when community settings call for it. API v2 accepts up to 100 attendee Roblox user IDs for a finish request.

When the event finishes, Clan Labs records its state and applies the event’s configured experience or quota awards to eligible hosts, co-hosts, and attendees. Check the result before making any manual compensation.

Cancel or reannounceCopy link to Cancel or reannounce

Use /host cancel when the event will not be completed. Cancellation does not represent completed attendance.

If the original Discord announcement is unavailable, the supported reannounce action creates a fresh announcement rather than assuming the old message can be edited. Verify the new message and avoid leaving two active announcements.

API workflowsCopy link to API workflows

API v2 supports listing and fetching events, listing curated types and locations, creating and announcing an event, finishing, cancelling, and creating a fresh announcement. Read operations require events.read; changes require events.write.

Operational checksCopy link to Operational checks

• Keep announcement and proof channels accessible to the bot.
• Limit event mention roles to the intended audience.
• Confirm host and attendee IDs before finishing.
• Do not retry a timed-out finish until you fetch the event and inspect its state.
• Use audit records to resolve disputed awards.

For configuration, see Configure events. If the command is absent, follow Command is unavailable.