Events

An event is one card people answer. The host schedules it, members press Going, Maybe or Can't make it on the card, and the bot pings the people who said yes in the channel fifteen minutes before it starts. Press Remind me on the card and the bot also messages you privately at that point, with a link back to the event; press it again to cancel. An event tied to a roster section can show who on that section has not answered, which is what an op night actually needs.

Or just tell the bot#

set up events
make the events go to #events
dispresso schedule a movie night in #events in 2 hours
dispresso make an event called scrims tomorrow at 8pm
dispresso what events are coming up
dispresso cancel the movie night

Scheduling, listing what is coming up and cancelling one are all said this way too, the same card /event schedule posts. Start with dispresso or mention it. It asks for anything it still needs, writes the same settings the dashboard writes, and the whole list of sentences is on Talk to Dispresso.

What goes on the card#

A title and a start are all that is required. The rest is optional, and all of it is on /event schedule: a picture (attach an image, or paste a link), a description, where it is (a place, a game server, or a voice channel from the server), an end, how many spots there are, a role to ping when the card goes up, and a daily or weekly repeat. Times are drawn in each reader's own timezone.

Spots and the waitlist. With a headcount set, the first people to press Going are in and everybody after them is on the waitlist, in the order they pressed. When somebody drops out, the first person waiting moves up and gets a private message saying they are in. Changing your answer and coming back puts you at the back of the queue.

Repeats. A daily or weekly event posts its next card in the same channel when the current one ends, with the same picture, place, spots and ping, and an empty list: a yes to last week's scrim is not a yes to this week's. Cancelling one stops the chain. With no end given, an event counts as over three hours after it starts.

Where to set it up#

The switch is the Events tile in /botdashboard or the Events page at /dashboard/<your server>/events, which also names the events channel and a default role to ping. With no channel named, an event is posted where it was scheduled from, or in the channel given on the command.

Commands#

/event schedule <title> <when>   post an event people can answer
      when: "in 2h", "2026-09-12 20:00" in UTC, or a unix timestamp
      ends: "2h", "90m", "22:00" in UTC, or a date
      optional: description, image or image_url, location or voice, spots, ping,
                repeat (every day / every week), channel, section
/event edit <event_id>           change any of the above; with no options, a form
                                 for the title, times, place and a long description
      clear: take the image, place, end, spots, ping, repeat, section or description off
/event list                      what is coming up, with spots and the place
/event cancel <event_id>         call one off; the card stays, struck through

Anybody can RSVP. Only the host or somebody with Manage Server can edit or cancel, the same rule the roster uses. The bot will only ping a role the host could mention themselves.

• /event schedule
  Post an event people can answer: a title and a time, plus an image, a place or voice channel, an end, spots, a role to ping, a repeat and a channel.
• /event edit
  Change any of it. With no options, a form for the long fields. The host or server staff.
• /event list
  What is coming up.
• /event cancel
  Call an event off. The host or server staff.