2025 MNRL Club Series
A1GP
MNRL’s next Club Series brings life back into the A1GP on a globe-trotting tour.
Welcome, racing enthusiasts and history-makers, to a legendary re-creation of motorsport history! Today, we step back in time to experience the open-wheeled wonders of the F3000’s.
There will be a single, 20-minute sprint race followed by a 40-minute feature race, broadcasted on the Champion Motorsports YouTube. A 10 minutes Qualifying session will determine the Sprint Race order while the Sprint Race results will set the grid for the feature.
Cars
MNRL will use the F3000 ITO mod by Luthien. The template and additional links are available in the Champion Motorsports (CMS) Discord.
Calendar
Google Calendar – MNRL Tuesday
Event Schedule
(note times may vary during Daylight Saving Time – See the Discord for details)
19:30 US ET – Server Reboot/Practice
20:55 US ET – Drivers’ briefing
21:00 US ET – Qualifying
21:15 US ET – Warmup
21:20 US ET – Sprint Race (Rolling Start – SOFT or HARD Tires)
21:50 US ET – Feature Race (Standing Start – No Formation – HARD Tires REQUIRED)
All drivers are expected to have completed the following:
- Read the CMS General Competition Rules (available on CMS Discord)
- Read the series & race briefings (this page and on CMS Discord)
- Install the required mods
- Join the server and confirm connection is working properly
- Practice adequately to ensure competent control of the car
Championships & Driver Classes
The rf2la app (password: cmsrocks) will record all sessions and standings. There are no separate driver classes for this championship.
Points
Sprint: 10-9-8-7-6-5-4-3-2-1 (for all other eligible finishers)
Feature: 20-18-16-14-12-10-8-6-4-2 (for all other eligible finishers)
Bonus Points
None
NOTE: Drivers must take the checkered flag to be eligible for points. There will be 4 drop events (worst combined results from a track) for the season. Only the top 10 events will count towards the season total.
Settings
Build: Latest stable build of rFactor 2
Damage: 50%
Mechanical Failures: Normal
Crash Recovery: OFF
Driving View: Open
Aids: Auto Clutch, Blip, Lift are the only rF2 global aids available
Fuel: 1x (noted in driver briefings)
Weather: Live
Flags: All (local yellows=no passing – no FCY)
Race Start: Formation Lap + Rolling Start for Sprint / Cold Standing for Feature. Drivers are required to maintain safety during the formation lap and be predictable. The formation lap may be considered part of the Orange Zone when assessing incidents. See race briefs for details.
Orange Zone (OZ)
There will be an OZ designated for each race in the driver notes that will be posted to the race brief and noted again in the pre-race driver’s brief. The OZ is a portion of the track that is active during the first lap. Any incidents that occur in this zone are subject to harsher penalties.
Custom Liveries
CMS standard (default) liveries are provided and drivers are encouraged to paint their own custom liveries. Templates are included with the mod. Liveries not containing required elements or containing inappropriate materials will be rejected and drivers may be subject to penalties and/or disciplinary actions. Contact the series admin with questions or concerns. All custom liveries will be applied as loose skins.
Competition Rules and Stewarding
This series will conform to the CMS General Competition Rules that may be found on the CMS Discord Server and here on the website All drivers are expected to know the GCRs and shall be required to abide by them. Additional, event-specific instructions will be provided via a drivers pre-race brief posted in the CMS Discord and reviewed with drivers verbally by the director prior to the race session.
Pit Entry/Exit Lines: Pit road entry or/and exit with white lane lines may not be crossed when cars utilizing pit road are present unless specifically permitted in a pre-race brief. Otherwise, it is permissible for tires to step on the white line, but crossing the line with one tire completely will result in a post-race Incident Review Request and penalty.
There are no live stewards. A post-race Incident Review Request may be submitted via the RRC Discord for adjudication with any resultant penalties to be served in the next race competed by the driver(s) at fault.
rFactor 2 system-assigned penalties during qualification and race sessions must be served. The Race Director will only clear penalties/DQ during practice/warm-up.
Connection Notes
Drivers are strongly advised to reboot their computer just before joining the server on race day. Drivers must also maintain a reasonable connection and appropriate ping rate which does not impact race conditions or else they may be asked to leave the server.
Race Communications
We will use the CMS Discord MNRL voice channel for race communications. Drivers will receive 3 notifications before being removed by race control during events. Drivers may return to the server once they have joined voice.
The voice channel is only required to monitor race control during the event. You do not need a microphone if you do not want to speak. If you have a microphone, please use “push to talk” or set voice activation properly to avoid disruptive background noises. Don’t be “that driver”.
Conversation during practice and warm up is encouraged. For qualification and race, only brief communication for session-critical information (eg “car stopped in turn 1”). One sentence then quiet is requested. NO TEXT CHAT ALLOWED during qualification & race. This is reserved for ADMIN USE ONLY.
Abusive and/or profane language in any form or channel may lead to that driver receiving a sanction up to and including a ban from CMS.
See you on track!
