GT3 GT3 Season XV pc

Apex Online Racing

League Information

Signups closed
Signup:
21.01.2024 - 11.02.2024
Season period:
19.02.2024 - 09.04.2024
Evaluation races:
29.01.2024 19:30 UTC
30.01.2024 19:30 UTC
04.02.2024 19:30 UTC
05.02.2024 19:30 UTC
12.02.2024 19:30 UTC
13.02.2024 19:30 UTC

General Information:

  • League structure: A set amount of tiers will be created, depending on the amount of drivers signing up at the start of the season. The faster drivers will be in the higher tiers and the slower drivers in the lower tiers.
    Only drivers who completed ALL steps of the signup process will be placed. That means a valid hotstint and passed evaluation is needed.
  • Regions: Assetto Corsa Competizione leagues currently only have European starting times. Drivers from all around the world are allowed to take part in the leagues, as long as their connection is suitable enough towards Europe.
  • Hotstint: All drivers will need to complete both hotstints.
  • Evaluation races: Drivers new to AOR ACC leagues will need to complete and pass one of our evaluation races. Before the season a set amount of evaluation races are scheduled for the new drivers. Signing up for one of the evaluation races before the season, can be done on the sign up page. During the season, new drivers who signed up mid-season can use one of the practice races as their evaluation race. The main goal of the evaluation races is to give new drivers the chance to show the coordinators they can race in a safe, clean and fair manner. During evaluation races, safety is more important than race pace. 
  • Assists: All tiers will have the maximum stability control setting to zero and auto-steer disabled. Other than the ones mentioned here, all assists are allowed to be used. Ideal racing line will be disabled on the servers of the top three tiers.
  • Driver placements: Drivers will be placed in an appropriate tier based on their hotstint time, their performances in the evaluation race, and their performance in the previous league seasons. Drivers who missed a significant number of races in previous seasons may be placed as reserves.
  • Race format: Each race event features a 15-minute qualifying session followed by a 60 or 90 minute race.
  • Day/time: League events for all tiers but the top tier, will take place on Tuesday nights from 7:30pm (UK time). The top tier will race on Monday nights from 7:30pm (UK time).
Time stated is start of Qualifying. Servers will be online one hour earlier with a practice session.

20.02.2024 19:30 UTC ES Barcelona
Tier 1: 19.02.2024

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
100% dry
0% wet
0% changing conditions
Server Json
{ "track": "barcelona", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 20, "cloudLevel": 0.4, "rain": 0, "weatherRandomness": 1, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 18, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 17, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 18, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Practice Races ES Barcelona Fastest practice times
17.02.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Barcelona #AORPR Results
17.02.2024 19:30 UTC #12 | Season XV - Practice Race Server 2 - Barcelona #AORPR Results
18.02.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Barcelona #AORPR Results
18.02.2024 19:30 UTC #12 | Season XV - Practice Race Server 2 - Barcelona #AORPR Results
19.02.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Barcelona #AORPR Results
19.02.2024 19:30 UTC #12 | Season XV - Practice Race Server 2 - Barcelona #AORPR Results

27.02.2024 19:30 UTC US Indianapolis Motor Speedway
Tier 1: 26.02.2024

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
0% dry
100% wet
0% changing conditions
Server Json
{ "track": "indianapolis", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 20, "cloudLevel": 0.25, "rain": 0.35, "weatherRandomness": 0, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 16, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 15, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 16, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Practice Races US Indianapolis Motor Speedway Fastest practice times
25.02.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Indianapolis #AORPR Results
25.02.2024 19:30 UTC #12 | Season XV - Practice Race Server 1 - Indianapolis #AORPR Results
26.02.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Indianapolis #AORPR Results
26.02.2024 19:30 UTC #12 | Season XV - Practice Race Server 1 - Indianapolis #AORPR Results

05.03.2024 19:30 UTC US Watkins Glen
Tier 1: 04.03.2024

Results
Race info
Race length: 90 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: No
Mandatory refueling: No
Refueling allowed: Yes
Weather forecast
24% dry
25% wet
51% changing conditions
Server Json
{ "track": "watkins_glen", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 25, "cloudLevel": 0.3, "rain": 0.3, "weatherRandomness": 3, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 10, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 90 }, { "hourOfDay": 9, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 10, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 90 } ], "configVersion": 1 }
Practice Races US Watkins Glen Fastest practice times
03.03.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Watkins Glen #AORPR Results
03.03.2024 19:30 UTC #12 | Season XV - Practice Race Server 1 - Watkins Glen #AORPR Results
04.03.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Watkins Glen #AORPR Results
04.03.2024 19:30 UTC #12 | Season XV - Practice Race Server 1 - Watkins Glen #AORPR Results

12.03.2024 19:30 UTC GB Brands Hatch
Tier 1: 11.03.2024

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
100% dry
0% wet
0% changing conditions
Server Json
{ "track": "brands_hatch", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 13, "cloudLevel": 0.15, "rain": 0.05, "weatherRandomness": 3, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 12, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 13, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 12, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Practice Races GB Brands Hatch Fastest practice times
10.03.2024 19:30 UTC Practice Race Server 1 Results
10.03.2024 19:30 UTC Practice Race Server 2 Results
11.03.2024 19:30 UTC #11 | Season XV - Practice Race Server 1 - Brands Hatch #AORPR Results
11.03.2024 19:30 UTC #12 | Season XV - Practice Race Server 2 - Brands Hatch #AORPR Results

19.03.2024 19:30 UTC FR Paul Ricard
Tier 1: 18.03.2024

Results
Race info
Race length: 90 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: No
Mandatory refueling: No
Refueling allowed: Yes
Weather forecast
42% dry
22% wet
36% changing conditions
Server Json
{ "track": "paul_ricard", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 16, "cloudLevel": 0.25, "rain": 0.3, "weatherRandomness": 4, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 19, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 19, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 19, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 90 } ], "configVersion": 1 }
Practice Races FR Paul Ricard Fastest practice times
15.03.2024 19:30 UTC Results
15.03.2024 19:30 UTC Results
17.03.2024 19:30 UTC Results
17.03.2024 19:30 UTC Results
18.03.2024 19:30 UTC Results
18.03.2024 19:30 UTC Results

