Tournament Organiser Hub

Run a tournament end to end: registration, check-in, brackets, referee-only disputes, results and a broadcast crew.

8 categories
50 channels
14 roles
Large

Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.

No uses yetNo views yet

Server structure

Channels

INFORMATION

welcome
Start here. Rules, schedule and format are in this category; registration is the next one down.
tournament-rules
The full rulebook. Referees rule by this document and nothing else.
tournament-announcements
Registration opening, check-in windows, bracket releases and delays.
event-schedule
Every round with its date and start time in UTC. Delays are posted in #tournament-announcements.
format-and-prizes
Bracket format, series lengths, map pool and the prize breakdown.
help-desk
Open a ticket for registration problems, disputes or anything a referee needs to see in private.

REGISTRATION

how-to-register
Eligibility, roster size, deadlines and what the form asks for.
register-here
The registration form. One submission per team, by the captain.
registered-teams
The official list of confirmed teams and seeds, posted by admins.
roster-changes
Captains post substitutions here before the deadline in #how-to-register. Admins confirm.
free-agents
Players without a team post role, rank and availability. Captains reply in a thread.

MATCH DAY

check-in30s slowmode
Captains post the team name inside the check-in window. A referee reacts to confirm and adds Checked In.
brackets
The live bracket link and a screenshot after each round, posted by admins.
match-lobbies
Lobby name and password per match, posted by the referee running it and deleted afterwards.
map-veto
One thread per match. Captains veto in turn; the referee posts the final map order.
results-submission10s slowmode
The winning captain posts the final screenshot and the match id. A referee confirms with a reaction.
score-updates
Confirmed scores as they come in, posted by referees. The bracket follows this channel.
Match Waiting Room

DISPUTES & RULINGS

disputes
Referees post dispute outcomes here. To raise one, open a ticket in #help-desk with the match id and evidence.
rulings-log
Rulings that set precedent, recorded by the Head Referee so the next event rules the same way.
referee-chatHidden from @everyone
Referees coordinating live: who has which match, what needs a second opinion.
Referee RoomHidden from @everyone

TEAM ROOMS

captains-loungeHidden from @everyone
Captains and staff only. Scheduling questions, rule clarifications, no disputes.
Team Room 1
Team Room 2
Team Room 3
Team Room 4
Team Room 5
Team Room 6
Team Room 7
Team Room 8

BROADCAST

caster-schedule
Which caster pair covers which match, with call times.
caster-notes
Storylines, team stats and pronunciations for the talent.
observer-feed
Observers post which match they are on and flag anything the casters should watch for.
overlay-and-graphics
The overlay package, team logos and lower thirds for the current event.
broadcast-issues
Stream drops, audio problems and delays, logged as they happen so the recap is easy.
Caster Booth
Observer Room

SPECTATOR AREA

spectator-chat
General chat for everyone watching. Match talk goes in #bracket-talk.
bracket-talk3s slowmode
Who is going to win, upsets, and the runs nobody expected.
highlights-and-clips
Clips from the broadcast. Include the round and match so casters can find them.
Main Stage
Spectator Voice
AFK

STAFF OPERATIONS

staff-chat
Admins and the Head Referee running the event.
staff-announcementsHidden from @everyone
Shift changes, bracket releases and decisions from the Director, for staff before the public.
volunteer-shifts
Referee and crew shifts per round. Claim a slot by reacting.
incident-logHidden from @everyone
Vetox posts role changes, channel edits and moderation here during the event.
prize-payoutsHidden from @everyone
Winner payment details and status. Admins and the Director only.
Staff Voice

Roles

Tournament DirectorAdministrator
AdminAdministrator
Head RefereeModerator
RefereeModerator
Caster
Observer
Broadcast Crew
Team Captain
Player
Coach
Checked In
Spectator
Muted

Overview

Built for the organiser who runs a bracket from sign-up to grand final and needs every stage of it to have its own channel. Information carries #tournament-rules, #event-schedule and #format-and-prizes, all read-only, with #help-desk for tickets. Registration walks a captain from #how-to-register to #register-here, where an Applications form collects the roster; #registered-teams is the official list, #roster-changes is where captains post substitutions and #free-agents is where players without a team find one. Match Day is where the event actually runs: captains post in #check-in during the window, referees drop lobby details in #match-lobbies, vetoes happen in threads under #map-veto, and the winning captain posts the screenshot in #results-submission for a referee to confirm. Disputes are referee-only: players raise one through a ticket, referees post the outcome in #disputes and the Head Referee records precedent in #rulings-log. Eight capped Team Rooms give every team a voice channel, the Broadcast category keeps casters, observers and graphics out of public view, and spectators get chat, #bracket-talk and a Main Stage. Staff Operations holds #volunteer-shifts, #incident-log and a #prize-payouts channel that only admins open.

When to use it

You have run a few one-off cups in a general gaming server and every time the same things broke: nobody could find the rules, check-ins got lost in chat, two captains argued about a result in public and a caster missed their slot. This layout gives each of those a channel with the right people able to post in it, so the next event runs on structure rather than on the organiser's attention.

What makes it different

#disputes and #rulings-log are referee-only: players raise a ticket, referees post the outcome.
#check-in, #map-veto and #results-submission accept posts from captains only, so match ops stay clean.
Eight capped Team Rooms give every team a voice channel without needing a role per team.
Broadcast is hidden: caster schedule, observer feed and overlays never appear in spectator view.
#prize-payouts is visible to Admins and the Director only, inside Staff Operations.

Recommended Vetox setup

Applications
Put the registration form in #register-here so every entry carries the team name, roster and captain contact in the same shape.
Tickets
Open disputes and general help through a ticket panel in #help-desk, so evidence stays between the captain and the referee.
Reminders
Schedule a Reminder in #check-in when the window opens and again ten minutes before it closes.
Embed Messages
Post the rules, the format and the prize breakdown as Embed Messages so they stay readable and easy to edit between events.
Logs
Point Logs at #incident-log so role changes and channel edits during the event are recorded without anyone typing.

Questions

How does check-in work with this layout?

Captains post in #check-in once the window opens; a referee reacts to confirm and gives the captain the Checked In role. When the window closes, a glance at who holds the role shows which teams are ready and which forfeit.

Do I need a role for every team?

No. Team Rooms are eight capped voice channels that any team can use, and captains share #captains-lounge. Per-team roles are only worth it in a fixed-roster league, which is what the Weekly League Season template is for.

Where do players raise a dispute if they cannot post in #disputes?

Through a ticket in #help-desk with the match id and evidence. The referee handles it inside the ticket, posts the outcome in #disputes and, if it sets precedent, the Head Referee adds it to #rulings-log.

Can casters manage the Main Stage themselves?

Yes. Caster and Broadcast Crew have stage-moderator permissions on Main Stage, so they can start the stage, invite speakers and mute without an admin present.

Common mistakes

Letting players post in #disputes, which turns every close result into a public argument before a referee has looked at it.
Using one channel for check-in and results, so a referee has to scroll past forty check-ins to find a screenshot.
Forgetting to clear Team Rooms and the Checked In role between events, so the next bracket starts with stale state.

Consider instead

Weekly League Season You run a season with fixed teams, weekly fixtures and standings rather than a bracket.
Esports Production Crew You only provide the broadcast for someone else's event.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages