Events & sign-ups

For raids, scrims and group nights: a sign-up post where members claim a spot in a specific role, not just "yes I'm coming".

Alpha — new; tell us if something looks off.

Set it up

1. Enable Events in the Plugin Market.
2. Optionally define your own Line-ups on the Events page. Each role in a line-up has an emoji, a label, a number of slots (0 = unlimited) and a button colour. The built-in MMO Trinity, Scrim 5v5 and Simple line-ups always work, so you can skip this step.
3. Post an event with /event create or /event setup in the channel where it should appear.

Command	What it does
/event create	Post an event. Options: title, when, roster (the line-up; empty = your first one), description, reminder (minutes before start, default 30, 0 = off).
/event setup	Post an event using a form — handy for multi-line details. Optional roster option.
/event list	Show up to 20 open events on this server, with their 6-digit codes.
/event cancel	Cancel an event by its code. The post stays, marked cancelled, and everyone signed up (except the bench) is pinged.
/event resume	Reopen an event by its code after it was paused because your network went over its plan's event limit. Only works once you're back within the limit.

Who can post events

By default only admins (Manage Server or CloudMod admins) can post events. Set an Event manager role on the Events page so raid leads can post and cancel them too. The role is a main-server role. The event's lead can always cancel their own event.

How sign-ups work

Each role is a button (up to 10 per event). Members click the one they want; clicking another role switches them, and clicking their role again removes them. When a role is full, further sign-ups go to the bench — and when someone drops out, the first person on the bench moves up automatically and gets pinged. Maybe and Out are answers, not sign-ups, so they never take a slot.

Members can add a short note when signing up ("only until 10", "bringing a friend").

Members who leave the server drop out of the roster automatically, and the bench moves up.

Times

Write the time as 2026-08-20 20:00, 20.08.2026 20:00, or relative like in 90m, in 3h, in 2d. Times in the past are rejected.

Event times are read in your network's timezone, set in project settings (or when you create the project). Discord does not tell bots what timezone a server is in — a server only has a preferred language — so this has to be configured once, and then "20

" means the same thing for events, birthdays and reminders.

The reminder pings everyone signed up (except the bench) in the event channel. Sign-ups close at the start time, and the event is wrapped up 4 hours later.

Good to know

• Each event carries a short code in its footer, for the commands that act on it.
• The buttons survive bot restarts.
• Open events per network: Node 3, Link 10, Network 25, Grid unlimited.

Requirements: Send Messages and Embed Links in the event channel.