26.03.2024 19:30 UTC JP Suzuka
Tier 1: 25.03.2024

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
94% dry
1% wet
5% changing conditions
Server Json
{ "track": "suzuka", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 20, "cloudLevel": 0.05, "rain": 0.1, "weatherRandomness": 5, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 14, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 15, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 14, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Practice Races JP Suzuka Fastest practice times
24.03.2024 19:30 UTC Results
24.03.2024 19:30 UTC Results
25.03.2024 19:30 UTC Results
25.03.2024 19:30 UTC Results

09.04.2024 18:30 UTC BE Spa
Tier 1: 08.04.2024

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
77% dry
4% wet
19% changing conditions
Server Json
{ "track": "spa", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 35, "cloudLevel": 0.25, "rain": 0.15, "weatherRandomness": 4, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 8, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 9, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 8, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Practice Races BE Spa Fastest practice times
31.03.2024 18:30 UTC Results
07.04.2024 18:30 UTC Results
08.04.2024 18:30 UTC Results
08.04.2024 18:30 UTC Results
  • 1.1 Patreon

    • AOR ACC is on Patreon!
      In the past we used a PayPal moneypool to give you the possibility to support us with the server costs on both the PC and PS side of things. Since PayPal decided to shut down the moneypool functionality and service, we started looking for a place where not only you could show your support - but also a place where we could give you something in return. That's why we decided to join Patreon. You can now become a supporter (also known as subscribing) and pick one of the four available tiers. Based on which tier you pick you get something in return. Examples: a supporter role in Discord, polls for future events and leagues To find out more about our Patreon page or to subscribe, please click HERE

  • 1.2 Changes in Season XV
    • 1.2.1

      For Season XV we will continue using a custom balance of performance. The custom balance of performance is an effort of LowFuelMotorsport and Apex Online Racing to level the playing field for the most used cars, based on reliable data. For the cars not included in the balance of performance, the available data was not reliable enough.
      The balance of performance has been applied to all ApexOnlineRacing servers with Season XV mentioned in the servername. 
      The balance of performance for a certain track can be requested in the #gt3_bop_bot channel in the Apex Online Racing Discord server.

    • 1.2.2

      A minor change has been made to the being lapped rule, more specifically the bit about lapping a car which already completed their pitstop. Drivers should announce their attempt to overtake, by clearly going towards the inside or flashing their lights shortly.

    • 1.2.3

      In the previous season, warnings were given to drivers but without any further consequences. This made warnings very similar to the no further action verdicts. For the new season every second warning a driver receives, automatically results in 1 license point.

    • 1.2.4

      At the end of the previous season, we reviewed the positions of all drivers who accumulated eight or more license points. This has for the current and likely future seasons, been reduced to six license points.

    • 1.2.5

      We have made changes to the rule about drivers changing the car they drive in. From now on, drivers are no longer allowed to change their car after the fourth race of the season. Drivers who joined mid-season, can only change their car between the first and second race after they joined, but not between the final two races of the season.

    • 1.2.6

      For the Season XV hotstints, the balance of performance of January 21st is in place. This will not be updated during the (pre-)season. 

  • 1.3 Tier Structure

    • The leagues on each platform (within each region) are organised in a tier structure.

    • 1.3.1

      It is possible for new and returning drivers to sign up while the season is ongoing. This will be possible between round 2 and round 6 of the season. They will still have to complete the steps on the sign-up website (sign up, hotstint and evaluation race). Then there are three possibilities:

      1. There is space in the tier closest to the driver's race pace. The driver will be placed in the tier as main driver.
      2. There is no space in the tier closest to the driver's race pace, but the tier does not have enough reserve drivers yet. The driver will be placed in the tier as a reserve driver.
      3. There is no space in the tier as main or reserve driver. The driver will be put on the waiting list. A coordinator will contact you once there is space (again).

    • 1.3.2

      Drivers who are assigned to a tier as a reserve driver will not have a guaranteed spot in the league races, but will be able to step in to race in place of any no-showers. Reserve drivers are required to pick a car when they sign up. Reserve drivers will be visibly listed in their tier's championship standings. Points scored during the reserve driver period will stay when the driver becomes a regular driver.

      Unlike main drivers, reserve drivers are not required to be online at the time of the races, but this is obviously appreciated. Reserve drivers will be contacted by their coordinator, when there is a free seat for a race. Reserve drivers who are inactive for a lengthy period of time (e.g. frequently not being available to fill no-show spot despite such spots being available) may be removed from the league.

      If a main driver spot opens up within a league during the season, that league's most active reserve driver will be first in line to fill that spot. In case there are multiple active reserves, the reserve who signed up earliest will be allowed to fill the empty spot.

    • 1.3.3

      Drivers may be moved between tiers while the season is ongoing if it's clear they have been misplaced. The coordinators team is free to move drivers to a higher/lower tier. This could be because they are clearly too fast for their split, or that they are unable to experience close racing due to being too slow. Moving drivers will only be done when it improves the competitiveness of all tiers involved.

      Preferably we want to avoid having to move drivers between leagues against their will, but in extreme situations this can be a necessity to keep the tiers competitive or sufficiently filled up. The league coordinators reserve the right to move drivers up to a higher (or lower) tier, if this is deemed to be in the best interest of a tier, to avoid drivers from excessively dominating.

    • 1.3.4

      Drivers are allowed to change the car they drive, but they may only do so just once during the season and latest before the fourth race of the season. Drivers who joined mid-season, can only change their car in-between the first and second race after they joined - but not before the last race of the season. Changing car automatically means your championship points will be reset to zero.

    • 1.3.5

      When setting up the tiers for a new season, we always aim to make the tiers as close and competitive as possible, by placing drivers where they best fit into the league structure.
      The leagues have no fixed promotion & relegation spots, due to the drivers taking part usually changing drastically from season to season, and due to wanting to incorporate new drivers in a competitive league straight away. This means it's up to the league coordinators to make a determination on where drivers should be placed, with the intention to make each tier as competitive as possible.
      All drivers will be placed in a suitable tier based on various factors; the hotstint event held as part of the sign-up process, performance in the evaluation race, and to some extent performances in the previous league seasons (for drivers who raced in previous seasons).
      Each tier will allow between 30 and 50 drivers, with the exact amount of main and reserve drivers being decided by the coordinator of the tier.

      Note: Drivers who missed a significant number of races in previous seasons may be placed as a reserve driver.

  • 1.4 Race Classification
    • 1.4.1

      The following points will be scored for each race finishing position.

      1st = 100 points
      2nd = 88 points
      3rd = 79 points
      4th = 72 points
      5th = 65 points
      6th = 59 points
      7th = 53 points
      8th = 48 points
      9th = 43 points
      10th = 39 points
      11th = 35 points
      12th = 31 points
      13th = 28 points
      14th = 25 points
      15th = 22 points
      16th = 20 points
      17th = 18 points
      18th = 16 points
      19th = 14 points
      20th = 12 points
      21st = 10 points
      22nd = 9 points
      23rd = 8 points
      24th = 7 points
      25th = 6 points
      26th = 5 points
      27th = 4 points
      28th = 3 points
      29th = 2 points
      30th = 1 points

    • 1.4.2

      Drivers who get disconnected from the server, due to a connection issue, need to have completed 70% of the race in order to be classified.

    • 1.4.3

      Drivers who complete less than 70% of the race distance will be classified as DNF (Did Not Finish) in the race results and will score 0 points regardless of their final position.

    • 1.4.4

      Drivers who get disqualified from a race - whether that be due to an in-game penalty or post-race disqualification via the stewards panel - will be classified as a DSQ (Disqualified) and moved below all other drivers in the results. A DSQ due to an in-game penalty can be appealed via the stewards panel.

      If a driver is classified as DSQ within a points scoring position, they will score 0 points for that position regardless of race distance completed.

    • 1.4.5

      Active league drivers who did not attend the race will be classified as DNS (Did Not Start), and will not score any points.

    • 1.4.6

      Drivers and teams are ranked in the standings based on how many points they've scored over the course of the season. If two or more drivers or teams are tied on points, the higher place in the standings will be awarded to the holder of the most first places. If the number of first places is the same, the holder of the most second places, then third places and so on until a winner emerges.

      At the end of the season, results of all races count.

  • 1.5 Disconnection Guidelines
    • 1.5.1

      ACC has the ability to let you rejoin the session at any time. We encourage to rejoin the session so that you still score points for the championship.

    • 1.5.2

      During a qualifying session or the race, if half (or more) of the drivers in a race lose connection at the same time, or over a short period of time, that counts as a mass disconnection.
      - If less than 50% of the race was completed at the time of the mass disconnection, the race will be restarted as soon as possible.
      - If more than 50% of the race was completed at the time of the mass disconnection, the race will end, and the race will be postponed.
      - If a mass disconnection happens during a qualifying session, the session will be restarted.

    • 1.5.3

      Unfortunately, sometimes the technology that allows us to go racing, turns against us. This means we may have to post-pone or cancel a race. If we do so, it's because we feel it's the fairest option for everyone.
      If a race is postponed or cancelled, the round in question will take place in the break week or after the season normally would have ended. This is to keep the rest of the calendar in sync for social media promotion and any interim leagues we run.

      Reasons we may postpone or cancel a race include:
      - Lobby/Connection issues: If drivers are continuously getting dropped and there is no way of keeping everyone in the lobby, then we may postpone the race rather than having a very small grid.
      - Mass Disconnection: See above.

  • 1.6 Who to contact

    • For league related enquiries or questions, your first point of contact should be the Discord channel #gt3_support.

      If you are unhappy about something, either with regards to a race, an individual participant or the league - feel free to contact one of the ACC coordinators.

      If you have an issue with a coordinator and would like to discuss the issue with someone, then seek out another person from the ACC Coordinator list on Discord and address the issue to them. Our coordinators and moderators are expected to remain completely unbiased, and as long as you address the situation sensibly and maturely they will be happy to discuss any issues no matter who it is with.

  • 1.7 Skin pack

    • A custom skin pack will be created by the coordinating team. This will allow you to share your custom livery with the other drivers participating in this championship.
      When submitting a skin to the AOR ACC Skin Pack, it is your responsibility that the skin is inline with recommendations according to the guidelines below. Read them all carefully, getting it right the first time saves a lot of time.

      ● Templates HERE

      AOR ACC Skin Pack guidelines:
      ● Files to provide:

      - From the \acc\customs\cars folder, the .json file for the livery
      - From \acc\customs\liveries folder:
      decals.png + decals_1.dds + decals.json
      OR
      sponsors.png + sponsors_1.dds + sponsors.json
      OR
      decals.png + decals_1.dds + decals.json + sponsors.png + sponsors_1.dds + sponsors.json

      Additional skinpack info for game version 1.8+
      The _1.dds file must be created by driving the car, not from renaming the showroom file (_0.dds).

      ● “skinTemplateKey”: 99 is NOT allowed.
      ● Each png file must not exceed 5MB
      ● It is forbidden to feature vulgar, obscene, suggestive language or imagery or anything that might go against public taste or may be taken as offensive by either the participants, organizers, or the general public.
      ● Submit your livery as any archive file type, however .zip .7z and .rar are recommended.
      ● By submitting a skin you accept that others have access to the skin(s).

      Custom skins can be uploaded on the signup page here

      Season XV skin pack submission deadline is 17.02.2024 at 22:00 UTC

      (Any submissions after this time are not guaranteed to be included in the pack).


      1 Installation instructions:
      1. Download the file from the link below.
      2. Extract its contents into the folder:
      C:\Users\*yourusername*\Documents\Assetto Corsa Competizione\
      3. Accept any file replacements.

      Note: For others to see your custom livery you must use the version from the skin pack.

  • 2.1 Clean racing
    • 2.1.1
      Race cleanly at all times. No contact should occur between cars on track, and as a driver you are required to do your best to avoid this from happening. Accidents can happen, but if you are at fault for causing a collision, you are likely to be penalised.
    • 2.1.2
      Deliberately crashing into another car will result in a 6-month ban from our ACC leagues, events and servers. Repeat offenders will be permanently excluded.
    • 2.1.3
      If lag (connection issues) is the cause of an incident, when it is obvious that your car's lag is the cause of another driver going off, this would still be classed as an unfair overtake. Please be more careful around other drivers if you are regularly involved in lag-related incidents.
  • 2.2 Overtaking
    • 2.2.1
      Don't be too aggressive when trying to overtake. As the chasing car, it is generally your responsibility to not make contact with the car in front.
    • 2.2.2
      Overtaking another car on the track, when under yellow flags, is prohibited/not allowed. An exception to this rule is in place, when the other car drives very slow due to damage and/or was involved in the incident causing the yellow flags. When a driver overtakes another car under yellow flags, they are supposed to return the position. This rule only applies during race sessions.
  • 2.3 Defending
    • 2.3.1
      Dangerous weaving and blocking is not allowed. Do not force a chasing car off the track or into a situation where they are forced to go off the throttle or on the brakes. If the attacking car is alongside you going into a corner (generally if the attacking car's front wheels is alongside or ahead of the defending car's rear wheels), you must adjust your line to avoid contact.
    • 2.3.2
      Do not leave it too late to defend a move. Make your move clearly and fairly. If you move too late and the car behind has no time to react, it is not them who will be blamed.
  • 2.4 Corner cutting/track extending
    • 2.4.1
      Stay within the track boundaries with at least two tyres at all times. The track boundaries are in general defined in-game. Cutting corners, or extending the track, to gain an advantage even when the game does allow it, is a punishable offense.  Drivers found to be persistently breaking this rule will be penalised retrospectively.
    • 2.4.2
      If you overtake another driver with all four wheels off track, or as a consequence of cutting a corner, you must slow down and give the position back. Failing to do so will likely result in a penalty.
    • 2.4.3
      The odd misjudgement of a corner can happen, but if you accidentally gain an advantage by going outside the track limits without getting a warning by the game, you are expected to back off to an extent that clearly negates any advantage gained. Failing to do so may result in an enquiry being opened for the stewards to review.
    • 2.4.4
      If a driver is reported to the stewards for a breach of this rule, it is up to the stewards' discretion as to whether they feel the driver has abused the track limits to an extent where a penalty is justified, and if so what type of penalty is appropriate to be handed out. This will depend on the severity and frequency of the cuts. The bottom line is, if you want to make sure you are not in danger of being awarded a stewards penalty, make sure you don't gain time from leaving the track limits throughout qualifying and the race.
  • 2.5 Qualifying etiquette
    • 2.5.1

      You are to use the entire out lap to build a gap managing pace to ensure no build up of cars is forming behind due to excessive slowing. It is not allowed to sit on the car aheads' bumper for the entire out lap to then create a gap in the final sector, due to the cars behind building gaps.

    • 2.5.2

      Overtaking is not permitted during qualifying while the cars involved are on a hotlap, with the exceptions of the car in front leaving the track completely, crashing or yielding. Should you wish to allow a car to overtake in this session, you must actively move from the racing line and yield in a safe and controlled manner.

    • 2.5.3
      In qualifying, it is your own responsibility to find free space on the track when starting a hot lap. A car on a hot lap does not have to yield for a faster car approaching from behind. If you are on an in or out lap, however, you have to let cars on a hot lap pass you without blocking them. If you are on a hot lap approaching a car not on a hot lap, flashing your lights is a way of notifying them that you're on a fast lap.
  • 2.6 Spatial Awareness
    • 2.6.1
      If you spin off whilst the pack is close, rejoining the track immediately is ill-advised. You do not ghost and you will cause accidents. Staying still is the best option until the other cars have avoided you. It is far easier to avoid a stationary obstacle. If you spin off whilst one or more competitors are close, you have to prioritize safety over minimal time loss, which might include braking until the control of the car is regained. Failing to do so may result in a penalty.
    • 2.6.2
      If you for whatever reason leave the track, rejoin in a manner that is predictable, safe and in no way a danger to other competitors. Realign your car with the direction of the track as much as possible before rejoining the track.
    • 2.6.3
      Using the in-game spotter, an external app like the crew chief or at least having the proximity arrows enabled is strongly advised. This helps the drivers to be aware of their surroundings.
    • 2.6.4
      In case of yellow flags and/or an incident happening in front of you, you have the obligation to slow down by going off-throttle if the situation is safe enough or by braking to avoid any collisions. Failing to do so may result in a penalty even if you're not responsible for the incident in front of you. This rule only applies during race sessions.
    • 2.6.5

      In case you get spun by another driver or spin on your own close to other cars, you are expected to hit the brakes. If you get spun and hit the brakes within an acceptable time, you are protected from penalties derived by further collisions. If you do not hit the brakes within an acceptable time and get collected by other cars you will likely be penalized.

  • 2.7 Pit exit and pit entry
    • 2.7.1
      Cars on a qualifying hot lap have the right of way, cars that reset to the pit during qualifying must let the hot lap cars through before entering the track. During the race, cars exiting the pits have the right of way and must be allowed to exit back onto the track. During the race, do not cut off the pit exit when a car is leaving the pit lane.
    • 2.7.2
      Every track has a pit entry and a pit exit lane designated by a solid white line. If there is a car within these boundaries, either entering or exiting the pits, passing cars are not to cross the lines and move out of the way of the car entering or exiting the pit lane. This is especially important on tracks whose pit exits intersect with the racing line - Paul Ricard and Spa, as an example. Should any incidents occur while a car is in the pit entry or pit exit line, the passing car will be held responsible.
    • 2.7.3
      A car is considered to be in the pit exit or entry zone when all four wheels are within the white lines.
    • 2.7.4
      Once the car has left the pit exit boundaries, it is no longer under "protection", and as such is considered to have rejoined the race. Any incidents that will happen beyond the pit exit line will be no longer considered in favour of the car leaving the pits.
    • 2.7.5
      Use of turn indicators is strongly encouraged to signal entering the pit, especially on tracks which have a very tight pit lane entry starting right after the final corner of the track (Paul Ricard, Monza, Suzuka, Zolder are examples of this).
    • 2.7.6

      Stay within the white line when entering and exiting the pit lane. The game allows a small tolerance in speed limits while travelling in the pits. You are not allowed to exploit that tolerance while driving in the pit lane. We let the game enforce speed limits and penalties - within its tolerance - while cars are crossing the pit entry line and are still significantly slowing down, but once the car is slowed down the pit limiter speed must be observed. Failing to do so is a reportable offense which will lead to penalties. Pit entry speeding limits and penalties are at the same time, in the more extreme cases, enforced by the game and may lead to non-reversible penalties. If you cause a dangerous situation by crossing the pit entrance or exit line, or if this is done in a way that blatantly gains time or track position, you will be penalised. Taking out the pit-limiter marker is a punishable offense.

  • 3.1 Being lapped
    • 3.1.1
      We are running with the in-game rules & flags system, which means that the game should alert you with a blue flag when you are about to be lapped. When receiving a blue flag or know that a car is going to lap you and is approaching from behind, you should prepare to let them pass, without interfering with their race, when safe, within the next few corners. In single class races, this is done best by the car that is being shown a blue flag moving off the racing line and easing on the accelerator on a straight, or lifting / braking early, and/or giving up the inside line to a corner to let the lapping car pass. The exception to this rule applies when the car being lapped has completed their mandatory pit stop, and the car approaching to lap them has not yet completed their stop. In this, and only this, situation the car being shown the blue flag has no requirement to move out of the lapping cars way, and may stick to the racing line until the lapping car attempts a pass. However, when the lapping car goes for a move, the blue flagged car should not defend in any way. The lapping car should announce their attempt of overtaking by clearly moving towards the inside of the upcoming turn and/or shortly flashing their headlights.
    • 3.1.2
      As a means of helping with blue flags, we advise the leaders to flash their lights at cars due to be lapped. This should not be done excessively. This is their cue to inform that the driver on the lead lap is about to go for a move on the driver being lapped. Flashing your lights at a competitor you are racing for position is not to be used as a "distraction technique" or in anger at an incident.
    • 3.1.3
      If you are faster than a car that has lapped you already, you are allowed to try and unlap yourself. Immediately after unlapping yourself, you are allowed to try to build a gap to the car behind giving you blue flags. If you don't manage to do so within one lap, and are still receiving blue flags, you must adhere to them as per rule 2.1.1.
  • 3.2 Pit stops
    • 3.2.1
      A pit stop with tire change is mandatory in every 60 minutes race, refueling will not be allowed. Every driver will have the ability to make their own choice on when to pit similar to the in-game Competition Races. A pit stop is mandatory in every 90 minutes race, but changing tires and/or adding fuel are not requirements.
    • 3.2.2
      A pit stop must be served after the official widget start and earliest at the end of lap 1. A pit stop must also be served before the final lap of a race. This takes into account the potential for having been lapped. Failing to observe this rule will cause a race DSQ.
  • 3.3 Driving in different conditions
    • 3.3.1
      For races that take place at night time, all drivers are required to have their headlights on in order to make your car visible to others, and to make the road more visible for you. If you're involved in an accident which damages both of your headlights, you must return to the pits immediately for repairs. Please also make sure you have a button assigned to turn the headlights on.
    • 3.3.2
      The above rule about having headlights on also applies to running in the fog and in the rain.
    • 3.3.3
      During rainy conditions, having the rain lights turned on is mandatory.
    • 3.3.4
      For races with rain or a chance of rain, please make sure you have a button assigned to turn the wipers on, or have the auto-wipers feature turned on.
  • 3.4 Return to pit box
    • If at any point in qualifying you want to return to the pit box, please do this off-track or manually drive to the pits safely.
  • 3.5 In-Game Disqualification
    • If you are disqualified from the race in-game and you feel it's unfair, submit your full race replay to the stewards. If we feel that the disqualification was justified, it will remain. However if we feel that the disqualification was unfair, or a result of a game glitch, then you will be classified as the last finisher and score full points for that position. In case you get disqualified when coming across the finish-line, you can be put back to your original finishing position.
  • 3.6 Formation lap/start
    • Drivers are at all times supposed to strictly follow the instructions given by the in-game widget. Drive through penalties awarded by the game will not be reverted. An exception to this is during live-stewarding. There the drive through penalties will first be removed, then reviewed and possibly reinstated. Long formation lap is being used in our league races.
  • 3.7 Restarts
    • 3.7.1
      In case of a major incident involving a massive number of cars in the first lap of the race, or general problems with the servers, the coordinator(s) of the tier are allowed to announce a session restart at their own discretion. The decision made by the coordinator should not be discussed during the race, if you feel like the restart wasn't needed then please contact your coordinator after the race. Only one restart will be done per race week.
    • 3.7.2
      Any incidents happening before the restart, are still reportable and will be reviewed by the stewards.
  • 4.1 Communication
    • 4.1.1
      For the PC leagues, usually a driver briefing will be done by the coordinators in the AOR Discord channels before races. A driver briefing can be done through voice chat in Discord, or through the in-game chat. This depends on what the coordinator prefers and the coordinator will announce it before the start of the season.
    • 4.1.2
      During the driver briefings, it is not allowed for the drivers to use the in-game chat or talk in Discord. Not being up to date due to not attending a briefing or reading the chat, cannot be used as an excuse.
    • 4.1.3
      Once qualifying has started, drivers are expected to no longer use the in-game chat function until the race has ended (for all drivers). Not obeying this rule may result in a penalty. It is advised to have the in-game chat pop-ups enabled, so messages written by the coordinators are being read. PC leagues have access to the Discord server, which acts as one of the official communication platforms in AOR.
    • 4.1.4

      Spotters are only allowed to use the spectator password when live-stewarding is involved in a race. Spotters are not allowed to use the in-game chat at all. Abuse of this will result in spotters no longer being allowed as spectators for the remainder of the season. This will be monitored by the coordinators.

  • 4.2 Lobby etiquette
    • 4.2.1
      Shouting, name-calling and generally speaking rudely is not acceptable. Drivers who are a disruptive influence on the lobby atmosphere will be penalised accordingly, or in extreme cases removed from the league.
    • 4.2.2
      Respect the other drivers. Keep a friendly atmosphere in the race lobby and treat your fellow drivers as equals, regardless of them being quicker or slower than you.
    • 4.2.3

      Respect the coordinators and stewards.

      Listen to the coordinators if they are giving a message, and accept the decisions they make. If you feel any actions/decisions are wrong, address the issue calmly and maturely. Coordinators' decisions are final within the lobby, but may be reviewed later if you feel an error has been made. Please accept that making a call instantly can be tricky and the coordinators, even if participating in the race, are expected to be entirely neutral.

      Don't be disrespectful towards the stewards or publicly make fun of them. Being disappointed about a decision made by the stewards is understandable, but there is no need to be disrespectful.

  • 4.3 Race etiquette
    • 4.3.1
      If you are involved in an on-track incident, don't overreact. It may be frustrating, but you need to stay calm and get on with it. Losing out due to another driver's mistake or recklessness is no excuse for retaliation or acting against the rules.
    • 4.3.2
      If another driver does something you feel is against the rules, report it to the Stewards Panel after the race rather than argue about it over the voice chat or in Discord post-race.
    • 4.3.3
      If you are having a bad race, don't act foolishly. As a driver, you have to accept that some races will be better than others and you can't always have it your way. If you are unable to enjoy the racing due to not always being at the front, this is not the place for you - there are many drivers in the league, and someone will always have to be at the back.
    • 4.3.4
      Wait until everyone has finished the session, both qualifying and race, to discuss the race either on Discord or using the in-game chat.
    • 4.3.5
      The cool down lap is part of the race event and therefore the same rules are being applied. Crashing into each other is not allowed during the cool down lap or any other particular time during the race event.
    • 4.3.6
      Penalties will be applied to drivers who knowingly take out brake marker boards and other signs that could be used as reference points.
  • 4.4 Rage-quitting
    • 4.4.1
      Deliberately quitting the race in any way - whether that is by quitting through the pause menu, getting yourself disqualified or deliberately crashing your car - is not allowed, unless you have a very good reason to do so. Accepted reasons for quitting could be that you are a danger to other drivers on track due to poor driving or connection issues. Quitting because you "couldn't be bothered" or due to being angry at something - rage-quitting, in other words - are not good reasons.
    • 4.4.2
      Excuses such as 'poor driving' and 'connection issues' will be monitored. These are not a get-out of jail free cards if you can't be bothered. Poor driving is occasional, if perhaps life has been unkind and you haven't had as much time to practice. However, turning up each week having not practiced, and therefore not enjoying your racing because you're struggling will see you put under review. We don't expect every driver to complete a certain amount of practice each week, but we expect you to be able to control your car and be safe on track. Also the more practice you do, the more competitive you are.
    • 4.4.3
      Connection issues can strike anybody, but drivers who are continually unable to race safely due to connection will be removed from the league - see Connection and Lag under Participation.
    • 4.4.4
      Repeatedly quitting the race before it has finished, gives the coordinator team the freedom to remove you from the league. This may also mean that you will not be accepted in the league for the next season.
  • 4.5 Discord
    • 4.5.1
      You will need to be on the AOR Discord server while being a driver in our leagues. It is encouraged to get involved with the community in the chats on Discord. If staff members are trying to contact you for whatever reason, they are likely to message you on Discord.
    • 4.5.2
      You are expected to behave in a respectful manner on the AOR Discord, like in the race lobbies. Please avoid name-calling, baiting and other behaviour that is intended to aggravate other members of the community.
  • 5.1 Completing races
    • To be eligible for being classified points after a race, you must have completed at least 70% of the race. The amount of laps the winner of the race drove, is considered to be 100%.
  • 5.2 Missing races
    • 5.2.1
      If you are unable to attend a race, you have to give sufficient notice for your absence before the race starts. As a main driver, you can sign out from a race through our webpage. For every race there is an option to sign out from the race.
    • 5.2.2
      When informing the coordinator of your absence, a proper reason must be given for why you can't attend. No-showing a race because you don't like the track, because you "can't be bothered", or other similar reasons are not accepted and you position in the league will be put under review immediately. If your social life/work/school is taking up more time than you anticipated then we may consider a reserve role for you. Ultimately we can also decide that it's best if you withdraw from the league completely. Drivers have accepted to regularly attend races as part of the sign-up process.
    • 5.2.3
      As a main driver, you are supposed to sign out from a race at least 90 minutes before the race. This gives the coordinators enough time to contact reserve drivers who can then still practice as well.
    • 5.2.4
      If you are absent without informing your league coordinator or signing out through the webpage at least twice, the coordinator of your tier can decide to remove you from the league. This may also result in you not being allowed to join the league the following season(s).
    • 5.2.5
      The official starting time of a race will be stated in the race thread of every race. If everything goes according to plan, races start at this official starting time. In case of a race starting earlier or later than the official starting time, a coordinator will let all drivers of the tier know.
    • 5.2.6
      Getting another driver to race in your name is completely prohibited and will result in serious punishment.
  • 5.3 Connection & Lag
    • It's an unfortunate aspect of online racing that having a stable connection can be critical to being able to race closely with other cars. While we understand that not everyone can have perfect connections, and that occasional lag can't be avoided, we reserve the right to ask a driver to step down from the league if their connection is causing too many issues for other drivers. Coordinators reserve the right to disqualify a driver during the race if their connection pose a serious danger to other cars on track.
  • 5.4 Pulling out mid-season
    • 5.4.1
      Commitment and good communications are very important on AOR. If you have to pull out of an ACC league while the season is ongoing, you must let a member of the ACC Coordinator team know. If you leave by simply not showing up for the races, without informing anyone, the coordinators reserve the right to remove you from the league and put your name on the blacklist, which means you might not be allowed to rejoin the leagues in the current and future seasons.
    • 5.4.2
      It's impossible for us to stop anyone from leaving if they've made their mind up, but keep in mind when signing up that pulling out of the league without a proper reason while the season is ongoing will possibly see you placed on the blacklist. A proper reason would be something happening in your life that forces you to quit - something that you didn't expect when signing up - or that your equipment (hardware or lag issues) leave you unable to carry on. However, choosing to quit due to getting bored of the game, having a bad season or because something goes against you, is not a good reason. Remember, when signing up you commit yourself to racing for a full season, not only for a few races.
    • 5.4.3
      If you find yourself in a situation where you're not enjoying your league because all other drivers are too quick or too slow compared to yourself, contact one of the AOR ACC coordinators rather than just giving up - and maybe we can find a solution. We may grant league swaps for drivers during the season if it's clear that they've been misplaced, given that this doesn't upset the balance between the leagues with regards to driver numbers.
    • 5.4.4
      Note that the above rules only apply while the season is ongoing. We don't have a problem with drivers choosing to leave after a season has finished, for whatever reason.
  • 6.1 Stewarding systems

    • We have two systems in place to enforce rules and penalize on-track wrongdoing:

      • Live Stewarding
      • Stewards Panel system

      During live stewarding, stewards will be spectating the race, investigating incidents and handing out penalties while the race is ongoing. The Stewards Panel system will be in place during every official league race where live stewarding is not in place.

  • 6.2 Saving Replays
    • As a means of helping the stewards with their enquiries, all PC drivers are required to save their race replays and keep it stored for at least one week after the race has taken place. If possible, it's better if you can record your race so we can see a live view of your screen, although this is not required. PlayStation drivers are required to record their race and also save a replay at the end of the race, to make sure it covers their entire race.
  • 6.3 Stewards Panel
    • 6.3.1
      The Stewards Panel can be used to report incidents and other rule violations that occur in one of the official qualifying or race sessions. A proper explanation and/or evidence of the incident must be provided in order for it to be investigated. This will then be looked into by the stewards and appropriate action will be taken.
    • 6.3.2

      What you can make a stewards enquiry for:
      • Racing incidents: If you feel another driver has caused an incident - eg. hitting your car, forcing you off the track, or generally driving too aggressively - you should report this to the stewards for investigation.
      • Track limits: If you witness another driver persistently gaining time by abusing the track limits by either running wide or cutting corners, you should report this to the stewards for investigation.
      • Dangerous driving: If a driver rejoins the track in an unsafe or dangerous manner, or drives in a way that is a danger to other cars, you should report it to the stewards.


      You should only report incidents that you are directly involved in. A breach of rule violations such as abusing the maximum speed allowed in the pit lane, where no other driver may directly be involved, can be considered an exception to this rule. The stewards will in such cases on a per case basis determine,  whether an inquiry was rightfully made or if it is considered nit-picking. 

      Reporting an incident that you heard about, saw behind you or in general had no influence on you at all, will not be accepted.       This is to further lower the risk of a "nit-picking" environment. Two drivers may collide, shake hands and speak no more of it. If someone goes and starts causing trouble for the sake of it, the enquiries will be closed if those involved in the incident prefer it to go no further. Members of the @Coordinator ACC PC group, may open steward enquiries on any driver.

    • 6.3.3
      Time limit for enquiries: Note that enquiries need to be submitted before Thursday 23:59 PM UK time for incidents you have been involved in. If any new rule violations come to light through videos released after this time, it is still possible to report this, but only if this violation is something that was not visible to the other driver(s) in the race at the time it happened.
    • 6.3.4

      Uploading video evidence: Any video evidence submitted in a stewards enquiry must be uploaded to a video streaming site (such as YouTube and Streamable) before being embedded and/or linked to in the enquiry thread. Stewards should not have to download video files in order to watch your evidence.
      The following elements, recorded from the race replay, are required in the video:
      • Cockpit and Chase point of view of the driver submitting the enquiry, recorded at normal speed and with HUD activated
      • Cockpit and Chase point of view of the driver who caused the incident, recorded at normal speed and with HUD activated
      Any additional point of view can be added after the required elements. When the enquiry is related to ignoring blue flags, the cockpit point of views are not a requirement. If the video evidence is part of a longer video that also contains other parts of the race, a time stamp must be provided next to the video to guide the stewards to the relevant part of the video where the evidence can be found. Failing to do this may lead to the evidence being dismissed.

      In case more than five drivers were directly involved in one and the same incident - the driver creating the inquiry is expected to upload the replay of the race and post a link to it in the inquiry description. Only the stewards are allowed to request addition of the replay file, as it adds no value for other drivers involved. This driver will be contacted by one of the coordinators.

      The game offers an option to save replays automatically. It can be found in the General options of the game. Enable "Auto save replays" and change the "Replay max length" setting to the highest possible. It is then also possible to bind a button on your wheel/keyboard to save the replay manually.

  • 6.4 Race Penalties
    • 6.4.1

      The stewards have a variety of penalties that may be applied to punish drivers who break our racing rules, depending on the severity of the violation. The available penalties received in the stewards panel are sorted below, in order of severity and will depend on the Stewards decision. Penalty points may or may not be added to the Drivers License - see further down for more details. (Note that penalties may be added together in the event of multiple violations in a race, which could result in higher penalties than what is suggested below)
      ● 0-20 race results points reduction - Driving in a dangerous or unsporting manner.
      ● 0-20 race results points reduction - Causing a minor avoidable collision.
      ● 0-40 race results points reduction - Causing a moderate avoidable collision.
      ● 0-60 race results points reduction - Causing a significant avoidable collision.
      ● 0-80 race results points reduction - Causing a major avoidable collision.
      The above means that the winner of a race could receive fewer points than the driver who finished in P2. This would mean that the winner of that race was to blame for causing a collision, while the P2 finisher had a clean race.

    • 6.4.2
      Modifiers to Race Penalties in the Stewards Panel:
      • Returning the position after an avoidable collision may result in the points deduction being reduced. Stewards encourage giving the position back or an attempt at waiting.
      • Causing an avoidable incident in the opening lap may result in an increase of result points deduction.
      • If the consequences of a penalty are worse or not as bad as the contact itself, the points reduction may be higher/lower than the usual punishments mentioned in the overview above.
      • Not slowing down when clearly witnessing an incident in front of you, may result in an increase of result points deduction.
  • 6.5 Drivers License Penalties
    • 6.5.1
      The Driver’s License points system is a way of keeping track of a driver's record of breaking the rules of clean racing, and to more severely punish repeat offenders. Driver’s License Points will not be influenced by external circumstances related to an incident, they will only be given for the severity of an incident. Driver License Points may or may not be applied alongside race penalties, as per the list below.
      ● 0 to 1 points - Driving in a dangerous or unsporting manner.
      ● 1 points - Causing a minor avoidable collision.
      ● 2 points - Causing a moderate avoidable collision.
      ● 3 points - Causing a significant avoidable collision.
      ● 4 points - Causing a major avoidable collision.
    • 6.5.2
      Modifiers to Driver’s License Penalties:
      • +1 point - Causing an avoidable incident in the opening lap
    • 6.5.3

      Driver’s License accumulations:

      • If a driver accumulates 5 points, they will be awarded a Qualifying ban
      • If a driver accumulates 8 points, they will be awarded a Race ban
      • If a driver accumulates 10 points, they will be removed from the league
      • If a driver accumulates 5 or more points during one event, they will be awarded a Race Ban.

      When a driver accumulates more than 6 points during a season, at the end of that season the drivers' position in the league will be reviewed for future seasons.

    • 6.5.4

      Every second warning a driver receives, automatically results in 1 license point.

    • 6.5.5
      Driver’s License points will reset to zero at the start of a new season
    • 6.5.6
      Any penalties will be aimed at the person who has done wrong - we cannot compensate anyone else as a result of someone's actions. All penalties are discussed by the Stewards Panel before being issued and the driver will always be informed of the outcome. The Stewards Panel is completely neutral and will not include anyone who may be affected by the incident in question with race results or championship points.
  • 6.6 Live stewarding - Penalties and penalty points system

    • The available race penalties during live stewarding are:
      ● 5-10-15 second time penalty - Dangerous driving, driving in an unsporting manner or causing a minor avoidable collision.
      ● 0-45 second time penalty - Causing a moderate avoidable collision.
      ● 0-75 second time penalty - Causing a significant avoidable collision.
      ● 0-90 second time penalty - Causing a major avoidable collision.

      ● Disqualification - Intentionally trying or crashing into another car and other unacceptable behavior. Can also be used by the race director for various other reasons (which will be stated in Discord after the race).

      The penalty points system will be used when live stewarding is announced for a certain tier (or multiple).
      No penalties carry over to the next race. Penalty points will be reset at the end of every season.

      Penalty points will be added to a driver's record when they receive an in-game penalty.
      ● Receiving a 5 or 10 second time penalty for dangerous driving or a minor avoidable collision, will result in 0 penalty points
      ● Receiving a 15 second time penalty or more than one penalty for minor collisions or dangerous driving during a race, will result in 1 penalty point
      ● Receiving a penalty for a moderate avoidable collision during the race, will result in 2 penalty points
      ● Receiving a penalty for a significant avoidable collision during the race, will result in 3 penalty points
      ● Receiving a penalty for a major avoidable collision during the race, will result in 4 penalty points

      Reaching the following amounts of penalty points will have additional consequences:
      • 5 penalty points results in receiving a qualifying ban. You will not be allowed to leave the pit-lane during the next qualifying session.
      • 8 penalty points results in receiving a race ban. You will not be allowed to attend the next qualifying and race session. Your position in the league will be reviewed by the coordinators.
      • 10 penalty points results in being removed from the league.

      After every race, an overview of penalties awarded during the race will be published.

      In case an incident is overlooked by the stewards, drivers can still create an enquiry through the Stewards Panel. This will be looked at by the Stewards and a verdict will be posted before the next race. Any time penalty received through the stewards panel, will be added to a driver's total race time of the most recent race.

  • 6.7 Reprimand system

    • While the race penalties and penalty points systems are aimed at dealing with on-track issues, the reprimand system deals with issues that may occur off the track. If you receive 3 reprimands, you will be removed from the league. Receiving 3 reprimands would also see you placed on the blacklist, meaning you would not be allowed to return to the leagues in the future. You will receive a reprimand for the following:

      ● Deliberately crashing out of the session
      ● Showing abusive behavior towards another driver, either in the race lobby or in discord.
      ● Intentionally hiding/removing evidence and/or footage to avoid receiving a penalty in an enquiry

      As an additional tool, coordinators can give drivers a timeout in Discord. Receiving a timeout in Discord equals a reprimand.

      Note that if we encounter situations where someone's behavior gets completely out of hand and is extremely serious, a ban may be applied directly regardless of reprimands accumulated.

  • 6.8 Blacklist
    • The blacklist contains the names of drivers who have been removed from the leagues - either through accumulating 10 penalty points from the stewards panel, due to not attending races regularly - and drivers who have left the leagues during an ongoing season without a valid reason. Having your name applied to the blacklist generally means you will not be allowed to rejoin the leagues in the current and next season.
Once tiers have been announced you can create a team to compete in the optional team championship.
Teams must consist of 2 drivers.
The deadline for creating a team is before race 3 of the season