Skip to main content

Events

Tournaments, races and team events that players sign up for, with entry fees, a prize pot, brackets and results. Internally the feature is built from generic building blocks, so a boxing tournament and a car race are the same machinery arranged differently.

Navigation path:

  • Server Admin → Events

Access requirements​

Five rights, all under the Economy section of the rights matrix:

  • admin.events.access — See Events In The Admin Area. Without it there is no page at all.
  • admin.events.manage — Create And Manage Events: create, edit, publish, cancel, delete, close registration.
  • admin.events.run — Run Events (Draws, Results): enter participants manually, check-in, withdraw, disqualify, group and edit teams, draw, start matches, enter results, create bets, award points, close and reset phases.
  • admin.events.payout — Close And Pay Out Events.
  • admin.events.manage_templates — Create And Manage Event Templates: create, edit and delete templates, and save an event as one. Using a template only needs manage.
Nothing was granted automatically

These rights ship deliberately without a backfill. A group without the admin.* wildcard does not see events until you grant them. access must accompany any run or payout grant — the other rights are useless without the door.

There is no subscription gate. The rights are the only thing between you and the feature.

How an event is put together​

An event is an ordered list of phases, and each phase is one of three kinds:

  • Bracket — knockout pairings, optionally with a third-place match
  • Lineup — everyone competes at once and you enter placements, which suits a race
  • Points — you award points over time and the standings follow

The standard templates on the create screen — boxing tournament, car race, team event, group stage plus knockout, or an empty event — only pre-arrange these phases for you. Nothing behind them is special. Your own templates sit above them; see Templates.

Registration is either solo or team. In team mode you set a minimum and maximum team size.

Templates​

A template is a saved starting point for new events, so a moderator can set up your usual Friday boxing tournament in a click instead of rebuilding it every week. Templates belong to one server and live in the Templates tab of the events page.

The template editor looks like the event settings, but every field sits behind an In template switch. Only switched-on fields are part of the template; everything else is left at its normal default when an event is created. Start, end and registration close are never part of a template. Phases are switched on or off as a whole.

There are two ways to make one:

  • Create template in the Templates tab starts empty.
  • Save as template on any event — in any state, finished and cancelled ones included — opens the editor with that event's values and every field switched on. Switch off what should not carry over, typically the name and description, and give the template a name.

To use a template, pick it under Your templates when creating an event, or press Create event on it in the Templates tab. The event is created as a normal draft with the template's fields filled in — nothing is locked, you edit and publish it as usual.

An event created from a template shows a Template: … badge in the admin list and on its detail page. It only records where the event came from, not whether it still matches. Deleting a template leaves its events untouched; their badge then reads (deleted). Players never see the badge.

The lifecycle​

Draft → Registration open → Registration closed → Running → Finished, and Cancelled from anywhere before the end.

Publishing needs a start time in the future, at least one phase, and valid team sizes if you are in team mode. Registration closes either at the time you set or when you close it by hand.

Closing the event requires every phase to be closed first, and computes the final placements from the last phase.

Paying out is a separate step, on purpose. Closing an event does not move money. The Finish tab shows a preview — the pot, who gets what, and which placements were already paid — and paying out again skips whatever has already been settled.

Settings, participants, running, finishing​

The detail page has four tabs.

Settings — name, description, times, registration mode, entry fee, team sizes, whether a no-show is refunded, whether check-in is required, DM notifications, the phase builder, the prize table, the zone exemptions, the markers and the Discord configuration.

Two things freeze as you go: entry fee, registration mode and team sizes lock as soon as anybody has registered, and a phase locks once it has been drawn — every other phase stays fully editable, even while the first one is already running. A drawn phase still takes a new name and a new Advance per pool, the latter until the following phase is drawn: only that draw reads the number. The screen tells you per phase what is still open.

Participants — search, enter somebody manually, check in, undo a check-in, withdraw somebody, disqualify somebody, and group solo participants into a team (only before the first draw).

Entering somebody works until the first draw, so after the registration deadline as well — beyond that point everybody sits in a pool and a latecomer would have nowhere to go. The entry fee is charged by default; the checkbox in the dialog leaves it out when somebody paid elsewhere. If the balance does not cover it, nothing is entered at all. In team mode you pick an existing team or open a new one; the maximum team size deliberately does not apply here.

Teams stay editable until the first draw: remove a player from a team (a paid entry fee goes back to them, and if they created the team the role passes to the next member) and add the replacement with Add player on the team. A team keeps at least one member — to take a whole team out, withdraw it. A team can be renamed at any time until the event ends. Withdrawing a team is final: its players cannot be entered again, so to swap a player, remove them instead of withdrawing the team.

Withdrawal and disqualification after registration has closed give no refund, and any open match is scored as a walkover.

Run — per phase: produce a draw and adjust it before you commit it, handle byes, start matches, enter or correct results, and close the phase, which opens the next one's draw. Points phases award and remove points here.

The draw dialog shows the phase the way it will play out: a bracket as its tree, with every round-one pairing as a card and byes already moved on to round two; a race as its start order; a group stage as its pools. To swap two teams, drag one onto the other — or click one and then the other. Nothing else moves.

