GT3 GT3 Season 9 pc

Apex Online Racing

League Information

Signups closed
Signup:
01.01.2022 - 18.01.2022
Season period:
25.01.2022 - 22.03.2022
Evaluation races:
04.01.2022 19:30 UTC
09.01.2022 19:30 UTC
11.01.2022 19:30 UTC
16.01.2022 19:30 UTC
17.01.2022 19:30 UTC
18.01.2022 19:30 UTC

General Information:

  • FOR MID-SEASON SIGN-UPS: NOT EVERY TIER CURRENTLY HAS EMPTY (RESERVE)SEATS - THIS MEANS YOU MAY STILL HAVE TO WAIT ONE OR MORE RACES BEFORE YOU ARE PLACED IN ONE OF OUR TIERS. MAKE SURE YOU HAVE COMPLETED YOUR HOTSTINTS AND EVALUATION RACE. AFTERWARDS ONE OF THE COORDINATORS WILL CONTACT YOU WHEN THEY ARE ABOUT TO PLACE YOU IN ONE OF THE TIERS.
  • 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 - since the 1.8 patch of the game changed the handling of cars quite a lot.
  • 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. 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 league 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 either a 60 minutes race or a 90 minutes 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.

25.01.2022 19:30 UTC FR Paul Ricard
Tier 1: 24.01.2022

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": "paul_ricard", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 22, "cloudLevel": 0.2, "rain": 0.0, "weatherRandomness": 1, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 21, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 21, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 21, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Session info FR Paul Ricard
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races FR Paul Ricard
22.01.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Paul Ricard | #AORPR Results
22.01.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Paul Ricard | #AORPR Results
22.01.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Paul Ricard | #AORPR Results
23.01.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Paul Ricard | #AORPR Results
23.01.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Paul Ricard | #AORPR Results
23.01.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Paul Ricard | #AORPR Results
23.01.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 4 - Paul Ricard | #AORPR Results
24.01.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Paul Ricard | #AORPR Results
24.01.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Paul Ricard | #AORPR Results
24.01.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Paul Ricard | #AORPR Results

01.02.2022 19:30 UTC DE Nürburgring
Tier 1: 31.01.2022

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
50% dry
50% wet
50% changing conditions
Server Json
{ "track": "nurburgring", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 15, "cloudLevel": 0.39, "rain": 0.13, "weatherRandomness": 5, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 15, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 16, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 15, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Session info DE Nürburgring
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races DE Nürburgring
29.01.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Nuerburgring | #AORPR Results
29.01.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Nuerburgring | #AORPR Results
30.01.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Nuerburgring | #AORPR Results
30.01.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Nuerburgring | #AORPR Results
30.01.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Nuerburgring | #AORPR Results
31.01.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Nuerburgring | #AORPR Results
31.01.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Nuerburgring | #AORPR Results
31.01.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Nuerburgring | #AORPR Results

08.02.2022 19:30 UTC GB Brands Hatch
Tier 1: 07.02.2022

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": 32, "cloudLevel": 0.55, "rain": 0.0, "weatherRandomness": 2, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 12, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 11, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 12, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Session info GB Brands Hatch
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races GB Brands Hatch
05.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Brands Hatch | #AORPR Results
05.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Brands Hatch | #AORPR Results
06.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Brands Hatch | #AORPR Results
06.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Brands Hatch | #AORPR Results
06.02.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Brands Hatch | #AORPR Results
07.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 2 - Brands Hatch | #AORPR Results
07.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Brands Hatch | #AORPR Results
07.02.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 2 - Brands Hatch | #AORPR Results

15.02.2022 19:30 UTC GB Donington
Tier 1: 14.02.2022

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": "donington", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 18, "cloudLevel": 0.1, "rain": 0.0, "weatherRandomness": 1, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 2, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 3, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 2, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Session info GB Donington
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races GB Donington Fastest practice times
12.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Donington Park | #AORPR Results
13.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Donington Park | #AORPR Results
13.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Donington Park | #AORPR Results
13.02.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Donington Park | #AORPR Results
14.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Donington Park | #AORPR Results
14.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Donington Park | #AORPR Results
14.02.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Donington Park | #AORPR Results

01.03.2022 19:30 UTC HU Hungaroring
Tier 1: 28.02.2022

Results
Race info
Race length: 90 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: No
Mandatory refueling: No
Refueling allowed: Yes
Weather forecast
100% dry
0% wet
0% changing conditions
Server Json
{ "track": "hungaroring", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 30, "cloudLevel": 0.2, "rain": 0.0, "weatherRandomness": 1, "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": 90 } ], "configVersion": 1 }
Session info HU Hungaroring
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races HU Hungaroring Fastest practice times
27.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Hungaroring | #AORPR Results
27.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Hungaroring | #AORPR Results
27.02.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Hungaroring | #AORPR Results
28.02.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Hungaroring | #AORPR Results
28.02.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Hungaroring | #AORPR Results
28.02.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Hungaroring | #AORPR Results

