GT3 Season 3
Apex Online Racing
League Information
Signups closed
Signup:
13.04.2021 - 24.04.2021
Season period:
04.05.2021 - 29.06.2021
Evaluation races:
18.04.2021 18:30 UTC
19.04.2021 18:30 UTC
25.04.2021 18:30 UTC
26.04.2021 18: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.
- 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: Drivers who did not participate in Season 2 will need to complete two hotstints - Nรผrburgring and Suzuka. Returning drivers from Season 2 only have to do the Suzuka hotstint.
- Evaluation Races: Drivers new to AOR need to do at least one evaluation race. Returning drivers are free to join, but new drivers have priority.
- Assists: All tiers will have the maximum stability control setting to zero and auto-steer disabled.
- 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 with starting the qualifying from 7:30pm (UK time).
# | Driver | Best Overall | Nürburgring | Laps | Car | Suzuka | Laps | Car | Valid |
---|---|---|---|---|---|---|---|---|---|
1 | DgC_Gehrig | 10:06.375 | 00:00.000 | 0 | 10:06.375 | 5 | |||
2 | VP_McGrady | 10:06.729 | 00:00.000 | 0 | 10:06.729 | 5 | |||
3 | CSR_schwantz34 | 10:06.747 | 00:00.000 | 0 | 10:06.747 | 5 | |||
4 | Jazzman77709876 | 10:07.134 | 00:00.000 | 0 | 10:07.134 | 5 | |||
5 | CSR_Kaczalski | 10:08.199 | 00:00.000 | 0 | 10:08.199 | 5 | |||
6 | Will-Friedmann | 10:08.376 | 00:00.000 | 0 | 10:08.376 | 5 | |||
7 | R3FR4CT_ | 10:08.925 | 00:00.000 | 0 | 10:08.925 | 5 | |||
8 | michaeljc53 | 10:09.435 | 00:00.000 | 0 | 10:09.435 | 5 | |||
9 | flawed_algorithm | 10:10.998 | 00:00.000 | 0 | 10:10.998 | 5 | |||
10 | Bgsgsdegha | 10:11.013 | 00:00.000 | 0 | 10:11.013 | 5 | |||
11 | MatthewAsbreuk | 10:11.355 | 00:00.000 | 0 | 10:11.355 | 5 | |||
12 | Anthos77 | 10:11.808 | 00:00.000 | 0 | 10:11.808 | 5 | |||
13 | Spenced_7 | 10:11.892 | 00:00.000 | 0 | 10:11.892 | 5 | |||
14 | Rotters91 | 10:11.958 | 00:00.000 | 0 | 10:11.958 | 5 | |||
15 | jawaite | 10:12.015 | 00:00.000 | 0 | 10:12.015 | 5 | |||
16 | TheTubbyNinja | 10:12.420 | 00:00.000 | 0 | 10:12.420 | 5 | |||
17 | RedBullEnergyyy | 10:13.443 | 00:00.000 | 0 | 10:13.443 | 5 | |||
18 | M20PCD | 10:13.659 | 00:00.000 | 0 | 10:13.659 | 5 | |||
19 | Marty-VR | 10:14.886 | 00:00.000 | 0 | 10:14.886 | 5 | |||
20 | Meester_Bond_WHG | 10:15.267 | 00:00.000 | 0 | 10:15.267 | 5 | |||
21 | VuNcE13 | 10:15.522 | 00:00.000 | 0 | 10:15.522 | 5 | |||
22 | Leonmsealy | 10:15.669 | 00:00.000 | 0 | 10:15.669 | 5 | |||
23 | WRC_madmax | 10:16.782 | 00:00.000 | 0 | 10:16.782 | 5 | |||
24 | AnAngryPidgeon | 10:16.995 | 00:00.000 | 0 | 10:16.995 | 5 | |||
25 | Wardy636 | 10:17.211 | 00:00.000 | 0 | 10:17.211 | 5 | |||
26 | denisdowntown28 | 10:17.679 | 00:00.000 | 0 | 10:17.679 | 5 | |||
27 | Chizubaga | 10:17.883 | 00:00.000 | 0 | 10:17.883 | 5 | |||
28 | FLYSKYDHK | 10:17.910 | 00:00.000 | 0 | 10:17.910 | 5 | |||
29 | neez84 | 10:18.360 | 00:00.000 | 0 | 10:18.360 | 5 | |||
30 | Lsd_high321 | 10:18.645 | 00:00.000 | 0 | 10:18.645 | 5 | |||
31 | Flabbs | 10:18.687 | 00:00.000 | 0 | 10:18.687 | 5 | |||
32 | silverfox5910 | 10:18.792 | 00:00.000 | 0 | 10:18.792 | 5 | |||
33 | Trucker-Lex93 | 10:21.087 | 00:00.000 | 0 | 10:21.087 | 5 | |||
34 | Hygrade_B_876 | 10:22.923 | 00:00.000 | 0 | 10:22.923 | 5 | |||
35 | Mcquiz95 | 10:23.019 | 00:00.000 | 0 | 10:23.019 | 5 | |||
36 | mprietod | 10:23.553 | 00:00.000 | 0 | 10:23.553 | 5 | |||
37 | crukip | 10:24.006 | 00:00.000 | 0 | 10:24.006 | 5 | |||
38 | chris130256 | 10:24.195 | 00:00.000 | 0 | 10:24.195 | 5 | |||
39 | opentheirminds | 10:24.324 | 00:00.000 | 0 | 10:24.324 | 5 | |||
40 | B4RN3Y__87 | 10:24.897 | 00:00.000 | 0 | 10:24.897 | 5 | |||
41 | fraantje | 10:25.089 | 00:00.000 | 0 | 10:25.089 | 5 | |||
42 | Ayresii1995 | 10:26.553 | 00:00.000 | 0 | 10:26.553 | 5 | |||
43 | Zout_101 | 10:26.766 | 00:00.000 | 0 | 10:26.766 | 5 | |||
44 | KentFusag | 10:27.315 | 00:00.000 | 0 | 10:27.315 | 5 | |||
45 | BMTM_Shifter | 10:27.618 | 00:00.000 | 0 | 10:27.618 | 5 | |||
46 | PRG_FredOgega | 10:28.017 | 00:00.000 | 0 | 10:28.017 | 5 | |||
47 | tomji_ | 10:28.562 | 00:00.000 | 0 | 10:28.562 | 5 | |||
48 | neonostra | 10:30.321 | 00:00.000 | 0 | 10:30.321 | 5 | |||
49 | PRG_FrankForest | 10:36.729 | 00:00.000 | 0 | 10:36.729 | 5 | |||
50 | Stuart_pietzka | 10:45.654 | 00:00.000 | 0 | 10:45.654 | 5 | |||
51 | Petr_Postl | 20:24.612 | 10:01.332 | 5 | 10:23.280 | 5 | |||
52 | Slow_wolf1 | 20:33.066 | 10:05.370 | 5 | 10:27.696 | 5 | |||
53 | Jinx98765 | 20:41.401 | 10:02.491 | 5 | 10:38.910 | 5 | |||
54 | Nitoher72 | 20:44.553 | 10:11.280 | 5 | 10:33.273 | 5 | |||
55 | SMT_Zoloba | 20:52.680 | 10:18.051 | 5 | 10:34.629 | 5 | |||
56 | TobyclassicGB | 20:56.865 | 10:12.210 | 5 | 10:44.655 | 5 | |||
57 | shmaids | 21:03.143 | 10:21.464 | 5 | 10:41.679 | 5 | |||
58 | Lacsap-Yoon | 21:08.829 | 10:24.279 | 5 | 10:44.550 | 5 | |||
59 | Eddie_cwb07 | 21:11.231 | 10:09.510 | 5 | 11:01.721 | 5 | |||
60 | lokka09 | 21:31.002 | 11:27.165 | 6 | 10:03.837 | 5 | |||
61 | Boy_RaXer14 | 21:32.865 | 11:24.801 | 6 | 10:08.064 | 5 | |||
62 | CoKa_Original | 21:34.104 | 11:30.702 | 6 | 10:03.402 | 5 | |||
63 | KillCity_GR27 | 21:34.143 | 11:28.407 | 6 | 10:05.736 | 5 | |||
64 | Juustokeisari | 21:36.003 | 10:18.516 | 5 | 11:17.487 | 5 | |||
65 | Mariodep097 | 21:38.712 | 11:31.650 | 6 | 10:07.062 | 5 | |||
66 | wikinico | 21:39.249 | 11:30.114 | 6 | 10:09.135 | 5 | |||
67 | Stitch5yy024 | 21:39.543 | 11:30.507 | 6 | 10:09.036 | 5 | |||
68 | PorcaVacca_91 | 21:40.119 | 11:32.088 | 6 | 10:08.031 | 5 | |||
69 | MVP_CORNERCRACK_ | 21:41.040 | 11:33.462 | 6 | 10:07.578 | 5 | |||
70 | CRN_Haighy | 21:41.259 | 11:35.295 | 6 | 10:05.964 | 5 | |||
71 | C_Leclerc_ | 21:42.804 | 11:32.730 | 6 | 10:10.074 | 5 | |||
72 | Enten_Salat_33 | 21:43.470 | 11:32.994 | 6 | 10:10.476 | 5 | |||
73 | Dive_Bomber52 | 21:44.253 | 11:37.572 | 6 | 10:06.681 | 5 | |||
74 | Schnixel | 21:45.750 | 11:36.255 | 6 | 10:09.495 | 5 | |||
75 | Flipping83 | 21:45.927 | 11:34.971 | 6 | 10:10.956 | 5 | |||
76 | marco1997mnm | 21:48.465 | 11:35.571 | 6 | 10:12.894 | 5 | |||
77 | ART_Connor_74 | 21:48.546 | 11:37.395 | 6 | 10:11.151 | 5 | |||
78 | Vitalycrash | 21:48.552 | 11:36.864 | 6 | 10:11.688 | 5 | |||
79 | Ix_unforg1v3n_xI | 21:49.083 | 11:41.496 | 6 | 10:07.587 | 5 | |||
80 | Coldtyre | 21:50.229 | 11:38.313 | 6 | 10:11.916 | 5 | |||
81 | SOP_MILDEN | 21:50.739 | 11:38.397 | 6 | 10:12.342 | 5 | |||
82 | COULL444RACING | 21:52.254 | 11:40.398 | 6 | 10:11.856 | 5 | |||
83 | Warlord_3099 | 21:52.488 | 11:40.041 | 6 | 10:12.447 | 5 | |||
84 | Sneaky24-7Ninja | 21:52.758 | 11:38.424 | 6 | 10:14.334 | 5 | |||
85 | Prehn | 21:52.803 | 11:37.749 | 6 | 10:15.054 | 5 | |||
86 | doquno | 21:52.896 | 11:39.813 | 6 | 10:13.083 | 5 | |||
87 | Essaracin | 21:54.321 | 11:38.730 | 6 | 10:15.591 | 5 | |||
88 | Johnny-Medrala | 21:54.498 | 11:41.955 | 6 | 10:12.543 | 5 | |||
89 | Igor_Param | 21:55.770 | 11:39.522 | 6 | 10:16.248 | 5 | |||
90 | Tobyheokxx | 21:57.879 | 11:43.071 | 6 | 10:14.808 | 5 | |||
91 | Markicevicus93 | 21:58.762 | 11:42.442 | 6 | 10:16.320 | 5 | |||
92 | DJDCleanShirt | 21:58.956 | 11:42.423 | 6 | 10:16.533 | 5 | |||
93 | DriveOfAgony | 21:59.757 | 11:43.170 | 6 | 10:16.587 | 5 | |||
94 | Nike_r_OK | 22:00.522 | 11:43.485 | 6 | 10:17.037 | 5 | |||
95 | SirTerehov | 22:00.894 | 11:40.179 | 6 | 10:20.715 | 5 | |||
96 | Luche109 | 22:01.137 | 11:42.312 | 6 | 10:18.825 | 5 | |||
97 | F1HL_SMT_ifjszcs | 22:01.482 | 11:42.747 | 6 | 10:18.735 | 5 | |||
98 | Thomasw769 | 22:01.659 | 11:45.732 | 6 | 10:15.927 | 5 | |||
99 | ediz-olcum | 22:01.767 | 10:44.793 | 5 | 11:16.974 | 5 | |||
100 | Adam_YNWA_foster | 22:01.785 | 11:43.137 | 6 | 10:18.648 | 5 | |||
101 | YabbaTheHutt | 22:02.304 | 11:43.437 | 6 | 10:18.867 | 5 | |||
102 | Tomas_Cezar | 22:04.029 | 11:45.093 | 6 | 10:18.936 | 5 | |||
103 | emreates_ | 22:04.245 | 10:37.806 | 5 | 11:26.439 | 5 | |||
104 | jsbarker95 | 22:04.293 | 11:46.905 | 6 | 10:17.388 | 5 | |||
105 | JR-Lock-N-Load | 22:04.949 | 11:47.189 | 6 | 10:17.760 | 5 | |||
106 | DAVEJ2013 | 22:05.220 | 11:44.976 | 6 | 10:20.244 | 5 | |||
107 | S-FELL-89 | 22:05.628 | 11:44.973 | 6 | 10:20.655 | 5 | |||
108 | SV_Kiselev | 22:07.719 | 11:49.449 | 6 | 10:18.270 | 5 | |||
109 | EMR_TxeliGSI | 22:07.806 | 11:48.912 | 6 | 10:18.894 | 5 | |||
110 | AlbertDeanI | 22:08.433 | 11:45.045 | 6 | 10:23.388 | 5 | |||
111 | carlos2008nc | 22:08.868 | 11:47.748 | 6 | 10:21.120 | 5 | |||
112 | Fot_79 | 22:09.897 | 11:46.623 | 6 | 10:23.274 | 5 | |||
113 | Devilsarmpit666 | 22:10.527 | 11:44.667 | 6 | 10:25.860 | 5 | |||
114 | RSlicker | 22:11.670 | 11:50.565 | 6 | 10:21.105 | 5 | |||
115 | Bigjeff1982_ | 22:12.765 | 11:51.294 | 6 | 10:21.471 | 5 | |||
116 | yellow-army84 | 22:13.368 | 11:50.034 | 6 | 10:23.334 | 5 | |||
117 | golzy | 22:14.478 | 11:51.204 | 6 | 10:23.274 | 5 | |||
118 | Mattiep9017 | 22:18.351 | 11:55.128 | 6 | 10:23.223 | 5 | |||
119 | JeroenG81 | 22:18.675 | 11:57.108 | 6 | 10:21.567 | 5 | |||
120 | Kslt55 | 22:19.339 | 11:53.055 | 5 | 10:26.284 | 5 | |||
121 | EarlyTerrorSpons | 22:20.796 | 11:55.239 | 6 | 10:25.557 | 5 | |||
122 | eCaptainKirk | 22:20.874 | 11:52.131 | 6 | 10:28.743 | 5 | |||
123 | Valbuena39_ | 22:22.080 | 11:54.471 | 6 | 10:27.609 | 5 | |||
124 | iDrasnop | 22:22.470 | 11:55.392 | 6 | 10:27.078 | 5 | |||
125 | Archie619 | 22:27.240 | 11:46.134 | 6 | 10:41.106 | 5 | |||
126 | surelook_ | 22:27.471 | 11:56.736 | 6 | 10:30.735 | 5 | |||
127 | NathBit | 22:27.501 | 11:56.022 | 6 | 10:31.479 | 5 | |||
128 | CHFALCKNER | 22:34.761 | 11:59.445 | 6 | 10:35.316 | 5 | |||
129 | Fozzy12 | 23:06.960 | 10:37.389 | 5 | 12:29.571 | 5 | |||
130 | DaveyZout | 22:21.546 | 11:56.988 | 6 | 10:24.558 | 5 | |||
131 | SMT_Boardman | 11:58.224 | 11:58.224 | 6 | 00:00.000 | ||||
132 | Kalló Ferenc | 20:56.742 | 10:04.599 | 5 | 10:52.143 | 5 | |||
133 | op2873 | 21:00.699 | 10:18.102 | 5 | 10:42.597 | 5 | |||
134 | Violent_S15 | 21:50.850 | 11:36.621 | 6 | 10:14.229 | 5 |
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
Practice Races Paul Ricard
02.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 1 Paul Ricard - Practice | discord.gg/ACrk2wG | Results |
03.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 1 Paul Ricard - Practice | discord.gg/ACrk2wG | Results |
03.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 1 Paul Ricard - Practice | discord.gg/ACrk2wG | 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
Practice Races Brands Hatch
09.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 2 Brands Hatch - Practice | discord.gg/ACrk2wG | Results |
09.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 2 Brands Hatch - Practice | discord.gg/ACrk2wG | Results |
10.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 2 Brands Hatch - Practice | discord.gg/ACrk2wG | Results |
10.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 2 Brands Hatch - Practice | discord.gg/ACrk2wG | 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
Practice Races Barcelona
16.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 3 Barcelona - Practice | discord.gg/ACrk2wG | Results |
16.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 3 Barcelona - Practice | discord.gg/ACrk2wG | Results |
17.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 3 Barcelona - Practice | discord.gg/ACrk2wG | Results |
17.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 3 Barcalona - Practice | discord.gg/ACrk2wG | 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
Practice Races Laguna Seca
23.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 4 Laguna seca - Practice | discord.gg/ACrk2wG | Results |
23.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 4 Laguna Seca - Practice | discord.gg/ACrk2wG | Results |
24.05.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 4 Laguna Seca - Practice | discord.gg/ACrk2wG | Results |
24.05.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 4 Laguna Seca - Practice | discord.gg/ACrk2wG | Results |
Race info
Race length: | 60 minutes |
Mandatory pit-stop(s): | 1 |
Mandatory tire change: | Yes |
Mandatory refueling: | No |
Refueling allowed: | No |
Weather forecast
44% dry |
56% wet |
57% changing conditions |
Server Json
Practice Races Bathurst Mount Panorama
06.06.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 5 Bathurst Mount Panorama - Practice | discord.gg/ACrk2wG | Results |
06.06.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 5 Bathurst Mount Panorama - Practice | discord.gg/ACrk2wG | Results |
07.06.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 5 Bathurst Mount Panorama - Practice | discord.gg/ACrk2wG | Results |
07.06.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 5 Bathurst Mount Panorama - Practice | discord.gg/ACrk2wG | 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
Practice Races Zolder
13.06.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 6 Zolder - Practice | discord.gg/ACrk2wG | Results |
13.06.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 6 Zolder - Practice | discord.gg/ACrk2wG | Results |
14.06.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 6 Zolder - Practice | discord.gg/ACrk2wG | Results |
14.06.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 6 Zolder - Practice | discord.gg/ACrk2wG | Results |
Race info
Race length: | 90 minutes |
Mandatory pit-stop(s): | 1 |
Mandatory tire change: | No |
Mandatory refueling: | No |
Refueling allowed: | Yes |
Weather forecast
19% dry |
81% wet |
81% changing conditions |
Server Json
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
Practice Races Silverstone
27.06.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 8 Silverstone - Practice | discord.gg/ACrk2wG | Results |
27.06.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 8 Silverstone - Practice | discord.gg/ACrk2wG | Results |
28.06.2021 18:30 UTC | ApexOnline.Racing #6 | GT3 Season 3 - Round 8 Silverstone - Practice | discord.gg/ACrk2wG | Results |
28.06.2021 18:30 UTC | ApexOnline.Racing #7 | GT3 Season 3 - Round 8 Silverstone - Practice | discord.gg/ACrk2wG | Results |
The leagues on each platform (within each region) are organised in a tier structure.
- 1.1 Driver placements
-
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 hot stint 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 a full grid of 30-45 drivers to be racing at the same time. A more precise amount will be known when the placements are published.
Note: Drivers who missed a significant number of races in previous seasons may be placed as a reserve driver.
-
- 1.2 Joining mid-season
-
It is possible for new drivers to sign up while the season is ongoing. They will still have to complete the steps on the sign-up website (sign up, hot-stint and evaluation race) and will then be placed into an appropriate tier based on their pace. However, drivers will only be able join a tier mid-season as a main driver if there is a space available. If there isn't, they will be placed into the tier as a reserve driver until a space opens.
-
- 1.3 Reserve drivers
-
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 who are inactive for a lengthy period of time (eg. frequently not being available to fill no-shower spots 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 most active reserves, the reserve who signed up earliest will be allowed to fill the empty spot.
-
- 1.4 Mid-season driver moves
-
Drivers may be moved between tiers while the season is ongoing if it's clear they have been misplaced. This could be that they are clearly too fast for their split, or that they are unable to experience close racing due to being too slow.
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 leagues 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.5 Switching cars
-
Drivers are allowed to change the car they drive, but they may only do so just once during the season. Changing car automatically means your championship points will be reset to zero.
-
- 2.1 Points system
-
The following points will be scored for each race finishing position.
1st = 50 points
2nd = 45 points
3rd = 40 points
4th = 36 points
5th = 32 points
6th = 29 points
7th = 26 points
8th = 23 points
9th = 20 points
10th = 17 points
11th = 15 points
12th = 13 points
13th = 11points
14th = 9 points
15th = 7 points
16th = 6 points
17th = 5 points
18th = 4 points
19th = 3 points
20th = 2 points
-
- 2.2 DSC
-
A driver who disconnects at any stage of the race, may rejoin the game session and carry on racing (he/she will be ## laps down) If you retire to the pits you may also rejoin the race (## laps down). If you do DSC and do not rejoin the race then you will not score points and will be classified as DSC (Disconnected) in the race results (please remember if you do rejoin you will be laps down and the cars in front have priority).
-
- 2.3 DNF
-
Drivers who complete less than 90% 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.
-
- 2.4 DSQ
-
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.
-
- 2.5 DNS
-
Active league drivers who did not attend the race will be classified as DNS (Did Not Start), and will not score any points.
-
- 2.6 Championship standings
-
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 the holder of most first places. If the number of first places is the same, the holder of most second places, then third places and so on until a winner emerges.
At the end of the season, results of all races count.
-
- 3.1 Disconnections
-
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.
-
- 3.2 Mass disconnections
-
During 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 40% of the race was completed at the time of the mass disconnection, the race will be restarted as soon as possible.
- If more than 40% of the race was completed at the time of the mass disconnection, the race will end, and the race will be postponed.
-
- 3.3 Postponing a race
-
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.
-
For league related enquiries or questions, your first point of contact should be a staff member within the tier you are assigned to. Upon joining a league, it will be made clear who your tier's coordinators are.
Example reasons to contact them could be:
โ To get information about your tier
โ To ask questions related to the league
โ If you are unhappy about something, either with regards to a race or something on the forums
If you have an issue with your coordinator and would rather discuss the issue with someone else, then seek out another person from the below list 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.
The following members are currently part of the team running the AOR ACC Leagues:
PlayStation Coordinators:
Benji_racing
Hygrade B
Jazzman7709879
PRG_FrankForest
Example reasons to contact them could be:
โ To get information about your tier
โ To ask questions related to the league
โ If you are unhappy about something, either with regards to a race or something on the forums
If you have an issue with your coordinator and would rather discuss the issue with someone else, then seek out another person from the below list 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.
The following members are currently part of the team running the AOR ACC Leagues:
PlayStation Coordinators:
Benji_racing
Hygrade B
Jazzman7709879
PRG_FrankForest
- 5.1 Hotstint(s)
-
New drivers now have to complete a hotstint on both Nรผrburgring and Suzuka. Returning drivers only have to complete a hotstint on Suzuka (and can improve last season's Nรผrburgring hotstint if they want).
-
- 5.2 License points penalties
-
The 25 license points for getting an qualification ban is being lowered to 15 license points.
-
- 5.3 Formation lap
-
Full formation lap will be used instead of the short formation lap.
-
- 5.4 Completing races
-
To be eligible for being classified for points you now need to have at least completed 90% of the race.
-
- 5.5 Creating teams
-
Teams can now be created for two drivers in the same tier, while racing in a different car brand.
-
- 5.6 Spacial awareness
-
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.
-
- 5.7 Mass disconnections
-
The 50% rule for what to do with an mass disconnect have been changed to 40%.
-
- 6.1 Who needs to do the hotstint
-
Drivers who did not participate in Season 2 will need to complete two hotstints - Nรผrburgring and Suzuka.
Returning drivers from Season 2 only have to do the Suzuka hotstint.
-
- 6.2 Submitting your hotstint
-
You can submit your hotstint by editing your sign up info on the website and click the Hotstint box at the top.
Once you have submitted the information an coordinator will check the info and will approve or decline the hotsint. When it is approved you will see a checkmark with the information "time validated".
In case you have improved your time you can re-submit your information by clicking the upload button.
Example of the picture you need to upload on the website
-
- 6.3 Nürburgring settings
-
Track: Nรผrburgring
Game Mode:
Hotstint Time: 14:00
Stint length: 10min
Time Multiplier: x1
Weather & Track conditions:
Clear
Dynamic weather: Disabled
Grip Level: Optimum
Screenshot of the settings:
-
- 6.4 Suzuka settings
-
Track: Suzuka
Game Mode:
Hotstint Time: 14:00
Stint length: 10min
Time Multiplier: x1
Weather & Track conditions:
Clear
Dynamic weather: Disabled
Grip Level: Optimum
Screenshot of the settings:
-
- 1.1 Clean racing
- 1.1.1Race 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.2Deliberately crashing into another car will result in being permanently excluded from our ACC leagues and events.
- 1.1.3If 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.1Don'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.2Overtaking 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.1Dangerous 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.2Do 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.1Stay 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.2If 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.3The 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 this puts you at the risk of being penalised in game, however if it fails to penalise you, an enquiry can be opened for the stewards to review.
- 1.4.4If 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.1In 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 Spacial Awareness
- 1.6.1If 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.2If 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.3Using 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.4In 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 will 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.1Cars 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.2Every 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.3A car is considered to be in the pit exit or entry zone when all four wheels are within the white lines.
- 1.7.4Once 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.5Use 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.1We 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.2As 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.3If 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.1Stay 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.2A 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.3A 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.1For 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.2The above rule about having headlights on also applies to running in the fog and in the rain.
- 2.3.3During rainy conditions, having the rain lights turned on is mandatory.
- 2.3.4For 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 respect and 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.1In 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.2Any incidents happening before the restart, are still reportable and will be looked at by the stewards.
- 3.1 Communication
- 3.1.1A driver briefing can be done in the tier channel on Discord by the coordinator. This depends on what the coordinator prefers and the coordinator will announce it before the start of the season.
- 3.1.2Not being up to date due to not reading the tier channel in Discord, cannot be used as an excuse.
- 3.1.3PSN leagues have access to the Discord server, which acts as one of the official communication platforms in AOR.
- 3.2 Lobby etiquette
- 3.2.1Shouting, 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.2Respect 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.3Respect 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.1If 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.2If 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.3If 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.4Wait 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.5The 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.6Penalties 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.1Deliberately 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.2Excuses 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.3Connection 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.4Repeatedly quitting the race before it has finished, gives your 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 Forums and Discord
- 3.5.1You will need an account on the AOR forums and you'll also 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.2You 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 90% of the race. The amount of laps the winner of the race drove, is considered to be 100%.
- 4.2 Missing races
- 4.2.1If 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.2When 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 are required to regularly race on race day as part of the sign-up process.
- 4.2.3As 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.4If 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.5The 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.6Getting 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.
- 4.4 Pulling out mid-season
- 4.4.1Commitment 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.2It'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.3If 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.4Note 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
- The Stewards Panel on the AOR forum will be used to review the incidents.
https://apexonlineracing.com/community/forums/stewards-enquiries-gt3-ps4.1839/
- 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.1The Stewards Panel forum 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.2What 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.3Time 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.4Uploading 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.1The 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-5 race results points reduction - Driving in a dangerous or unsporting manner.
0-20 race results points reduction - Causing a minor avoidable collision.
0-30 race results points reduction - Causing a moderate avoidable collision.
0-40 race results points reduction - Causing a significant avoidable collision.
0-50 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.2Modifiers 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.1The 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.2Modifiers to Driverโs License Penalties: +5 points - Causing an avoidable incident in the opening lap
- 5.5.3Clean Racing Award: -5 points - Completing a race without any penalty. (Note: points balance won't go below 0)
- 5.5.4Driverโs License accumulations:
If you accumulate 15 points, you will be awarded a qualifying ban
If you accumulate 40 points, you will be awarded 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 - 5.5.5Driverโs License points will carry over to a new season
- 5.5.6Any 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 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're out. 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.7 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.
In-game name | PS Network ID | Discord name | Social | Car | Number | |
---|---|---|---|---|---|---|
Matt - | Ix_unforg1v3n_xI | @Matt_aka_unforg1v3n | BMW M6 GT3 (2017) | 206 | ||
Kim-David Merckens | Violent_S15 | @93kimdavidmerckens | Mercedes-AMG GT3 (2020) | 93 | ||
Olivier Charbonneau | op2873 | @op2873 | Audi R8 LMS Evo (2019) | 33 | ||
Lucas Morato | lm3377 | @luksy | Ferrari 488 GT3 (2015) | 69 | ||
Joe Reed | zJReedy | @zJReedy | Lamborghini Huracan GT3 Evo (2019) | 78 | ||
Melvin Van de Kerckhove | Floesmyn | @Melvin Van de Kerckhove | Ferrari 488 GT3 Evo (2020) | 14 | ||
Johnny Medrala | Johnny-Medrala | @Johnny-Medrala ๐ฉ๐ฐ | Ferrari 488 GT3 Evo (2020) | 2 | ||
Fabian Radeck | doquno | @doquno | Ferrari 488 GT3 Evo (2020) | 111 | ||
Benji McCluskey | Boy_RaXer14 | @benji_racing | Porsche 991 II GT3 R (2019) | 28 | ||
Luca Voncken | Enten_Salat_33 | @Luca33 | Bentley Continental GT3 (2018) | 133 | ||
AVinto7 | AVinto7 | @AVinto7 | Porsche 991 II GT3 R (2019) | 7 | ||
Kallo_Ferenc Kalló Ferenc | Kalló Ferenc | @Kalló Ferenc | Ferrari 488 GT3 Evo (2020) | 87 | ||
Peter Vidovics | SMT_Boardman | @Peter Vidovics | Bentley Continental GT3 (2018) | 33 | ||
Shane Taylor | Shamma69 | @Shamma | BMW M6 GT3 (2017) | 69 | ||
SMT_ Zoloba | SMT_Zoloba | @zoloba73 | Mercedes-AMG GT3 (2020) | 73 | ||
Eduardo Gonzaga | Eddie_cwb07 | @ERT_Eddie | Bentley Continental GT3 (2018) | 92 | ||
Marc Tol | Stitch5yy024 | @Stitch5yy024 | McLaren 720S GT3 (2019) | 24 | ||
Erik Ga | Raiker_chu | @Raiker_chu | Ferrari 488 GT3 Evo (2020) | 25 | ||
Tamás Suvada | Slow_wolf1 | @slow_wolf1 | Mercedes-AMG GT3 (2020) | 43 | ||
Csaba Szuh | F1HL_SMT_ifjszcs | @szuhcsaba | Bentley Continental GT3 (2018) | 27 | ||
Joris Schmidt | GH0ST_SCHMIDT12 | @MRL_GH0ST | AMR V8 Vantage (2019) | 98 | ||
Fozzy12 | Fozzy12 | @Fozzie_Bear | Bentley Continental GT3 (2018) | 6 | ||
Jeffrey van Buuren | Bigjeff1982_ | @jeffreybigjeff1982_ | Ferrari 488 GT3 Evo (2020) | 187 | ||
Stuart Pietzka | Stuart_pietzka | @ccfc_stu | AMR V8 Vantage (2019) | 81 | ||
Emre Ates | emreates_ | @EmreAtes | Porsche 991 II GT3 R (2019) | 759 | ||
yellow-army84 | yellow-army84 | @yellowarmy84 | Ferrari 488 GT3 (2015) | 11 | ||
Ediz Olcum | ediz-olcum | @Ediz Olçum | Audi R8 LMS Evo (2019) | 13 | ||
Robert Sundqvist | YabbaTheHutt | @YabbaTheHutt (Robert Sundqvist) | Lexus RC F GT3 (2016) | 720 | ||
Mario De paz | Mariodep097 | @STDRS_mariodepaz97 | Lamborghini Huracan GT3 Evo (2019) | 22 | ||
MVP_CORNERCRACK_ | MVP_CORNERCRACK_ | @M.Bielitza | McLaren 720S GT3 (2019) | 420 | ||
EarlyTerrorSpons | EarlyTerrorSpons | @EarlyTerrorSpons | Audi R8 LMS Evo (2019) | 909 | ||
Pascal Nooy | Lacsap-Yoon | @lacsapyoon | Ferrari 488 GT3 Evo (2020) | 13 | ||
Thomas Walsh | Thomasw769 | @Thomasw769 | Lamborghini Huracan GT3 Evo (2019) | 17 | ||
Chris Rode | Dive_Bomber52 | @Dive_Bomber52 | Mercedes-AMG GT3 (2020) | 52 | ||
Aidan Urquhart | shmaids | @shmaids | Ferrari 488 GT3 (2015) | 46 | ||
Michael Barnard | Pharmar | @pharmar | AMR V8 Vantage (2019) | 17 | ||
Fred Ogega [FFR] | PRG_FredOgega | @fred_ogega | Bentley Continental GT3 (2018) | 27 | ||
PorcaVacca_91 PorcaVacca_91 | PorcaVacca_91 | @PorcaVacca_91 | Lamborghini Huracan GT3 Evo (2019) | 9 | ||
denisdowntown28 | denisdowntown28 | @denisdowntown28 | Ferrari 488 GT3 Evo (2020) | 92 | ||
F Reggel | Freggelrock | @freggel | Lexus RC F GT3 (2016) | 55 | ||
BMTM_Shifter | BMTM_Shifter | @BMTM_Shifter | Bentley Continental GT3 (2018) | 367 | ||
Scott Fell | S-FELL-89 | @scottfell | Bentley Continental GT3 (2018) | 89 | ||
Scott McCallum | Chizubaga | @_chizubaga | Bentley Continental GT3 (2018) | 333 | ||
Dan Dyson | golzy | @golzy | Porsche 991 II GT3 R (2019) | 20 | ||
Meester Bond | Meester_Bond_WHG | @meester.bond.whg | Bentley Continental GT3 (2018) | 7 | ||
Valbuena39_ | Valbuena39_ | @Valbuena39_ (ะฎัะฐ) | Mercedes AMG GT3 (2015) | 20 | ||
Toby Classic | TobyclassicGB | @Tobyclassic | Bentley Continental GT3 (2018) | 76 | ||
Fot79 | Fot_79 | @Fot_79 ๐ฎ๐น | Ferrari 488 GT3 Evo (2020) | 51 | ||
Rodion Sorokin | RedBullEnergyyy | @redbullenergy | McLaren 720S GT3 (2019) | 14 | ||
Juustokeisari | Juustokeisari | @Juustokeisari | Porsche 991 II GT3 R (2019) | 60 | ||
Wikinico . | wikinico | @wikinico | McLaren 720S GT3 (2019) | 12 | ||
Brandon Haigh | CRN_Haighy | @CRN_Haighy | Audi R8 LMS Evo (2019) | 96 | ||
DgC_Gehrig | DgC_Gehrig | @DgC_Gehrig | Ferrari 488 GT3 Evo (2020) | 369 | ||
Andrew Terehov | SirTerehov | @Sir.Terehov | McLaren 720S GT3 (2019) | 347 | ||
Connor Byers | ART_Connor_74 | @art_connor_74 | Mercedes-AMG GT3 (2020) | 74 | ||
Schnixel | Schnixel | @Schnixel | Ferrari 488 GT3 Evo (2020) | 42 | ||
Ben Milden | SOP_MILDEN | @ | Bentley Continental GT3 (2018) | 111 | ||
JR-Lock-N-Load (Junior) | JR-Lock-N-Load | @junior212 | McLaren 720S GT3 (2019) | 212 | ||
Duncan Bell | kevlar-hybrid | @kevlar-hybrid | Ferrari 488 GT3 Evo (2020) | 74 | ||
Petr Postl | Petr_Postl | @Petr_ Postl | Ferrari 488 GT3 Evo (2020) | 68 | ||
Nikolay Burykin | Nike_r_OK | @nikerok | Bentley Continental GT3 (2018) | 795 | ||
TheTubbyNinja | TheTubbyNinja | @TheTubbyNinja | McLaren 720S GT3 (2019) | 29 | ||
Vitaliy Uvarov | Vitalycrash | @Vitaliy_Uvarov | McLaren 720S GT3 (2019) | 7 | ||
Igor Paramonov | Igor_Param | @Igor Paramonov | McLaren 720S GT3 (2019) | 51 | ||
Sam Birch | Flabbs | @Flabbs | McLaren 720S GT3 (2019) | 13 | ||
Anthony Pickthall | Anthos77 | @Anthos77 | Lexus RC F GT3 (2016) | 77 | ||
Constantin Kampik | CoKa_Original | @consti0507 | Mercedes-AMG GT3 (2020) | 101 | ||
Tom Griffiths | tomji_ | @tomji_ | Ferrari 488 GT3 Evo (2020) | 14 | ||
Vlad Kucher | Warlord_3099 | @warlord39 | Bentley Continental GT3 (2018) | 39 | ||
surelook_ | surelook_ | @surelook | Nissan GT R Nismo GT3 (2018) | 23 | ||
Toni Hermoso | Nitoher72 | @Nitoher72(PS4) | AMR V8 Vantage (2019) | 33 | ||
Kris Egert Rünkjanen | Mcquiz95 | @mcquiz95 | Lamborghini Huracan GT3 Evo (2019) | 25 | ||
Vincent Draijer | VuNcE13 | @vunce_0000 | Audi R8 LMS Evo (2019) | 13 | ||
Frank Forest [FFR] | PRG_FrankForest | @fsr_frankforest | Bentley Continental GT3 (2018) | 61 | ||
Carlos Mezouar | carlos2008nc | @carlitus93 | McLaren 720S GT3 (2019) | 22 | ||
Manu Prieto | mprietod | @Manu Prieto | Porsche 991 II GT3 R (2019) | 73 | ||
Tobias Pulsford | Tobyheokxx | @Tobyhoekx | Bentley Continental GT3 (2018) | 33 | ||
Michael Cameron | michaeljc53 | @michaeljc53 | Ferrari 488 GT3 Evo (2020) | 53 | ||
Dimitris Petropoulos | KillCity_GR27 | @KillCity_GR27 | McLaren 720S GT3 (2019) | 720 | ||
Adam Kaczalski | CSR_Kaczalski | @kaczalski | Lexus RC F GT3 (2016) | 777 | ||
chris davidson | chris130256 | @chris130256 | Bentley Continental GT3 (2018) | 13 | ||
McGrady | VP_McGrady | @vp_mcgrady | Bentley Continental GT3 (2018) | 34 | ||
Tomas Cisar | Tomas_Cezar | @Tomas__Cisar | Mercedes-AMG GT3 (2020) | 27 | ||
Refr4ct | R3FR4CT_ | @refr4ct | Lexus RC F GT3 (2016) | 30 | ||
marco1997mnm . | marco1997mnm | @Marco97 | Ferrari 488 GT3 Evo (2020) | 222 | ||
Adam_YNWA_foster | Adam_YNWA_foster | @ | McLaren 720S GT3 (2019) | 28 | ||
Diogo Pinto | Bgsgsdegha | @Bgsgsdegha | Lamborghini Huracan GT3 Evo (2019) | 15 | ||
Alex van Keulen | Trucker-Lex93 | @Lexie1993Maxie | Audi R8 LMS Evo (2019) | 99 | ||
Arthur Mr__Fugu | Mr__Fugu | @Gamernia | Ferrari 488 GT3 Evo (2020) | 34 | ||
Klst55 | Kslt55 | @kslt | Lexus RC F GT3 (2016) | 55 | ||
NathBit | NathBit | @NathBit | AMR V8 Vantage (2019) | 14 | ||
Jamie Rees | Jinx98765 | @jamie_sbr108 | AMR V8 Vantage (2019) | 189 | ||
Marco Locatelli | lokka09 | @Lokka09 | Mercedes-AMG GT3 (2020) | 22 | ||
Frederic Ponsard | iDrasnop | @idrasnop | Mercedes-AMG GT3 (2020) | 124 | ||
Jean-Marie Ponsard | eCaptainKirk | @ecaptainkirk | Lexus RC F GT3 (2016) | 123 | ||
DriveOfAgony | DriveOfAgony | @DriveOfAgony | Lamborghini Huracan GT3 Evo (2019) | 504 | ||
Neez84 | neez84 | @n33za | Ferrari 488 GT3 Evo (2020) | 67 | ||
Steven Archibald | Archie619 | @archie619 | Lexus RC F GT3 (2016) | 619 | ||
Will Friedmann | Will-Friedmann | @๐๐๐๐ ๐ฝ๐ฃ๐๐๐๐๐๐๐ | Ferrari 488 GT3 Evo (2020) | 8 | ||
Jeroen81 | JeroenG81 | @jeroeng81 | Ferrari 488 GT3 Evo (2020) | 81 | ||
EMR_ TxeliGSI | EMR_TxeliGSI | @Moon_AAndres | McLaren 720S GT3 (2019) | 3 | ||
Lsd_high321 | Lsd_high321 | @lsd_high321 | Bentley Continental GT3 (2018) | 69 | ||
Anders Prehn | Prehn | @.prehn | McLaren 720S GT3 (2019) | 9 | ||
Toby Atkinson | CSR_schwantz34 | @Tj Atk | Mercedes-AMG GT3 (2020) | 112 | ||
Dave Trapani | DAVEJ2013 | @davej2013 | Bentley Continental GT3 (2018) | 53 | ||
silver fox | silverfox5910 | @silverfox7240 | Ferrari 488 GT3 Evo (2020) | 11 | ||
Matthew Asbreuk | MatthewAsbreuk | @matthew010383 | Ferrari 488 GT3 Evo (2020) | 83 | ||
Daniel Okken | Flipping83 | @DAO_Flipping83 | Ferrari 488 GT3 Evo (2020) | 7 | ||
Mattiep9017 | Mattiep9017 | @Mattiep9017 | Lexus RC F GT3 (2016) | 188 | ||
C_Leclerc_ | C_Leclerc_ | @C_Leclerc_ | McLaren 720S GT3 (2019) | 16 | ||
Nemanja Markicevic | Markicevicus93 | @Markicevic | Ferrari 488 GT3 Evo (2020) | 11 | ||
Craig Ward | Wardy636 | @wardy636(๐๐) | McLaren 720S GT3 (2019) | 636 | ||
Luche109 | Luche109 | @Luche109 | Ferrari 488 GT3 Evo (2020) | 109 | ||
Manuel Düchs | @duce381 | Bentley Continental GT3 (2018) | 7 | |||
Devils Armpit666 | Devilsarmpit666 | @devilsarmpit666 | Lexus RC F GT3 (2016) | 666 | ||
Graham Day | Sneaky24-7Ninja | @sneaky24_7ninja | McLaren 720S GT3 (2019) | 15 | ||
Graham Potter | Rotters91 | @rotters91 | Bentley Continental GT3 (2018) | 91 | ||
Richard Wilson | RSlicker | @slicker_xvr | Bentley Continental GT3 (2018) | 59 | ||
Sergey Kiselev | SV_Kiselev | @Svkiselev | Audi R8 LMS Evo (2019) | 34 | ||
Coldtyre | Coldtyre | @Coldtyre | Honda NSX GT3 Evo (2019) | 99 | ||
Michael Coppens | neonostra | @neonostra | Ferrari 488 GT3 Evo (2020) | 36 | ||
Mark Lessen | flawed_algorithm | @flawed_algorithm | Ferrari 488 GT3 Evo (2020) | 78 | ||
CHFALCKNER | CHFALCKNER | @CHFALCKNER | Ferrari 488 GT3 Evo (2020) | 71 | ||
FLY SKY | FLYSKYDHK | @FLYSKYDHK | Ferrari 488 GT3 Evo (2020) | 99 | ||
Tiago Cruz | crukip | @tiago_cruz | Bentley Continental GT3 (2018) | 16 | ||
K Barrett | Hygrade_B_876 | @hygradeb876 | Bentley Continental GT3 (2018) | 876 | ||
Marty VR | Marty-VR | @martyvr. | Bentley Continental GT3 (2018) | 10 | ||
Daniel Dye | DJDCleanShirt | @DJDCleanShirt | Lexus RC F GT3 (2016) | 23 | ||
Spenced_7 | Spenced_7 | @Spenced_7 | Mercedes-AMG GT3 (2020) | 17 | ||
Jay Fraan | fraantje | @fraantje | Mercedes-AMG GT3 (2020) | 4 | ||
jawaite | jawaite | @jawaite | AMR V8 Vantage (2019) | 68 | ||
Dan Barnard | B4RN3Y__87 | @b4rn3y87 | Ferrari 488 GT3 Evo (2020) | 87 | ||
Sean Coull | COULL444RACING | @coull444racing | Mercedes-AMG GT3 (2020) | 14 | ||
Shurland George | WRC_madmax | @shurland_george | Ferrari 488 GT3 Evo (2020) | 868 | ||
M20PCD | M20PCD | @m20pcd | AMR V8 Vantage (2019) | 69 | ||
Bjorn Stomberg | KentFusag | @Fusag | McLaren 720S GT3 (2019) | 222 | ||
Jordan Barker | jsbarker95 | @barker95 | AMR V8 Vantage (2019) | 24 | ||
Alen Bardet | AlbertDeanI | @AlbertDeanI | Ferrari 488 GT3 Evo (2020) | 80 | ||
AnAngryPidgeon | AnAngryPidgeon | @AnAngryPidgeon | Bentley Continental GT3 (2018) | 21 | ||
Leon Sealy | Leonmsealy | @leonmsealy | Ferrari 488 GT3 Evo (2020) | 246 | ||
Dan Ayres | Ayresii1995 | @ayresii1995 | Bentley Continental GT3 (2018) | 888 | ||
Danny Zoutenbier | Zout_101 | @dannyzout_101 | Bentley Continental GT3 (2018) | 7 | ||
Chris Jones | Essaracin | @Essa28_FSR | Ferrari 488 GT3 Evo (2020) | 28 | ||
Martijn Huijerjans | tinus_in_da_haus | @bodhie | Bentley Continental GT3 (2018) | 13 | ||
opentheirminds | opentheirminds | @Opentheirminds | McLaren 720S GT3 (2019) | 17 | ||
Jarryd Vermeulen | Jazzman77709876 | @jazzman77709876 | Bentley Continental GT3 (2018) | 14 | ||
Davey Zout | DaveyZout | @daveyzout | Lamborghini Huracan GT3 Evo (2019) | 84 |
Once tiers have been announced you can create a team to compete in the optional team championship.
Teams must consist of 0 drivers.
The deadline for creating a team is before race 2 of the season
Teams must consist of 0 drivers.
The deadline for creating a team is before race 2 of the season