Built in 11 commands 8 settings

Beacon Events: Set it up

In short

Switch Beacon Events on, run setup and create your first event. Members then sign up with buttons and get reminders on their own.

The dashboard's health check expects: Announcement channel. It shows a warning while one of these is missing or points at something deleted. The steps below say what each one does.

Beacon Events posts an event card with sign-up buttons, keeps the roster up to date, reminds the people who signed up and records who turned up. These steps are the shortest path from an empty server to a finished event.

1. Turn on Beacon Events

Open the dashboard, pick the server, open Services and switch on Beacon Events.

Who can switch it on, and before it is on

Changing services on the dashboard needs the manager access level. Until Beacon Events is on, its commands reply "The Beacon Events service is switched off in this server." If you have Manage Server, a button under that reply switches it on.

2. Run setup

Open Beacon Events from the service list. Until an announcement channel exists, Home shows a card that says so: press Set it up for me.

What setup creates

An owner, or anyone whose role has Edit on Beacon Events, can run setup, from that card or with Run setup under Setup and health on the Settings page. Setup:

  • uses the announcement channel and the log channel picked on Settings, when the bot can still open them
  • otherwise creates #beacon-events, a channel everyone can read but only the bot can post in, and a private #event-logs channel
  • saves both and posts a "Beacon Events is Live!" message in a new announcement channel

If a channel with one of those names already exists and the bot can see it, setup reuses it. Nothing is written to #event-logs; the announcement channel is the one that matters. Running setup again keeps the channels you picked and every other setting, and posts no second welcome.

3. Check the settings

Open Settings in the Beacon Events menu. Pick another Announcement channel only if you want cards somewhere else.

What each setting does
  • Announcement channel is where every event card, reminder, waitlist notice and completion recap goes. Pick another channel from the list to move them.
  • Reminder before the start sets the default reminder for new events: 30 minutes unless you change it.
  • Default event length is how long a new event lasts: 2 hours unless you change it. The editor can pick another length for each event.
  • Example roles for /beacon create only sets the example text in the Roles box of the /beacon create form. It does not add roles to new events, so you set roles on each event in the next step.
  • Post a recap when an event ends is on by default. Turn it off and events end without the thank-you post.
  • Time zone for events follows the server's time zone by default. The Server timezone on the Server settings tab of the Bot Settings page then decides how a time typed without a zone is read. Pick a zone here only if Beacon Events should differ from the rest of the bot. See Server timezone.
  • Warn about a short event sets how long before sign-ups close an event that is still short of its minimum warns its organizer and pings its Ping when short role. Pick 1, 3, 6, 12 or 24 hours. It is 3 hours unless you change it. Sign-ups close at the start, or at the sign-up deadline when the event has one.
  • Event manager role is optional. Pick a role from the list of your server's roles. Members with that role run every event the way its organizer can: cancel, close and reopen it, without the Manage Server permission. Pick None for no such role.
  • Voice rooms sets where event voice rooms are made and how early they open.
  • Calendar makes a link that shows all your upcoming events as one calendar. Paste it into Google Calendar, Apple Calendar or Outlook as a calendar to subscribe to. Anyone who has the link can see your upcoming events, so share it with members only. Make a new link replaces it and the old one stops working. Turn off removes it. Show the calendar links on event cards controls the Add to calendar links on each card. It is on by default. Cards change the next time they update.
  • Discussion threads sets whether new events start with a thread under their card and how long Discord waits before it hides a thread nobody has posted in.
  • Attendee role gives a role of your choice to the members who are confirmed (attending or late) for an event while it runs, or from the moment they are confirmed. The bot takes it away when no event of theirs is running, and never takes it from a member who had it already. The bot needs Manage Roles, and its own role must be above the attendee role in the role list. A role with an admin-level permission (such as Administrator, Manage Server, Manage Roles, Ban Members or Kick Members) or one that belongs to an integration cannot be picked, so signing up never hands out moderator powers. The server's owners and managers get one notice when the bot cannot give the role. Each event can pick its own attendee role in the editor, under Discord extras: the server's role, none or another role. A member who is confirmed for two events keeps each role until no event that gives it is running.
  • Setup and health says whether the announcement channel exists, whether the bot can post there and whether a time zone is set. Home lists the same problems under Needs you.

4. Create the event

In Discord, run /beacon create, or press New event in the Beacon Events menu of the dashboard. Either way the card lands in the announcement channel with the buttons ✅ Sign Up, 🚪 Leave and ⚙️ Options. Discord shows each member the start time in their own local time.

The form in Discord

The form asks for:

  • a name and an optional description
  • the start time, such as 2026-03-10 20:00, tomorrow 8pm or fri 20:00 (add a zone such as PST or UTC+2 if it is not the server timezone)
  • an optional participant cap
  • optional roles as Tank:2, Healer:4, DPS:14, Flex