08.03.2022 19:30 UTC BE Spa
Tier 1: 07.03.2022

Results
Race info
Race length: 60 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: Yes
Mandatory refueling: No
Refueling allowed: No
Weather forecast
50% dry
50% wet
50% changing conditions
Server Json
{ "track": "spa", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 21, "cloudLevel": 0.40, "rain": 0.20, "weatherRandomness": 5, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 13, "dayOfWeekend": 1, "timeMultiplier": 2, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 12, "dayOfWeekend": 2, "timeMultiplier": 2, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 13, "dayOfWeekend": 3, "timeMultiplier": 2, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Session info BE Spa
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races BE Spa Fastest practice times
06.03.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Spa | #AORPR Results
06.03.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Spa | #AORPR Results
06.03.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Spa | #AORPR Results
07.03.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Spa | #AORPR Results
07.03.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Spa | #AORPR Results
07.03.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Spa | #AORPR Results

15.03.2022 19:30 UTC BE Zolder
Tier 1: 14.03.2022

Results
Race info
Race length: 90 minutes
Mandatory pit-stop(s): 1
Mandatory tire change: No
Mandatory refueling: No
Refueling allowed: Yes
Weather forecast
100% dry
0% wet
0% changing conditions
Server Json
{ "track": "zolder", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 20, "cloudLevel": 0.1, "rain": 0.0, "weatherRandomness": 1, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 20, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 90 }, { "hourOfDay": 20, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 20, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 90 } ], "configVersion": 1 }
Session info BE Zolder
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races BE Zolder Fastest practice times
13.03.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Zolder | #AORPR Results
13.03.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Zolder | #AORPR Results
13.03.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Zolder | #AORPR Results
14.03.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Zolder | #AORPR Results
14.03.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Zolder | #AORPR Results
14.03.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Zolder | #AORPR Results

