Running an event on Discord

Pick a format that sustains itself

The best format is not the most ambitious: it is the one you can run every week without losing your Sunday to it. A small regular appointment builds a habit; a big event announced then postponed destroys trust.

• Quiz or blind test — easiest to host, easiest to repeat, and the format needing the least preparation.
• Tournament — high engagement, but organising load climbs fast with entrant numbers. Save it for occasions.
• Creative contest — spread over days, needs no live presence, and leaves something behind.
• A voice night with no competition — underrated. No preparation, and often what bonds a server most.

Sign-ups: why reactions are not enough

An event announced with a message and a reaction always produces the same situation: half the sign-ups do not show, two people insist they signed up with nothing to prove it, and you discover the team composition five minutes before starting.

An explicit sign-up list, visible before the start, fixes all three. Above all it lets you form groups calmly, which is the difference between an event that starts on time and one that starts twenty minutes late.

Announce at the right moments

1. Several days ahead: the initial announcement, with date, format and rewards.
2. The day before: a reminder. This is the one that makes the difference to real turnout.
3. A few minutes before: a final message in the event channel.
4. Each time, mention a notification role rather than @everyone. A server that overuses @everyone ends up with an audience that has muted it — and your next announcements will reach nobody.

Announce the rewards at sign-up, not at the end. That is what decides participation: nobody signs up to an event whose stakes they do not know.

During: the live leaderboard

A leaderboard updated during the event changes the atmosphere completely. Participants watch their position move instead of waiting for a verdict, which keeps the attention of those not in the lead.

It also removes disputes. A leaderboard visible throughout has been seen by everyone; one announced at the end has to be taken on trust — and someone will not take it.

Have two people run it if you can: one hosting, one scoring. Doing both alone is the commonest cause of scoring errors, and a scoring error in a tournament leaves a mark.

After: the part that gets rushed

• Hand out rewards immediately. A reward promised and given three days later, by hand, is nearly always given wrong — someone is forgotten, and that is what people remember.
• Publish the final leaderboard in a channel that stays. It is the proof the event happened and ended.
• Thank helpers by name. It decides whether they help next time.
• Note what went wrong while it is fresh. The ambiguous rule you discovered live takes two minutes to fix now, and never gets fixed in six months.

How Kuratos helps

The Events module takes all three obstacles: an explicit sign-up list with manual or automatic team composition, a leaderboard updated live in the channel, and automatic reward distribution on closing — role, server currency or inventory item, differing by rank.

Reminders are scheduled in advance: X minutes before the start or before sign-ups close, with the mention of your choice. The day-before reminder is what drives turnout, and it is the one people forget to send.

A recurring event is scheduled once and recreates itself, sign-ups included — which makes the small weekly appointment everything else depends on actually sustainable.