Reset a phase that went wrong — even one that already has results. Its draw and the draws of every later phase are deleted, open linked bets are cancelled, and bets already paid out stay paid out. Resetting the first phase puts the event back to Registration closed: you can add participants again, and anyone dropped for missing the check-in is back in. Once prizes are paid out, phases can no longer be reset.

Finish — close the event, review the payout preview, pay out.

Markers: who wears what​

Most events hand each side something to wear so everybody can tell them apart. Under Markers in the settings you choose what this event offers: colors from a fixed palette (14 standard colors plus 12 more for big events), items from the item catalogue such as armbands or tracksuits, or both. Presets add a whole set in one click — all armbands, all tracksuit jackets, raincoats, ski gloves and more. The order matters — it is the order markers are handed out. A boxing event with just Red and Blue has every match fight Red against Blue. Templates carry the list too.

Items show their picture and their in-game name with the color, for example Armband (Red). Names and colors come from dzbot's item catalogue, so nobody has to type them.

Automatic assignment (on by default) gives every match its markers on its own:

  • At the draw the draw dialog shows each side's marker next to its name. Click it to pick a different one before you confirm.
  • In later rounds a side keeps what it wore before. If both sides wore the same, the first slot keeps it and the other gets the next free marker.
  • Staff choices are never overwritten. Markers on any undecided match on Run changes them at any time. Picking the other side's marker swaps the two, and two sides of one match never wear the same.

Players pick their own (off by default) lets a solo participant or a team's creator choose a marker on the event page after registering, until the draw. Each marker goes to one side only, first come first served. That pick is the side's marker for the whole event.

The bracket on the admin and the player page tints each side in its marker color and shows the item picture, what it wears and the team's members. When a match starts, the round-updates channel gets a "who wears what" post and every player of the match a DM with their marker and their opponents' (only if DM notifications are on). Changing the markers of a running match sends both again.

Results per side​

When you enter a result you can give each side an optional result of up to 8 characters — rounds, points, a lap time. It appears on the right of the side's row. The winner gets an accent frame, and a trophy if no result was entered; the losing side fades out. Who wins is always what you pick as winner or placement, never the result text.

Prizes and the pot​

The pot is the sum of the entry fees actually paid. A prize row gives a rank a fixed amount, a share of the pot, or both. Pot shares cannot add up to more than 100%.

Team prizes are split evenly among the members; whatever does not divide evenly goes to the player who created the team.

Entry fees and prizes move on the player's normal per-server wallet — the same balance the shop uses.

Winner roles​

A prize row can also carry a Discord role. When you pay out, each such role is taken from everybody who currently holds it on your Discord server and given to the players on that rank — every tied player and every member of a winning team. A role whose rank nobody reached is only taken away. This happens once, when the payout first completes; paying out again does not touch the roles.

Discord problems never hold up the money. A winner without a linked Discord account, a player who is not on the server, or a role the bot is not allowed to manage (it must sit below the bot's own role) shows up as a warning after the payout.

Zone exemptions​

Events held inside a zone — a boxing tournament in the safe zone, say — would otherwise trip that zone's rules: a knockout in a no-kill zone means an instant permanent ban. Pick those zones under Zone exemptions in the settings. While the event is Running — from the first draw until you close it — its active participants are exempt from every rule of those zones, including through their linked accounts. Withdrawn and disqualified participants are not exempt, and neither is anybody else.

The exemption ends with the status, not with the scheduled end time: close the event when it is over, or the zones stay open for its participants.

Cancelling​

Cancelling an event refunds every entry fee that has not already been refunded, no matter what state a participant was in, and cancels any linked bets that have not been settled.

Deleting​

A finished or cancelled event can be deleted from its settings tab. It disappears from every list, for admins and players alike; bookings, payouts and bets stay as they were. A running event cannot be deleted — cancel it first.

Betting on matches​

With admin.events.run you can attach a bet to a match that has at least two known participants. The admin who creates it becomes its bookmaker, and players bet through the ordinary bookmaker feature.

  • Betting closes automatically when the match starts. Event bets have no deadline of their own.
  • Entering a result settles the bet automatically.
  • Correcting a result does not re-settle an already-settled bet. The screen warns you when this is the case; putting the money right is then a manual job.
  • Walkovers, disqualifications and cancelling the event cancel the bet and refund the stakes.

Discord​

On publishing, dzbot can create a dedicated channel for the event and a Discord scheduled event in your guild. It announces publication, cancellation, registration closing, the draw, match results and the finish into the channels you configure, and sends participants direct messages about their registration, their pairings and their prize.

A missing bot permission fails silently here

Creating the Discord scheduled event needs the MANAGE_EVENTS permission. If your bot was invited without it, everything else still works — the event publishes, announcements post — but no Discord scheduled event ever appears and the admin screen says nothing about it. If you expect scheduled events in your guild and never see them, re-invite the bot with that permission.

Staff with admin.events.run can also run check-in and withdraw participants right in Discord with /event, and players can register there — see Discord commands.

Guests​

Show Events to guests is on by default. It makes the event list and detail pages publicly visible without a login, which is what turns an event into advertising. Turn it off if you would rather keep them behind the door.

The guest navigation entry appears only when the setting is on and at least one event exists.

What to do before your first event​

  1. Grant the rights. Nothing happens without them, and nobody got them automatically.
  2. Re-invite the Discord bot with MANAGE_EVENTS if you want scheduled events in your guild.
  3. Decide whether guests should see events.