22.03.2022 19:30 UTC GB Silverstone
Tier 1: 21.03.2022

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": "silverstone", "preRaceWaitingTimeSeconds": 240, "sessionOverTimeSeconds": 200, "postQualySeconds": 30, "postRaceSeconds": 900, "ambientTemp": 22, "cloudLevel": 0.1, "rain": 0.0, "weatherRandomness": 1, "simracerWeatherConditions": 1, "sessions": [ { "hourOfDay": 10, "dayOfWeekend": 1, "timeMultiplier": 1, "sessionType": "P", "sessionDurationMinutes": 60 }, { "hourOfDay": 11, "dayOfWeekend": 2, "timeMultiplier": 1, "sessionType": "Q", "sessionDurationMinutes": 15 }, { "hourOfDay": 10, "dayOfWeekend": 3, "timeMultiplier": 1, "sessionType": "R", "sessionDurationMinutes": 60 } ], "configVersion": 1 }
Session info GB Silverstone
● Practice - 18:30 UTC (19:30 CET)
● Qualifying - 19:30 UTC (20:30 CET)
● Race - 19:50 UTC (20:50 CET)
Practice Races GB Silverstone Fastest practice times
20.03.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Silverstone | #AORPR Results
20.03.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Silverstone | #AORPR Results
20.03.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Silverstone | #AORPR Results
21.03.2022 19:30 UTC ApexOnline.Racing #50 | AOR Season 9 - Practice Race Server 1 - Silverstone | #AORPR Results
21.03.2022 19:30 UTC ApexOnline.Racing #51 | AOR Season 9 - Practice Race Server 2 - Silverstone | #AORPR Results
21.03.2022 19:30 UTC ApexOnline.Racing #52 | AOR Season 9 - Practice Race Server 3 - Silverstone | #AORPR Results
  • 1.1 Clean racing
    • 1.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.
    • 1.1.2
      Deliberately crashing into another car will result in being permanently excluded from our ACC leagues and events.
    • 1.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.
  • 1.2 Overtaking
    • 1.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.
    • 1.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.
  • 1.3 Defending
    • 1.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.
    • 1.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.
  • 1.4 Corner cutting/track extending
    • 1.4.1
      Stay within the track boundaries with at least two tyres at all times. The track boundaries are defined in game. Cutting corners, or extending the track, to gain an advantage is not allowed. Drivers found to be persistently breaking this rule will be penalised retrospectively.
    • 1.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.
    • 1.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.
    • 1.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.
  • 1.5 Qualifying etiquette
    • 1.5.1
      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 faster cars pass you without blocking them. If you are on a fast lap approaching a slow car, flashing your lights is a way of notifying them that you're on a fast lap.
  • 1.6 Spatial Awareness
    • 1.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.
    • 1.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.
    • 1.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.
    • 1.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 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.
  • 1.7 Pit exit and pit entry
    • 1.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.
    • 1.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.
    • 1.7.3
      A car is considered to be in the pit exit or entry zone when all four wheels are within the white lines.
    • 1.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.
    • 1.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).
  • 2.1 Being lapped
    • 2.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. This means that you're not allowed to brake later than the lapping car.
    • 2.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.
    • 2.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.
  • 2.2 Pit stops
    • 2.2.1
      Stay within the white line and obey the speed limit when entering and exiting the pit lane. 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. Remember to assign your pit limiter button as well. The speed limit line is enforced by ACC.
    • 2.2.2
      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.
    • 2.2.3
      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.
  • 2.3 Driving in different conditions
    • 2.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.
    • 2.3.2
      The above rule about having headlights on also applies to running in the fog and in the rain.
    • 2.3.3
      During rainy conditions, having the rain lights turned on is mandatory.
    • 2.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.
  • 2.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.
  • 2.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.
  • 2.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. Long formation lap is being used in our league races.
  • 2.7 Restarts
    • 2.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.
    • 2.7.2
      Any incidents happening before the restart, are still reportable and will be looked at by the stewards.
  • 3.1 Communication
    • 3.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.
    • 3.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.
    • 3.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.
  • 3.2 Lobby etiquette
    • 3.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.
    • 3.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.
    • 3.2.3
      Respect the League Coordinator. Listen if he is giving a message, and accept the decisions he makes. 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 Coordinator, even if participating in the race, is expected to be entirely neutral.
  • 3.3 Race etiquette
    • 3.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.
    • 3.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 the forums post-race.
    • 3.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.
    • 3.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.
    • 3.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.
    • 3.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.
  • 3.4 Rage-quitting
    • 3.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.
    • 3.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.
    • 3.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.
    • 3.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.
  • 3.5 Discord
    • 3.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.
    • 3.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.
  • 4.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%.
  • 4.2 Missing races
    • 4.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 the apexonline.racing webpage. For every race there is an option to sign out from the race.
    • 4.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.
    • 4.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.
    • 4.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).
    • 4.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.
    • 4.2.6
      Getting another driver to race in your name is completely prohibited and will result in serious punishment.
  • 4.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.
  • 4.4 Pulling out mid-season
    • 4.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.
    • 4.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.
    • 4.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.
    • 4.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.
  • 5.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.
  • 5.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.
  • 5.3 Stewards Panel
    • 5.3.1
      The Stewards Panel can be used to report incidents and other rule violations that occur in a race. 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.
    • 5.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 report incidents that you are involved in. Reporting an incident that you heard about, or saw behind you for example, will not be accepted. This is to 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 @ACC Coordinator group, may open steward enquiries on any driver.
    • 5.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.
    • 5.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.
  • 5.4 Race Penalties
    • 5.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 total time penalties of a higher number 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.
    • 5.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.
  • 5.5 Drivers License Penalties
    • 5.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.
      ● 5 points - Driving in a dangerous or unsporting manner.
      ● 5 points - Causing a minor avoidable collision.
      ● 10 points - Causing a moderate avoidable collision.
      ● 15 points - Causing a significant avoidable collision.
      ● 20 points - Causing a major avoidable collision.
    • 5.5.2
      Modifiers to Driver’s License Penalties:
      • +5 points - Causing an avoidable incident in the opening lap
    • 5.5.3
      Clean Racing Award:
      • -5 points - Completing a race without any penalty. (Note: points balance won't go below 0)
    • 5.5.4
      Driver’s License accumulations:
      • If you accumulate 15 points, you will be awarded a 30 second time penalty*
      • If you accumulate 25 points, you will be awarded a 45 second time penalty*
      • If you accumulate 40 points, you will be awarded a Qualifying or a Race Ban
      • If you accumulate 50 points, your league status will be put under review, with the likely outcome of being removed from the league

      * Penalties will be applied by coordinators via ACC admin commands at the start of the formation lap of the next race.
    • 5.5.5
      Driver’s License points will carry over to a new season
    • 5.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 (consisting of the members of the AOR ACC Team - Admins, Moderators and Coordinators - from all platforms) 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.
  • 5.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-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 major avoidable collision during the race, will result in 3 penalty points
      Reaching the following amounts of penalty points will have 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.
      • 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.
  • 5.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 can receive a reprimand for the following:

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

      Note that if we encounter situations where someone's behaviour gets completely out of hand and is extremely serious, a ban may be applied directly regardless of reprimands accumulated.
  • 5.8 Blacklist
    • The blacklist contains the names of drivers who have been removed from the leagues - either through accumulating 50 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