The event lasts the Default event length from the Settings page. Submitting works on every server, with no limit on open events. See /beacon create.

The editor on the dashboard

The New event editor takes the same basics (times are in the server timezone). It adds a length (30 minutes to 8 hours), a category, roles with class and spec choices, several reminders (channel or DM), recurrence, a sign-up deadline, a minimum number of participants, a role to ping when the event is short, an attendee role and an automatic voice room.

The preview beside the editor is the card the bot posts, in the server's language. It changes as you type. When you edit an event, it also shows the members already signed up.

The Roles step has presets for a WoW raid, an FFXIV party, a Guild Wars 2 squad, an Elder Scrolls Online trial, a Lost Ark raid, a Black Desert node war, a New World group and a Throne and Liberty party. Each fills in that game's usual roles, caps and classes or specs, and you can change any of it. Every step has a save button, so an event can be saved after its first step. Leaving the editor with changes you have not saved asks first. Saving posts the card at once and confirms "Event created and posted to Discord!", or tells you to set an announcement channel first.

Copy to next week, on Home and on an event's page, opens the editor filled in from that event a week later. Nothing is made until you save, and you organize the copy. Start fast on Home does the same for a template or the last event.

A template keeps the card, the roles, the repeat, the length, the minimum number of participants and the sign-up deadline. A number the template leaves blank is not set: the event uses your default length and has no minimum and no deadline. A template never keeps roles of your server (such as the attendee role or the role to ping), so it works on any server it is shared with.

Discord extras in the editor

The last step of the editor has a Discord extras part. Each switch belongs to one event, and a repeating event keeps its switches from run to run.

  • Add a Discord event also shows the event in your server's Events list in Discord, with its start and end and a link to its card. The bot makes it once the card is posted, keeps it in step when you change the title, the description, the start or the length, and removes it when you cancel the event. If you delete it in Discord, the bot does not make it again. The bot needs the Create Events permission, which its invite asks for, and Discord allows 100 scheduled events at a time on a server. If either stops it, the server's owners and managers get one notice in their dashboard notifications.
  • Open a thread under the card makes a public thread on the card once it is posted, so members can talk about the event in one place. It starts on or off from the Discussion threads setting. The bot needs Create Public Threads in the announcement channel.
  • Send reminders in the thread too also posts each reminder line in that thread, without mentions.
  • Keep sign-ups for the next run is part of Repeating events and shows for events that repeat. Each new run starts with the members who were confirmed or on the bench in the run before, in the same roles. Members who were absent or tentative are left out, and a member the new run has no seat for waits on its waitlist.

5. Let members sign up

Members press Sign Up on the card. The card updates within a couple of seconds.

Roles, the waitlist and the other buttons
  • Sign Up signs a member up straight away. When the event has roles, it opens a "Choose your role..." dropdown instead, with a second dropdown for class or spec when those exist.
  • When the event is full, new sign-ups go on a waitlist ("⏳ This event is full! You've been added to the waitlist"). When a role, class or spec is full, the reply names it ("⏳ Tank is full, so you're on the waitlist.") and the member can pick another role instead.
  • Leave removes a sign-up. If that frees a seat, the longest-waiting member whose role has room moves up, with a DM to them and a notice in the channel.
  • Options lets a member mark themselves 🤔 Tentative, 🕐 Late, 💺 Bench or ❌ Absent. Bench and Absent members get no reminders, and the reply says so.
  • Only members marked attending hold a seat. One who switches to another status frees it for the next in line. A member on the waitlist keeps their place as Tentative or Late and leaves the waitlist as Bench or Absent.
What the card shows

The bot, the dashboard and the editor's preview all draw the same card:

  • the title, with 🔒 while sign-ups are closed, "✅ [COMPLETED]" once the event has ended and "🔴 [CANCELLED]" when it is called off
  • When: the start and the end in each member's own time, a countdown, the category and "Hosted by" with the organizer
  • Attending: one count, the confirmed members against the participant cap, then the tentative and late ones, for example "18 / 20 confirmed, 2 tentative, 1 late"
  • the time sign-ups close (or "Closed")
  • Voice channel: a link to the event's voice room once the bot has made it, until the event ends
  • Add to calendar: links that add an open event to Google Calendar or any calendar app (an .ics file), until the event ends. They work for anyone who sees the card, signed in or not. You can hide them for the whole server in Settings.
  • Still need: the roles under their cap (such as "1× Tank, 2× Healer") and how many more confirmed sign-ups the event needs to reach its Min Participants. It shows while new sign-ups are open and the event is not full.
  • one section per role, with its confirmed members against its cap. Tentative and late members are listed with a tag and do not count. A member who picked a class or spec is listed under the role above it, with the class or spec beside the name.
  • No role yet for members signed up without a role on an event that has roles
  • Bench, Absent and any other status under Other
  • the Waitlist, in its order
  • your own fields. The editor's eye hides a field, the built-in When, Attending and Roles included. Hiding Attending or Roles also hides its line under Still need.

