/beacon create takes no options. It opens a form titled "📅 Create New Event" with five fields: Event Name (required, up to 100 characters), Description (optional, up to 500 characters), When (required), Max Participants (optional, blank means unlimited) and Roles (optional, comma-separated, blank means no roles).
Before the form opens the bot applies your Command Access rules, then checks that Events is switched on for the server. If it is not, the bot replies "Beacon is not enabled for this server." The plan checks run when you submit the form. If your server does not have the Create/Edit Events feature the bot replies "🔒 Creating events requires a premium subscription. Ask a server admin to upgrade in the dashboard." If the server is at its active-event limit it replies "🔒 This server has reached the limit of N active events. Upgrade for unlimited events!"
When accepts YYYY-MM-DD HH:MM, YYYY-MM-DDTHH:MM, or a bare YYYY-MM-DD (read as midnight). A time typed without a zone is read in the server timezone: the zone chosen in the Events Settings card, or, when that is left on "Follow server timezone", the Server Timezone set on the Bot page. To use another zone, add it as the last word: a common abbreviation such as UTC, EST, PST, CET, BST, JST or AEST, a full zone name such as America/New_York, or a fixed offset such as -0700 or +05:30. If the bot cannot read the time it replies "⚠️ Couldn't parse the time." and lists the accepted forms. A time that has already passed gets "⚠️ That time is in the past! Please pick a future date." Max Participants must be a whole number, or the bot replies "⚠️ Max participants must be a number."
Roles uses the form Tank:2, Healer:4, DPS:14, Flex. A label followed by a colon and a number caps that role. A label on its own has no cap. When an event has roles, members pick one from a dropdown when they sign up. When it has none, the Sign Up button signs them up directly.
On success the event is saved with one reminder taken from the Reminder lead time setting (30 minutes before the start unless you changed it), and the event card is posted to the announcement channel with the buttons ✅ Sign Up, 🚪 Leave and ⚙️ Options. Only you see the confirmation, which starts "✅ Title is scheduled for" followed by the date and the channel it was posted in. If the card could not be posted, the bot says the event was still created, gives its number, and asks you to check that it can see that channel and has Send Messages and Embed Links there. If no announcement channel is set, it tells you to configure one in the Beacon dashboard.
Good to know
- Any member can run this command unless you restrict it on the Command Access page. Cancelling, closing and reopening an event are limited to its organizer or members with Manage Server.
- Discord shows the event time to each member in their own local time, with a countdown.
- The form cannot set a category, a sign-up deadline, recurrence, class or spec choices, custom buttons or the automatic voice room. Create the event from the dashboard (Beacon Events, then Create Event) for those.
- Members who sign up once the event or their role is full go on a waitlist. When someone leaves, the longest-waiting member is moved up, receives a DM, and a notice is posted in the channel.