Esports Production Crew

A broadcast crew server: casters, observers, graphics and tech with a schedule, a run of show and comms rooms.

9 categories
19 channels
10 roles
Small

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

CREW DESK

crew-handbook
How we work a show: call times, comms etiquette, what goes in which channel, invoicing for freelancers.
crew-notices
New bookings, crew changes and anything the whole crew must read.
broadcast-schedule
Every event we are booked for with dates, call times and who is on it. Posted by the producer and director.

RUN OF SHOW

run-of-show
The rundown for the current broadcast: segments, timings, sponsor reads. The director posts and edits it.
live-changes
During the show only: delays, swapped segments, dropped reads. One line each, timestamped.

TALENT

caster-prep
Storylines, stats sheets, player name pronunciations and sponsor talking points for the next show.
Commentary Booth

OBSERVERS

observer-callouts
Player cams, replay requests and which fight to follow, written down for the observer between rounds.
Observer Comms

GRAPHICS

graphics-requests
What you need, for which segment, by when. One request per message; graphics reacts when it is done.
overlay-assets
Finished overlays, lower thirds, transitions and team logos, with the version in the file name.

TECH ROOM

tech-room
Encoder settings, capture issues, network drops and the fix that worked last time.
Tech Comms

GREEN ROOM

crew-chat
General chat for the crew between shows.
Green Room

VOICE

Production Comms
AFK

MANAGEMENT

producer-chat
Bookings, rates, crew performance and client notes. Producer and director only.
crew-logsHidden from @everyone
Vetox posts moderation, join and message logs here.

Roles

ProducerAdministrator
Broadcast DirectorModerator
Caster
Observer
Graphics
Tech Ops
Crew
Freelancer
Muted

Overview

A working server for the people who put an esports broadcast on air: producers, casters, observers, graphics and tech. It is built around a show day. The Crew Desk carries the #crew-handbook, #crew-notices and a read-only #broadcast-schedule where the producer posts the events the crew is booked for. Run of Show is the live spine: #run-of-show holds the rundown for the current broadcast, posted by the Broadcast Director, and #live-changes is where anyone on the crew flags a delay, a swapped segment or a dropped sponsor read while the show is running, so the change is written down instead of shouted. Talent has #caster-prep for storylines, stats and name pronunciations, and a three-seat Commentary Booth. Observers have #observer-callouts and their own Observer Comms room, because the observer needs to hear the director and the casters need not. Graphics runs on #graphics-requests and #overlay-assets. The Tech Room is #tech-room for encoder, capture and network issues plus a Tech Comms voice channel. The Green Room is where the crew hangs out before and after the show, with #crew-chat beside it, and Production Comms is the intercom everyone is in during the broadcast. Producers have a hidden chat and a log channel. Freelancers who join for one event get the same access as the core crew except Management.

When to use it

Your crew works four events a month and every run of show is a screenshot in a group chat; observers miss director calls because everyone is in one voice room and graphics requests arrive by DM ten minutes before air. This layout gives the show a written rundown and a change log, gives each discipline its own comms, and keeps the intercom separate from the booth.

What makes it different

#run-of-show and #live-changes turn the rundown and mid-show changes into a written record.
Commentary Booth, Observer Comms, Tech Comms and Production Comms keep each discipline on its own audio.
#broadcast-schedule is producer-only, so the crew's bookings are never lost in chat.
#graphics-requests and #overlay-assets give graphics one intake and one delivery channel.

Recommended Vetox setup

Reminders
Schedule a Reminder in #broadcast-schedule the day before each event pinging the crew to check #run-of-show and their comms room.
Self-Roles
Post a Self-Roles panel in #crew-handbook for Caster, Observer, Graphics and Tech Ops so a #live-changes ping reaches the right discipline.
Embed Messages
Post the rundown in #run-of-show as an Embed Message the Broadcast Director edits, so the current version is one message, not a scroll.
Logs
Enable Logs into #crew-logs so a deleted #live-changes note or an edited rundown can be reconstructed after the show.

Questions

How does a one-event freelancer get set up?

Give them Freelancer plus their discipline role. Freelancer sees everything except Management, so they can read #run-of-show, post in #live-changes and join their comms room. Remove the role after the event and their access ends.

Why are there four voice rooms for a crew of ten?

Because they carry different audio. Production Comms is the intercom with the director, Commentary Booth is what goes to air, Observer Comms is the observer and director only, and Tech Comms is for troubleshooting without cluttering the intercom. A crew of ten uses all four on a show day.

Where do the organisers we work for talk to us?

Not in this server. Client conversations go through the producer, who posts the outcome in #broadcast-schedule and #run-of-show. Keeping clients out means the crew can talk plainly in #crew-chat and #live-changes.

Common mistakes

Putting the whole crew in one voice room during the show, so observers cannot hear the director over the casters.
Keeping the run of show in a document nobody refreshes, so half the crew works from an old segment order.

Consider instead

Tournament Organiser Hub You run the whole event, brackets and teams included, not only the broadcast.

Do you have any doubts?

Our team is there for you

0.0k

Servers

Commands

Users

Languages