Every label is in the server's language.

6. Let reminders go out

You do nothing here. The bot checks once a minute and posts the reminder at the right time.

What the reminder says, and when none goes out

At the reminder time the bot posts "⏰ Title starts in 30 minutes!" in the announcement channel. Then come "Heads up:" and a mention of every member signed up as attending, tentative or late.

  • Reminders added as DM in the dashboard editor go to each of those members privately. A member whose DMs are closed is skipped. Every DM from the bot ends with the name of the server it comes from.
  • A reminder that comes due before anyone has signed up waits. It goes out within a minute of the first sign-up, as long as the event has not started. None is sent for a cancelled event. Closing sign-ups does not stop reminders.
  • An event with a Min Participants that is still short at its warning time sends its organizer one DM. The warning time is 3 hours before sign-ups close unless you pick another in Settings. Sign-ups close at the start, or at the sign-up deadline when the event has one. The DM says how many more confirmed sign-ups the event needs and links to the event's page. An event made after that moment sends none.
  • An event with a Ping when short role also gets one post at the warning time. The bot posts in the event's channel (or in its thread when reminders go there too) and pings that one role. The post says what the event still needs, in the words of the card's Still need line, and links to the card. The role must be one anyone can mention, or the bot needs the Mention Everyone permission. No post is made for an event whose sign-ups you closed. Moving the start of an event gives the DM and the post another go for the new time.

7. Change course if you need to

Use /beacon close to stop new sign-ups, /beacon cancel to call the event off or /beacon clone to copy it to a new date. Only the organizer, a member with the event manager role or a member with Manage Server can close or cancel.

What each command does
  • /beacon close stops new sign-ups and role changes. The card shows a 🔒 and keeps its buttons, so members already signed up can still change their status or leave. Reminders, the voice room, completion and the next run of a repeating event go on as usual. /beacon open lets new sign-ups in again.
  • /beacon cancel, or Cancel the event on the event's dashboard page, marks the card "🔴 [CANCELLED]" and removes the buttons.
  • For a repeating event, cancelling skips that one date and the next run is posted within a minute. To end the series, edit its next run on the dashboard and choose None under Recurrence in the Finish step. A run that is under way can still get a longer Length.
  • /beacon clone copies an event to a new date, roles and reminders included.

See /beacon close, /beacon cancel and /beacon clone.

8. Let the event close itself

When the event ends, the bot marks it complete. You do nothing here.

When an event ends and what completing does

An event ends at its start plus its length: the Length picked in the editor, or the Default event length. Until then the card keeps its buttons. The card shows the start and the end, and Discord shows both in each member's own time.

At the end the card's title becomes "✅ [COMPLETED]" and the buttons go. The announcement channel gets "✅ Title is complete! N attended. Thanks for joining!"

  • N is the number of members who joined the event's voice room, when the bot created one. Otherwise it is the number signed up as attending or late.
  • No recap is posted for an event that was never posted to Discord, or when Post a recap when an event ends is off.

Attendance is credited at the same time:

  • attending members count as attended
  • late members count as half
  • when the bot created a voice room for the event, an attending member who never joined it counts as a no-show and a late member who never joined it gets nothing

The voice room goes once the event has ended and nobody is in it. A recurring event posts its next occurrence when the run ends.

To correct who came, open the event and press Mark attendance: each member is attended, late, no-show or not counted. Saving replaces what the bot recorded for that event, so nobody is counted twice, and the scores update at once.

9. Export or review attendance

Run /beacon export for a CSV of sign-ups, or /beacon rep for one member's record.

What the export and the record show
  • /beacon export event_id gives a private CSV of every sign-up: Discord user ID, display name, role, spec, status, waitlisted, whether the member joined the voice room and sign-up time. You can also use Export sign-ups (CSV) on the event's dashboard page, which has the same columns.
  • /beacon rep shows one member's score, streak and badges. The Members page on the dashboard lists every member by name with their score, streak and badges, and opens a page for each one. Find a member searches by name. It matches the start of a username or a server nickname, and lists only members who signed up for an event here.
  • Insights shows how full your events got (confirmed members divided by the cap), how many of the counted members came, the days and hours your events start, the roles members took and how events from each template did. Times are in your server's time zone, with the day and hour named. Each part tells you why it is empty until an event has ended.

If something does not work, see Troubleshooting.

2 optional features with their own switch
  • Event log: event log
  • Voice room category: event voice category
Was this page helpful?
YourBot docs Reference tables are generated from the code that is running. Ask in Discord