Weekly League Season

A weekly league season: standings, fixtures, result submission, transfers, private team channels and an admin room.

  • 8 categories
  • 38 channels
  • 16 roles
  • Medium
Download Discord JSON

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

LEAGUE OFFICE

  • league-handbook

    Format, season dates, match rules, the transfer window and how disputes are handled. Read it before week one.

  • code-of-conduct

    Respect the referees, play your fixtures, no smurfing or ringers, no harassment across team lines.

  • league-announcements

    Season start, week openers, transfer window dates and playoff news.

  • notification-roles

    Pick Fixture Ping for match-day reminders and Free Agent if you are looking for a team.

SEASON

  • standings

    The table, updated after every week by the Stats Keeper. The newest message is the current standings.

  • fixtures

    This week's matches with the slot and the map or series format. Reschedules are reflected here.

  • weekly-results

    Confirmed results, one message per match, oldest to newest.

  • player-of-the-week

    One player each week, picked by the referees from the submitted matches.

MATCH OPS

  • submit-results

    Winning captain posts the score and the end-of-match screenshot within an hour. Losing captain reacts to confirm.

  • reschedule-requests

    Ask at least 48 hours ahead with a proposed new slot. The other captain replies; a referee confirms.

  • lobby-details

    Lobby names, passwords and server picks for tonight's fixtures. Delete after the match.

  • dispute-tickets

    Open a ticket to dispute a result or report a conduct issue. Referees rule in private and log it.

TRANSFERS

  • transfer-requests

    Captains post a move: player, from, to. The player confirms in the thread. Only during the window.

  • free-agent-pool

    Unsigned players: role, rank, availability. Captains browse here when a roster has a gap.

  • roster-confirmations

    Every confirmed roster move, recorded by the Stats Keeper. This is the eligibility record.

TEAM CHANNELS

  • crimson-chatHidden from @everyone

    Private to Team Crimson and the referees.

  • azure-chatHidden from @everyone

    Private to Team Azure and the referees.

  • jade-chatHidden from @everyone

    Private to Team Jade and the referees.

  • amber-chatHidden from @everyone

    Private to Team Amber and the referees.

  • onyx-chatHidden from @everyone

    Private to Team Onyx and the referees.

  • ivory-chatHidden from @everyone

    Private to Team Ivory and the referees.

TEAM VOICE

  • Crimson CommsHidden from @everyone
  • Azure CommsHidden from @everyone
  • Jade CommsHidden from @everyone
  • Amber CommsHidden from @everyone
  • Onyx CommsHidden from @everyone
  • Ivory CommsHidden from @everyone

LOUNGE

  • league-chat

    General chat for everyone in the league: players, captains, spectators.

  • power-rankings

    Your weekly ranking of the teams and why. Argue about it here, not in the team channels.

  • clips-of-the-week

    The best plays from this week's fixtures. Referees pick from here for player of the week.

  • League Lobby
  • Watch Along
  • AFK

ADMIN ROOM

  • admin-chat

    Coordination between the commissioner, admins, referees and the stats keeper.

  • referee-rulings

    Every dispute ruling with the ticket reference, the evidence and the decision. The precedent record.

  • standings-worksheet

    The working table, tiebreak notes and pending results before they are published in #standings.

  • league-logsHidden from @everyone

    Vetox posts moderation, join and message logs here.

  • Referee Room

Roles

  • League CommissionerAdministrator
  • League AdminAdministrator
  • RefereeModerator
  • Stats KeeperModerator
  • Team Captain
  • Player
  • Free Agent
  • Team Crimson
  • Team Azure
  • Team Jade
  • Team Amber
  • Team Onyx
  • Team Ivory
  • Fixture Ping
  • Muted

Overview

A server for a league that runs over a season rather than a weekend: fixed teams, one match a week, a table that matters. The League Office holds the #league-handbook with format and dates, #code-of-conduct and the announcements. Season is the public record and is read-only: #standings and #fixtures are updated by the Stats Keeper, #weekly-results is the feed of finished matches and #player-of-the-week is the small ritual that keeps a mid-table team engaged. Match Ops is where captains do the weekly work: #submit-results with the screenshot and score, #reschedule-requests when a lineup cannot make it, #lobby-details for codes and passwords, and #dispute-tickets, which opens a private ticket rather than a public argument. Transfers has a #transfer-requests channel that captains post in, a #free-agent-pool where unsigned players advertise, and a read-only #roster-confirmations where the Stats Keeper records every confirmed move so the eligibility of any player is one search away. Team Channels gives each of the six teams a private text channel and a Comms voice room that only that team and the referees can see. The Lounge carries #league-chat, #power-rankings and #clips-of-the-week, plus a Watch Along voice room for spectators. The Admin Room has #referee-rulings, a #standings-worksheet and a Referee Room voice channel for match-night calls.

When to use it

You run a season with eight teams and one match a week, and every result, reschedule and roster change arrives by DM to whoever happens to be online. This layout gives the table and fixtures a read-only home, gives captains one channel per task, records transfers so eligibility is provable, and gives each team a private room on the league's server.

What makes it different

  • Season is read-only and kept by the Stats Keeper, so the table is never edited by a captain.
  • Every team gets a private text channel and a Comms voice room visible only to that team and the referees.
  • #submit-results, #reschedule-requests and #lobby-details give captains one channel per weekly task.
  • #roster-confirmations is a read-only record of every transfer, so eligibility disputes are settled by search.
  • #dispute-tickets opens a private ticket, so rulings are made in #referee-rulings and not in public.

Recommended Vetox setup

  • Tickets

    Put a ticket panel in #dispute-tickets so a captain raises a dispute with the referees in private and the ruling is logged in #referee-rulings.

  • Reminders

    Schedule a Reminder in #fixtures every match day pinging Fixture Ping so no team forgets its slot.

  • Self-Roles

    Post a Self-Roles panel in #notification-roles for Fixture Ping and Free Agent so reminders reach players who opted in.

  • Embed Messages

    Post the standings in #standings as an Embed Message the Stats Keeper edits each week, so the table is always one tidy message.

  • Logs

    Enable Logs into #league-logs so an edited result or a deleted transfer request is traceable when a captain disputes it.

Questions

What if my league has more or fewer than six teams?

Add or remove a text channel in Team Channels and a Comms room in Team Voice for each team, plus the matching team role. Each pair is hidden from @everyone and visible to its team role and Referee, so copy that overwrite pattern when you add one.

How are results made official?

A captain posts the score and screenshot in #submit-results. The Stats Keeper checks it, posts it in #weekly-results and updates #standings. If the other captain objects, they open a ticket in #dispute-tickets and the referees rule in #referee-rulings before the table changes.

How do transfers work mid-season?

A captain posts the move in #transfer-requests, the receiving player confirms, and the Stats Keeper records it in #roster-confirmations, which is read-only. Unsigned players advertise in #free-agent-pool. Whether the window is open is stated in #league-handbook.

Common mistakes

  • Letting captains edit the standings channel, which makes the table a matter of opinion by week three.
  • Running team comms on each team's own server, so referees cannot join a match room when a dispute happens live.

Consider instead

Do you have any doubts?

Our team is there for you

0.0k

Servers

0+

Commands

0

Users

0

Languages