iRacing

iRacing features require a Premium subscription.

The Overseer's iRacing tab gives your league a full race operations layer inside Discord — championship standings tracked across multiple rounds, a Race Control system for filing and ruling on protests, and automated event reminders for races and practice sessions.

Championships

An iRacing championship is a Points League tournament scoped to the iRacing game. Races are scored on the F1-style placement table and cumulative standings update after every round.

Creating a Championship

Create championships from the iRacing tab on the dashboard, or directly in Discord:

/tournament create name:[Name] format:points game:iracing mode:[solo|team] rounds:[1–50]

Once created, the bot posts a sign-up embed in your configured channel. Members click a button to register. When sign-ups close, run /tournament start id:[id] to lock the roster and begin the season.

Scoring

Championships use the racing scoring preset — finishing position only, no kill/elimination points:

Position	Points	Position	Points
1st	25	6th	8
2nd	18	7th	6
3rd	15	8th	4
4th	12	9th	2
5th	10	10th	1

Positions 11th and beyond score 0 points. Standings accumulate across all rounds in the season.

Recording Race Results

After each race, record results with:

/tournament round id:[championship_id]

Attach a screenshot of the end-of-race finishing order — the bot reads it automatically and matches driver names to Discord members using saved gamertags. You can also enter results manually if the screenshot can't be parsed cleanly.

Have drivers save their iRacing screen name with /tournament gamertag set platform:iracing tag:[name] before the season starts so the bot can match them from scoreboard screenshots.

Team Championships

Set mode:team to run a team-based championship. Members form teams during registration:

Command	Description	Access
/tournament team create	Create a team and become the captain.	Participant
/tournament team join	Join an existing team.	Participant
/tournament team leave	Leave your current team.	Participant

Race Control & Protests

Race Control gives your league a structured protest system. Drivers file incidents, Race Control staff review them, and rulings are issued with a penalty — all tracked in a dedicated Discord thread per protest.

Setup

Configure Race Control in the iRacing tab on the dashboard or via /setup:

Race Control channel — where protest embeds are posted
Race Control role — members with this role can review and rule on protests. Falls back to anyone with Manage Guild permission.
Protest window — optional time limit (default 48 hours after the race)
DM filer on ruling — optionally notify the driver who filed when a ruling is issued

Filing a Protest

Any member can file a protest in the Race Control channel:

/protest file reason:[category]

After selecting a reason, a form opens for:

Lap number(s) — identifies when the incident occurred
Driver(s) involved — names or car numbers
Description — what happened (required)
Evidence — replay links or timestamps (optional)
Race / session reference — for window enforcement

Protest Category
Intentional Wrecking
Rough Driving
Retaliation
Blocking
Driver Ineptitude
Verbal Abuse
Other

Protest Workflow

Open

Protest is filed. A thread is created for evidence and discussion. Race Control is notified.

Reviewing

A Race Control member has picked up the protest. Filer and involved parties can be contacted via the thread.

Ruled

Race Control has issued a ruling with a penalty. Thread is archived.

Dismissed

Protest was reviewed and dismissed with no penalty. Thread is archived.

Withdrawn

The filer withdrew their protest before a ruling was issued.

Penalties

Race Control selects a penalty type when issuing a ruling:

Penalty	Description
Warning	Formal warning, no points or time impact.
Time Penalty	Seconds added to the driver's race time.
Grid Drop	Starting position drop for the next race.
Points Deduction	Championship points removed.
DQ	Disqualified from the race.
No Action	Protest reviewed, no penalty warranted.

Event Reminders

Schedule automated race announcements that fire at 24 hours before, at the start, and at the end of each event. Supports one-off and recurring schedules.

Events are created from the iRacing tab on the dashboard. Each event can be:

Linked to a championship for automatic context in the announcement
Set to ping a specific role when each reminder fires
Configured to recur on a daily / weekly / biweekly / monthly schedule

Use recurring weekly events for a fixed race night so you only set it up once and the bot handles every week automatically.

Dashboard iRacing Tab

The iRacing tab at dash.mavops.org consolidates all iRacing management in one place:

Create, view, and cancel championships
View live standings and round history
Configure Race Control channels, roles, and protest settings
Create and manage event reminders with recurrence

Commands Reference

Command	Description	Access
/tournament create (game:iracing)	Create a new iRacing championship.	Admin
/tournament start	Lock sign-ups and begin the season.	Admin
/tournament round	Record race results for a round. Attach a scoreboard screenshot for auto-parsing.	Admin
/tournament info	View championship details and current standings.	Anyone
/tournament list	List all championships in the server.	Anyone
/tournament cancel	Cancel a championship.	Admin
/tournament gamertag set (platform:iracing)	Save your iRacing screen name for result matching.	Anyone
/tournament gamertag view	View saved gamertags.	Anyone
/tournament team create	Create a team (team-mode championships).	Anyone
/tournament team join	Join an existing team.	Anyone
/tournament team leave	Leave your current team.	Anyone
/protest file	File an incident protest with Race Control.	Anyone