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.

For an overview of announcements, attendance, and awards, explore Roblox event tracking.

Find an eventCopy link to Find an event

Open Events in community management and use search or the status filter to find its card. The card summarizes the event's status and details. Choose View to open it. Cancel and Delete appear when permitted; cancellation is available for scheduled or started events. Review the confirmation before either action.

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.

Check attendee eligibilityCopy link to Check attendee eligibility

The Dashboard attendee picker excludes members with an active suspension, an applicable community blacklist, or a Clan Labs ban. Restrictions can apply through a linked account or membership in a blacklisted or banned Roblox group. The Dashboard checks eligibility again when saving attendance or finishing the event, so a previously selected member can become ineligible.

If the response says a Roblox user cannot be an event attendee, remove the identified user from the attendee list and submit the corrected list. Host or staff permissions do not override attendee restrictions. If Roblox group membership cannot be verified, let the lookup recover before trying again.

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.

Awards during a suspensionCopy link to Awards during a suspension

An active suspension withholds that member's event experience and quota awards, whether they are the host, co-host, or an attendee. This applies to Dashboard, Discord, and API v2 event finishes. The suspension is checked when applying awards; being recorded on the event does not guarantee points.

An event can finish while a suspended participant receives no award. Check the event state, member balances, suspension status, and available audit records before treating missing points as a failed finish. Do not finish the event again or add points manually to bypass the suspension. See Suspend and restore members for the restriction lifecycle.

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.

Before finishing, confirm host and attendee IDs. If the finish request times out, fetch the event and inspect its state before retrying. Use audit records to resolve disputed awards.

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