Use the menu above for detailed league information such as rules, concept, history and more.
Changes from to the TDoREL Ruleset moving into Season 9:
All changes to the ruleset are highlighted in yellow in their respective areas. Here is a brief breakdown of the changes from season 6.
~ Removing the Team Point/Individual Driver Point sections and merging them together. All points will be assigned per individual driver, regardless of the bonus/penalty. Team points are determined by highest driver's points total of the team. Exceptions are the 50%, minimum laps, and DQ modifiers. These will apply to all drivers of the team.
~ Led-a-Lap Bonus will now be able to provide more bonus points. Total # of drivers that have led laps in the event will dictate the highest # of points for the bonus, then the points will be distributed from highest # of led laps, down to least.
~ Battle for Lead Bonus will now provide more points to each driver for more vehicles finishing on the lead lap for their class. Instead of a flat 1 point for all, if there are 4 vehicles on the lead lap for their class crossing the finish line, then all 4 teams will get 4 points assigned to all drivers.
~ Removing the fastest AVERAGE Lap time for your class bonus, as this was generally always going to the class leader, thus giving the winner, even more points for winning. (Bonus for a Bonus situation.
~ Addition of Dynamic Surface Model Information into ruleset. ALL TDoREL Official Sessions will start with a 0% "Green" track, and have the rubber buildup and marbles carried over into the next portion of the individual session. "Scrubbing" or cleaning of marbles will *NOT* be used for our league in any event, either between session states, or during yellow flag pacing.
~ Grids will have all vehicles grouped by class, with qualifying only determining position in your individual class. Exceptions to this *MAY* be enforced for particular weeks if iRacing logic places vehicles that are considerably slower (+5sec/lap) ahead of the class directly behind. In those cases, the grid will be determined entirely by qualifying time only, irrespective of class.
~ Inclusion of incident DQ information for Mastiff Series (IE: None)
~ Various Safety and Conduct ruleset adjustments. (Please see respective section of rules)
~^**^~~^**^~~^*~~^**^~~^**^~
Points/Scoring rules for TDoREL Main Series (Keeshond/Ridgeback):
Basic points/class position as follows:
Teams will have their own individual point standings and safety rankings, much like we have had individual driver rankings in all previous seasons. Teams will be ranked only after their 3rd event.
Point modifiers applied after base points above have been applied:
- Consecutive Race Bonus +2
- 0-incident race=+1 point for Keeshond Series. +2 for Ridgeback Series
- Led-A-Lap bonus +1 point/driver for any team that led 1 or more laps (Points will be increased for total # of laps led)
- Battle for the Lead bonus +1 point/vehicle awarded to each driver from a vehicle finishing on the same lap as your class leader.
- Fastest AVERAGE lap time of event for each CLASS +1 point/driver (REMOVED FOR SEASON 9)
- Incident based variable bonus points system:
- 1 point subtracted for every 5X (cannot go below 0)
- 1 point added for every 2X less than overall event average incidents/driver
- Only incidents in race portion of event counted. Incidents from qualify are NOT counted.
Other Point Information: (In order of application)
- Any team completing less than 50% of overall winner laps will have final points halved for each driver in the team.
- Team must complete a minimum of 10 laps (or 10% of the event - whichever is larger) to qualify for any points or points for all members are void.
- ***Note, this will also affect the vehicle being counted towards our vehicle use rotation.
- All drivers will get points regardless of final race status, with exception of team not completing 10+ laps, or drivers not meeting your team's "Fair Share" quota.
- Any type of disqualification showing in the race results will result in -5 points for ALL DRIVERS IN THE TEAM, incurred after all other point modifiers.
# of point scoring weeks to be determined by average # of participated events/series from the top 25% of point scoring drivers.
- Once the number of drivers for average has been determined, the average number of events completed (rounded down) will be taken as the number of events counted.
- Top X event points (equal to above mentioned average events) will be counted
- Negative, or 0 balance races will be included unless more than average # of races have been completed for series
- Disconnected races will still count as a participation race
~ Teams will have their own individual points standings, for each series, as well as a combined season scoreboard. Each event's points will be determined by the average point total of all drivers who turned any laps during an event.
~ Individuals will also have their own individual points standings for each series, as well as a combined season scoreboard.
~ Team Safety will be combined into one overall safety ranking for all events during the season
~ Individual Safety rankings will be split into each seperate series. All events for the season will now be consolidated into one spreadsheet for the season
***OTHER***
Drivers AND Teams will be ranked based on league history for SAFETY. The safer the ranking, the safer that member or team's history has proven to be.
~ Drivers and teams will be ranked at the beginning of every season, with it being re-assessed every season based on your entire league history
~ Rankings *MAY* be re-assesed as much as once/week (time permitting) for promotion/demotion
~ All drivers and teams are free to use whatever number suits their fancy for their teams in our sessions
Rankings are as follows with Alien Class being the safest and Accident Prone possibly being removed from the league!
Alien Class (Average of 267+ CPI)
Inhuman class (Average 171-256 CPI)
Pro class (Average 114-170 CPI)
A class (Average 76-113 CPI)
B class (Average 50-75 CPI)
C class (Average 34-49 CPI)
D class (Average 23-33 CPI)
Rookie class (Average 15-22 CPI)
Accident Prone (Average of less than 14 CPI)
~ New drivers and New teams will be ranked in the same way, with rankings being calculated after participating in 3 or more events.
Only driver and team information from weekend main event races will be used for member statistic tracking. Qualifying portion will not be tracked. As well, all league practice events will NOT be tracked for member statistics. This *DOES* however mean that any laps/incidents showing up on the results screen in an official league event session even with a disconnect, or glitched server will apply to your overall rankings for membership (not series points)
Global Event Rules
- WEAVING DURING PACING IS DANGEROUS AND *MAY* RESULT IN BEING REMOVED FROM SERVER
- It has been proven that weaving or rapidly accelerating and slowing down gives a marginal at best result
- Holding both the brake and throttle for up to 15 seconds has been proven to heat tires more than other methods (Sometimes even higher than running temp)
- see here for more details: members.iracing.com/jforum/posts/list/3230240.page
- iRacing FIRST Sporting Code will be in effect for all events, practice included
- Realistic Weather will be in all races
- ALL TDoREL Official Sessions will start with a 0% "Green" track, and have the rubber buildup and marbles carried over into the next portion of the individual session. "Scrubbing" or cleaning of marbles will *NOT* be used for our league in any event, either between session states, or during yellow flag pacing.
- If there is a night option for a track, that will be utilized before day configurations
- US Server Farm will be used in all events
- League exclusive, 4-way multi-class vehicle rotation will be in affect for all main series (Week 13 & Special Series Events Exempt)
- Open setup (Please feel free to share setups!)
- 100% fuel for all series.
- All events will have an open qualifier with all classes on track together
- Rolling starts for all events regardless of length of pace lap (*Exception: If 50% or more of the weekday practices fail to go green clean it will be switched to standing)
- Grids will have all vehicles grouped by class, with qualifying only determining position in your individual class. Exceptions to this *MAY* be enforced for particular weeks if iRacing logic places vehicles that are considerably slower (+5sec/lap) ahead of the class directly behind. In those cases, the grid will be determined entirely by qualifying time only, irrespective of class.
- All events will have ZERO fast tows or repairs.
- Full course cautions MAY occur in any event, dependent on iRacing Automation
- Lucky Dog will be enabled
- Double-File - Lapped at Back
- Weight Penalty of X.x KG to be added to every vehicle that stays in for another week, where X = the average usage from the current and previous week.
- Incident disqualification rules:
- Set for each event based on average lap-times of all vehicles compared against corners/lap for specific venue
- Each type of event will have their own disqualification safety requirements
- All practice events will be set to Rookie 3.0 SR
- Keeshond Series (1.5 hour) will be set to Class D 3.0 SR
- Ridgeback Series (3.5 hour) will be set to Class C 3.0 SR
- Mastiff Series (2 hour) will *NOT* have an incident DQ set for either practices or main events.
Safety and Conduct issues:
- FULL COURSE CAUTIONS
- A full-course caution may be called at any venue by method of driver request
- Drivers may request a full course caution at anytime they feel one may be warranted due to SAFETY REASONS. Administration will require a minimum of 3 independant drivers saying "Yellow" or "Caution" before it shall be called.
- Drivers simply wanting a "Break" should not use this feature. These manually called cautions should only be used in the event that iRacing automation does not call a yellow automatically in error, or if there are multiple vehicles involved and could potentially cause more incidents if a caution has not been called.
- Competition Cautions should *NEVER* be called in any event for any reason other than iRacing automation, or the above mentioned method.
- BLUE FLAG RULES:
- AS PER iRACING F.I.R.S.T. Code of Conduct, Blue flag is INFORMATIONAL ONLY. Drivers do not HAVE to move over. It is helpful to facilitate a pass though
- It is ALWAYS the faster vehicles responsibility to perform a clean pass. Unless you are already past a vehicle, then as long as they are maintaining a consistent racing line, it is the vehicle that is being passed that has right-of-way, regardless of if you are already side-by-side with that vehicle. The vehicle being passed has the right to continue following their regular racing line, and do *NOT* have to come off of that line for any reason. This includes tracking out, post-apex.
- When getting a blue flag, it is encouraged to communicate when/where you are expecting to be passed when feasible
- Drivers coming up on lap down vehicles are suggested to communicate their passing intentions in advance if possible
- Drivers expressing displeasure for a slower vehicle not moving out of their way may be subject to a stop-and-go black flag penalty. Please refer 3 lines above.
- Slower vehicles NOT maintaining a consistant and predictable line to facilitate faster vehicles passing (IE Blocking, or unexpectedly changing direction) may also be subject to a stop-and-go black flag
- Reckless driving, including driving backwards, driving alternate routes or blocking the flow of traffic on the race surface during *ANY* official session may result immediate disqualification from event. This includes our official practice sessions!
- If a driver is confirmed to be the cause of a multi-vehicle incident (3 or more vehicles), or the cause of grief due to to lack of respect for other drivers on the track, the driver may be served a black flag for a duration deemed appropriate at that time by the administration.
- Black Flags, regardless of how aquired will NEVER be cleared in any session by administration.
- Misuse of in-game chat (EG whining and complaining about an incident, or anything else that negatively affects multiple drivers) will result in an immediate revocation of chat priviledges for the remainder of the event. Like black flags, this will not be cleared.
- Misuse of TeamSpeak server in the same manner will result in a kick from the active channel as a warning. Second offense will be a ban from the server for 1 hour. Third offense will result in a permanant ban from the teamspeak server.
***If you have a particular issue with a certain member regarding a FIRST matter, feel free to file a protest via the official iRacing protest form.***
This is a detailed breakdown of our current ruleset.
