F1 Season 22 MAIN
Apex Online Racing
League Information
Signups closed
Signup:
17.07.2021 - 06.08.2021
Season period:
15.08.2021 - 19.12.2021
Evaluation races:
20.07.2021 19:00 UTC
22.07.2021 19:00 UTC
24.07.2021 19:00 UTC
25.07.2021 19:00 UTC
28.07.2021 19:00 UTC
31.07.2021 19:00 UTC
04.08.2021 19:00 UTC
General Information:
SIGN UPS RE-OPEN AFTER ROUND 1
- You must create a forum account across at apexonlineracing.com/community . You will need this for any potential stewards enquiries.
- The Stewards Panel can be found here.
- To help the AOR staff out when placing drivers into leagues, please can your forum / discord name match your gamertag / Steam ID.
- Join our Discord: https://discord.gg/BDEt39h
- League structure: Each platform and region runs a set amount of leagues, depending on the amount of drivers signing up at the start of the season. The leagues are tiered, with the aim to have the faster drivers in the higher leagues and the slower drivers in the lower leagues.
- Regions: Separate league structures will be available for the Europe and American regions. Drivers are allowed to take part in the leagues for a region as long as their connection is suitable enough towards that region.
- Assists: In the main European leagues, the top league tiers will have all driving assists banned. There will be assist leagues for all those using any assist.
- Driver placements: Drivers will be placed in an appropriate league based on their time trial times, their performances in the evaluation race, and their performance in the previous league season (for drivers who raced in Season 21). Drivers who missed a significant number of races in Season 21 may be placed as reserves. Only new drivers require to complete an evaluation race.
- Race format: Each race event features an 18-minute qualifying session followed by a 50% distance race. (100% for alternate layouts
- Day/time: League events will take place on Sunday nights from 8:00pm (UK time for Europe, Eastern time for America).
- Notable Dates:
- Sign-up & time trial opens: 17th July 2021
- Sign-up & time trial closes: 6th August 2021
- Evaluation race date(s): 20th July, 22nd July, 24th July, 25th July, more TBD
- Driver placement announcement: 11th August 2021
- Car selection begins: upon sign up
- Season begins: 15th August 2021
- Season ends: 19th December 2021
# | Driver | Best Overall | Spain | Car | Great Britain | Car | Valid |
---|---|---|---|---|---|---|---|
1 | Fehler3 | 02:38.809 | 01:14.177 | 01:24.632 | |||
2 | @Tobi π | 02:38.860 | 01:14.168 | 01:24.692 | |||
3 | Azure | 02:39.190 | 01:14.452 | 01:24.738 | |||
4 | BallakSenior95 | 02:39.265 | 01:14.386 | 01:24.879 | |||
5 | Daniel | 02:39.397 | 01:14.258 | 01:25.139 | |||
6 | @Patrick16 | 02:39.487 | 01:14.334 | 01:25.153 | |||
7 | AtrocityZA | 02:39.489 | 01:14.528 | 01:24.961 | |||
8 | Tim Roelleke | 02:39.580 | 01:14.643 | 01:24.937 | |||
9 | FVR Darn | 02:39.610 | 01:14.562 | 01:25.048 | |||
10 | [COR] F1Racer29 | 02:39.647 | 01:14.588 | 01:25.059 | |||
11 | ripsn | 02:39.651 | 01:14.511 | 01:25.140 | |||
12 | Tudor | 02:39.662 | 01:14.604 | 01:25.058 | |||
13 | Simon Nyznyk | 02:39.723 | 01:14.569 | 01:25.154 | |||
14 | Rivershan | 02:39.737 | 01:14.607 | 01:25.130 | |||
15 | Kevgenetics | 02:39.737 | 01:14.666 | 01:25.071 | |||
16 | @Tom Danel π«π· | 02:39.804 | 01:14.622 | 01:25.182 | |||
17 | Sauerbraten | 02:39.812 | 01:14.586 | 01:25.226 | |||
18 | TTV/TRL__MinTy | 02:39.820 | 01:14.862 | 01:24.958 | |||
19 | @Juca | 02:39.822 | 01:14.626 | 01:25.196 | |||
20 | donuthole | 02:39.873 | 01:14.694 | 01:25.179 | |||
21 | @FeelRacing_Seb | 02:39.909 | 01:14.579 | 01:25.330 | |||
22 | Hy77inen | 02:39.928 | 01:14.755 | 01:25.173 | |||
23 | Pulkkkis | 02:40.006 | 01:14.595 | 01:25.411 | |||
24 | RichyB | 02:40.006 | 01:14.845 | 01:25.161 | |||
25 | lior.z | 02:40.040 | 01:14.928 | 01:25.112 | |||
26 | Potato06 | 02:40.063 | 01:14.727 | 01:25.336 | |||
27 | Matti_29 | 02:40.117 | 01:14.775 | 01:25.342 | |||
28 | Persegeeli | 02:40.125 | 01:14.789 | 01:25.336 | |||
29 | ZaneFast | 02:40.162 | 01:14.861 | 01:25.301 | |||
30 | iBlue | 02:40.178 | 01:14.774 | 01:25.404 | |||
31 | Ved | 02:40.186 | 01:14.939 | 01:25.247 | |||
32 | BeBix | 02:40.188 | 01:14.911 | 01:25.277 | |||
33 | tYsU^ | 02:40.247 | 01:14.909 | 01:25.338 | |||
34 | matrixschlange | 02:40.284 | 01:14.935 | 01:25.349 | |||
35 | TheGaffa | 02:40.311 | 01:14.864 | 01:25.447 | |||
36 | Pezi | 02:40.314 | 01:14.990 | 01:25.324 | |||
37 | Vaga® | 02:40.317 | 01:14.958 | 01:25.359 | |||
38 | Yohann | 02:40.320 | 01:14.857 | 01:25.463 | |||
39 | [FcT] Nevo | 02:40.322 | 01:14.940 | 01:25.382 | |||
40 | Boris_ | 02:40.384 | 01:14.781 | 01:25.603 | |||
41 | strusieek | 02:40.431 | 01:15.146 | 01:25.285 | |||
42 | The AM | 02:40.445 | 01:15.138 | 01:25.307 | |||
43 | GalaXxy_RD | 02:40.454 | 01:15.042 | 01:25.412 | |||
44 | RMate | 02:40.574 | 01:15.094 | 01:25.480 | |||
45 | do1mi8nik | 02:40.577 | 01:15.072 | 01:25.505 | |||
46 | Ioseba Solís | 02:40.580 | 01:15.001 | 01:25.579 | |||
47 | Der_Kaya@Twitch | 02:40.583 | 01:15.018 | 01:25.565 | |||
48 | GuilMauv | 02:40.608 | 01:14.977 | 01:25.631 | |||
49 | VegaZ | 02:40.690 | 01:15.055 | 01:25.635 | |||
50 | Keystone1976 | 02:40.700 | 01:15.111 | 01:25.589 | |||
51 | GluecksBirne | 02:40.703 | 01:15.286 | 01:25.417 | |||
52 | Tom Frank | 02:40.703 | 01:15.275 | 01:25.428 | |||
53 | @Nikolay | 02:40.738 | 01:15.354 | 01:25.384 | |||
54 | RockyOoze | 02:40.739 | 01:15.140 | 01:25.599 | |||
55 | @YouSeven | 02:40.750 | 01:15.264 | 01:25.486 | |||
56 | FcT Daigoro | 02:40.792 | 01:15.226 | 01:25.566 | |||
57 | Hopey | 02:40.803 | 01:15.308 | 01:25.495 | |||
58 | SkyKartoffel | 02:40.824 | 01:15.165 | 01:25.659 | |||
59 | STINGY RING | 02:40.839 | 01:15.434 | 01:25.405 | |||
60 | Mtw1man2 | 02:40.842 | 01:15.238 | 01:25.604 | |||
61 | Finnsen | 02:40.860 | 01:15.344 | 01:25.516 | |||
62 | @sp3ed9 | 02:40.872 | 01:15.213 | 01:25.659 | |||
63 | ReCreight | 02:40.880 | 01:15.255 | 01:25.625 | |||
64 | Creepydrive | 02:40.908 | 01:15.317 | 01:25.591 | |||
65 | ZOR_MrJoshua | 02:40.918 | 01:15.250 | 01:25.668 | |||
66 | @Sulphix | 02:40.994 | 01:15.260 | 01:25.734 | |||
67 | ScraG | 02:41.006 | 01:15.244 | 01:25.762 | |||
68 | Tagnemon | 02:41.039 | 01:14.969 | 01:26.070 | |||
69 | cyeardly | 02:41.136 | 01:15.435 | 01:25.701 | |||
70 | Kiinako_ | 02:41.171 | 01:15.377 | 01:25.794 | |||
71 | Shift4 | 02:41.178 | 01:15.346 | 01:25.832 | |||
72 | SPE | Varga Balázs | 02:41.209 | 01:15.270 | 01:25.939 | |||
73 | LuDAMer22 | 02:41.364 | 01:15.775 | 01:25.589 | |||
74 | bartaaron04 | 02:41.368 | 01:15.548 | 01:25.820 | |||
75 | RampageJackson | 02:41.381 | 01:15.516 | 01:25.865 | |||
76 | [MRL] Mulchian | 02:41.393 | 01:15.572 | 01:25.821 | |||
77 | JTREY 1 | 02:41.408 | 01:15.600 | 01:25.808 | |||
78 | V8_Visquin | 02:41.412 | 01:15.756 | 01:25.656 | |||
79 | CHERNOSHTANOV | 02:41.419 | 01:15.583 | 01:25.836 | |||
80 | Gar3d | 02:41.421 | 01:15.656 | 01:25.765 | |||
81 | Leonard | 02:41.552 | 01:15.766 | 01:25.786 | |||
82 | twitch.tv/exodium | 02:41.590 | 01:15.761 | 01:25.829 | |||
83 | TWLinkerbaan | 02:41.629 | 01:15.711 | 01:25.918 | |||
84 | szollosiati | 02:41.630 | 01:15.728 | 01:25.902 | |||
85 | greenamit | 02:41.645 | 01:15.645 | 01:26.000 | |||
86 | Crusix | 02:41.743 | 01:15.580 | 01:26.163 | |||
87 | eeqw | 02:41.763 | 01:15.841 | 01:25.922 | |||
88 | hd_storm | 02:41.774 | 01:15.948 | 01:25.826 | |||
89 | Gelbewand | 02:41.779 | 01:15.542 | 01:26.237 | |||
90 | murphyslawl1 | 02:41.838 | 01:15.982 | 01:25.856 | |||
91 | CRX_Gh0ds | 02:41.870 | 01:16.021 | 01:25.849 | |||
92 | @Siny | 02:41.872 | 01:15.669 | 01:26.203 | |||
93 | Cedyyy | 02:41.926 | 01:15.666 | 01:26.260 | |||
94 | Ed | 02:41.942 | 01:16.023 | 01:25.919 | |||
95 | Levingston | 02:41.979 | 01:15.885 | 01:26.094 | |||
96 | AC Poke | 02:42.016 | 01:15.939 | 01:26.077 | |||
97 | Pingu | 02:42.020 | 01:15.804 | 01:26.216 | |||
98 | TTv/MrDaleJE | 02:42.022 | 01:15.911 | 01:26.111 | |||
99 | @okaui | 02:42.048 | 01:15.987 | 01:26.061 | |||
100 | Wasa | 02:42.089 | 01:15.886 | 01:26.203 | |||
101 | tomjd | 02:42.107 | 01:15.876 | 01:26.231 | |||
102 | CRX_Mars | 02:42.177 | 01:15.993 | 01:26.184 | |||
103 | f1manu | 02:42.202 | 01:15.936 | 01:26.266 | |||
104 | @tko survivor | 02:42.227 | 01:16.160 | 01:26.067 | |||
105 | SLI | 02:42.323 | 01:15.784 | 01:26.539 | |||
106 | Cloakz | 02:42.359 | 01:16.152 | 01:26.207 | |||
107 | @MrZOCKson | 02:42.361 | 01:15.947 | 01:26.414 | |||
108 | Neo Sieben | 02:42.364 | 01:16.179 | 01:26.185 | |||
109 | Alejandro | 02:42.386 | 01:15.970 | 01:26.416 | |||
110 | Neurux | 02:42.409 | 01:16.176 | 01:26.233 | |||
111 | Revitalize | 02:42.423 | 01:16.065 | 01:26.358 | |||
112 | Max Duca | 02:42.448 | 01:15.547 | 01:26.901 | |||
113 | Bache Lightyear | 02:42.455 | 01:16.003 | 01:26.452 | |||
114 | Skatie | 02:42.492 | 01:16.247 | 01:26.245 | |||
115 | Oria | 02:42.502 | 01:16.157 | 01:26.345 | |||
116 | Rarecax | 02:42.542 | 01:16.179 | 01:26.363 | |||
117 | SirBrokealot | 02:42.571 | 01:16.140 | 01:26.431 | |||
118 | Márk | 02:42.642 | 01:16.354 | 01:26.288 | |||
119 | mrsoulhd | 02:42.678 | 01:16.056 | 01:26.622 | |||
120 | Scroptompulous | 02:42.757 | 01:16.479 | 01:26.278 | |||
121 | KStrike | 02:42.763 | 01:16.217 | 01:26.546 | |||
122 | Robin Wolkow | 02:42.846 | 01:16.329 | 01:26.517 | |||
123 | @balazsbekes_2804 | 02:42.898 | 01:16.026 | 01:26.872 | |||
124 | loafcorn | 02:42.902 | 01:15.991 | 01:26.911 | |||
125 | BoxAFrog | 02:42.902 | 01:16.220 | 01:26.682 | |||
126 | @ronnin1978 | 02:42.928 | 01:16.196 | 01:26.732 | |||
127 | thomasooo | 02:42.929 | 01:16.167 | 01:26.762 | |||
128 | Sean-William | 02:42.954 | 01:16.317 | 01:26.637 | |||
129 | @RFGangster | 02:43.010 | 01:16.412 | 01:26.598 | |||
130 | @luisoracing | 02:43.111 | 01:16.316 | 01:26.795 | |||
131 | Frihman | 02:43.127 | 01:16.473 | 01:26.654 | |||
132 | St_Jonh | 02:43.275 | 01:16.519 | 01:26.756 | |||
133 | Magda | 02:43.276 | 01:16.440 | 01:26.836 | |||
134 | dak_attack | 02:43.370 | 01:16.567 | 01:26.803 | |||
135 | [SIR] Tr0Kyo® | 02:43.470 | 01:16.385 | 01:27.085 | |||
136 | BlackViperGT | 02:43.547 | 01:16.648 | 01:26.899 | |||
137 | @.callmemagic | 02:43.611 | 01:16.660 | 01:26.951 | |||
138 | Azbi | 02:43.618 | 01:16.453 | 01:27.165 | |||
139 | Jersias | 02:43.716 | 01:16.720 | 01:26.996 | |||
140 | AOR | SnIpPz_zRuSh | 02:43.786 | 01:16.408 | 01:27.378 | |||
141 | phoenix1987 | 02:43.787 | 01:17.213 | 01:26.574 | |||
142 | Alan Garner | 02:43.790 | 01:16.993 | 01:26.797 | |||
143 | @supersonic_frisbee | 02:43.820 | 01:17.002 | 01:26.818 | |||
144 | Yandu | 02:43.837 | 01:16.555 | 01:27.282 | |||
145 | Luzzio | 02:43.939 | 01:17.575 | 01:26.364 | |||
146 | Hermann26 | #SL | 02:43.950 | 01:16.779 | 01:27.171 | |||
147 | yngwiereid | 02:44.109 | 01:16.915 | 01:27.194 | |||
148 | @Bario | 02:44.132 | 01:17.045 | 01:27.087 | |||
149 | floryen | 02:44.141 | 01:16.967 | 01:27.174 | |||
150 | Tobias | 02:44.377 | 01:17.893 | 01:26.484 | |||
151 | @Elliota | 02:44.391 | 01:17.298 | 01:27.093 | |||
152 | Roy | 02:44.404 | 01:16.730 | 01:27.674 | |||
153 | peruna_ | 02:44.506 | 01:16.995 | 01:27.511 | |||
154 | erti147 | 02:44.605 | 01:17.030 | 01:27.575 | |||
155 | Arphaxad | 02:44.733 | 01:17.290 | 01:27.443 | |||
156 | Steve | 02:44.982 | 01:17.103 | 01:27.879 | |||
157 | Aurelijus Miciulis | 02:44.989 | 01:17.240 | 01:27.749 | |||
158 | ThatLitium | 02:45.095 | 01:16.985 | 01:28.110 | |||
159 | nexes_on_pc | 02:45.176 | 01:17.645 | 01:27.531 | |||
160 | @Felix1000 | 02:45.265 | 01:16.999 | 01:28.266 | |||
161 | Taylor Funk | 02:45.286 | 01:17.406 | 01:27.880 | |||
162 | MadLad | 02:45.400 | 01:17.049 | 01:28.351 | |||
163 | N3j | 02:45.504 | 01:17.441 | 01:28.063 | |||
164 | Flare Star | 02:45.515 | 01:17.536 | 01:27.979 | |||
165 | shyguy1992 | 02:45.748 | 01:18.572 | 01:27.176 | |||
166 | AstroSniper | 02:47.280 | 01:18.584 | 01:28.696 | |||
167 | Grigor | 02:47.566 | 01:19.254 | 01:28.312 | |||
168 | flyskils | 02:47.609 | 01:19.351 | 01:28.258 | |||
169 | m0rpheus1975 | 02:48.340 | 01:18.493 | 01:29.847 | |||
170 | Bruno | 02:48.666 | 01:19.199 | 01:29.467 | |||
171 | colyente | 02:52.921 | 01:21.352 | 01:31.569 | |||
172 | Clint58 | 02:53.033 | 01:21.943 | 01:31.090 | |||
173 | Luki1054 | 02:53.712 | 01:21.392 | 01:32.320 |
15.08.2021 19:00 UTC
Bahrain
22.08.2021 19:00 UTC
Spain
29.08.2021 19:00 UTC
Monaco
05.09.2021 19:00 UTC
Azerbaijan
12.09.2021 19:00 UTC
France
19.09.2021 19:00 UTC
Austria
31.10.2021 20:00 UTC
Italy
14.11.2021 20:00 UTC
Belgium
21.11.2021 20:00 UTC
Portugal
28.11.2021 20:00 UTC
Great Britain
05.12.2021 20:00 UTC
China
12.12.2021 20:00 UTC
Imola
19.12.2021 20:00 UTC
Brazil
The leagues on each platform (within each region) are organised in a tier structure.
-
European region:
These will be separated into the Main leagues and the Assist leagues. The main leagues will include drivers using no assists at all. The assist leagues will include everyone who uses any of the assists, like traction control, ABS, racing line and/or automatic gears. Pit Assist, Pit Release and Automatic ERS/DRS are banned in all AOR F1 leagues.
The main and assist leagues will have separate sign up sections on the sign-up interface.
America region:
The assists allowed in the America leagues will depend on amount of sign-ups, and their required assists.
Provisional assists allowed in the America region (may be changed):
β PC: Racing Line, Automatic Gearbox
- 2.1 Driver placements
-
When setting up the leagues for a new season, we always aim to make the leagues 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 to allow us 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 league tier as competitive as possible.
All drivers will be placed in a suitable league based on various factors; the Time Trial event held as part of the sign-up process, performance in the mandatory evaluation race (new drivers only), and to some extent performances in the previous league season (for drivers who raced in Season 21).
In the European leagues, drivers may choose to either sign up to the Main Leagues, or to sign up to the Assist Leagues
Each league will allow a full grid of 20 drivers, plus reserves if necessary.
Note: Drivers who missed a significant number of races in the previous season may be placed as a reserve driver.
-
- 2.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 time trial event, and will then be placed into an appropriate league based on their pace. No evaluation race will be required as a new driver signing up at this point. However, drivers will only be able join mid-season if there is a space available in an appropriate league. If there isn't, they will be placed into a league as a reserve driver - or on the waiting list - until a space opens.
-
- 2.3 Reserve drivers
-
Drivers who are assigned to a league 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 can choose to race with any of the cars that have been left open by a no-shower, however since they are not a permanent part of a specific team, the points they score will not count towards the Constructor Championship.
Reserve drivers will not be visibly listed in their league's championship standings. However, the table keeps record of their points in the background, so that if they later get promoted to a main race seat (if one of the main drivers pulls out or is removed), points scored during the reserve driver period will be added to their total points count.
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) will be removed from the league. It's a good idea to keep an eye on the the relevant discord channels before the races to see if any no-showers are announced.
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.
Note that we will not be accepting drivers signing up with the intention to be a permanent reserve. Drivers who are not able to race regularly may take part in social races as an alternative.
-
- 2.4 Mid-season driver moves
-
Drivers may be moved between leagues while the season is ongoing if it's clear that they have been misplaced. This could be that they are clearly too fast for their league, or that they are unable to experience close racing due to being too slow.
If a league ends up in a situation of severely lacking driver numbers, appropriate drivers from the league(s) below may be offered a move up in order to balance the numbers.
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 overseers reserve the right to move drivers up to a higher (or lower) tier if this is deemed to be in the best interest of the league, and to avoid drivers excessively dominating.
-
Cars and teams will be decided individually within each league at the start of the season. When signing up, drivers can create an ordered list of their preferred car choices. When the placements are published, also a list of drivers and their car will be published. Afterwards, people can still request car changes if they agreed with another driver to switch cars.
- 3.1 Selection order
-
The order in which the drivers will receive their cars within each league is decided based on the below priority list:
1. Returning drivers championship finishing order of previous season
2. Non previous season returning drivers ranked from fastest to slowest combined time from the time trials. 3. New drivers who have not previously raced in the AOR F1 Leagues, ranked from fastest to slowest combined time from the time trials and evaluation pace.
If a new driver joins the league at a later stage of the season, they may pick any car that is available at the point of being assigned to the league.
-
The following lobby settings will be applied for the official league race sessions:
- 4.1 Session Options
-
- AI Driver Level: 90 (Master)*
- Era: 2021 F1 Cars
- Car Performance: Equal
- Maximum Participants: 20 (22 in leagues with live broadcasts)
- Practice Length: None
- Qualifying: Short Qualifying
- Race Distance: 50%/100%(short versions of circuits)
- Weather: Dynamic
- Forecast: Approximate
- Session Start Time: Official
- Session Privacy: Invite Only
-
- 4.2 Race Settings
-
- Parc FermΓ© Rules: On
- Collisions: On
- Recovery: Off
- Vehicle Damage: Standard
- Vehicle Damage Rate: Standard
- Low Fuel Mode: Hard
- Tyre Temp: Surface & Carcass
- Ghosting: On
- Car Setup: Full
- Safety Car: Standard**
- Rules and Flags: On
- Corner Cutting Stringency: Strict
- Track Surface Type: Realistic
- Formation Lap: On
- Race Starts: Manual
*The AI Driver Level may be adjusted individually within each league depending on the general pace of the drivers.
**Using the Safety Car is very dependent on the number of bugs, and it may be up to the coordinator and drivers on whether to have it on.
-
- 5.1 Points system
-
The following points will be scored for each race finishing position.
1st = 25
2nd = 18
3rd = 15
4th = 12
5th = 10
6th = 8
7th = 6
8th = 4
9th = 2
10th = 1
11th-20th = 0
One extra point will be awarded to the driver of the fastest lap in the top 10. *Doesn't matter if the fastest lap of the race is outside the top 10.
-
- 5.2 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.
Drivers who disconnect from the lobby and have their race finished by the AI are only classified for the laps that were completed under the driver's own control, unless they are able to reconnect to the lobby and finish the race under manual control.
Drivers who complete more than 90% of the race before accidentally crashing out or getting disconnected will be classified as a finisher, but will only be credited with the amount of laps they completed in control of their car, even if the driver's AI car makes it to the end. Points will then be scored as per the system above.
-
- 5.3 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.
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.
-
- 5.4 DNS
-
Active league drivers who did not attend the race will be classified as DNS (Did Not Start), and will not score any points.
Championship standings:
- Drivers and constructors 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 constructors are tied on points, the higher place in the standings will be awarded to 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.
-
- 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, and this is reported to the stewards, then you will be penalised.
- 1.1.2Deliberately crashing into another car will result in being permanently excluded from the leagues.
- 1.2 On-track battling
- 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β Do not force another car off the track by leaving it too little room on corner entry or exit. If the other car is alongside you when going into a corner (at the turn-in point*), or when exiting a corner, you must adjust your line to avoid contact and to not force the other car off the track. Being sufficiently 'alongside' to warrant being left room is generally judged as the attacking car's nose being alongside or ahead of the defending car's sidepod. *The 'turn-in point' in this setting refers the natural turn-in point as per the standard racing line. If the defending car causes contact due to turning in earlier than what is considered the standard, he will be seen at fault.
- 1.2.3β Any movement in the braking zone is not accepted when in close proximity to other cars, as the action can easily cause an incident. Choose a line before entering the braking zone, and hold that line until the turn-in point. If you come from a defensive position and want to move back towards the racing line, you must leave a least one car width between your car and the edge of the track.
- 1.2.4β On straights, if another driver has any part of their car alongside your car, you must respect their position on the track and avoid making any movement into the other car.
- 1.2.5β Excessive weaving and blocking is not allowed. When defending from another car, choose a line on the track and stick to it, and make sure the attacking car has sufficient time to react to your movement.
- 1.2.6β Excessive weaving on straights with the purpose of breaking slipstream is not allowed, even if the car behind is not physically close enough to make an overtaking attempt. Weaving in this situation is deemed excessive if the car ahead makes more than two moves across the track on the same straight.
- 1.3 Track limits
- 1.3.1Stay within the track boundaries with at least two tyres at all times. The track boundaries are defined by the white lines, NOT by the edge of the kerbs. The white lines are deemed part of the track, however the kerbs are not. 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. It is up to the stewards' discretion (based on the evidence provided) to determine whether a driver has abused the track limits to an extent where a penalty is justified.
- 1.3.2The occasional misjudgement of a corner can happen, but if you accidentally gain an advantage by going outside the track limits you are expected to back off to an extent that clearly negates any advantage gained.
- 1.3.3If 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, unless the game awards you a penalty.
- 1.3.4In qualifying, if you go outside the track limits in a way that doesn't clearly lose you time, you are expected to lift off the throttle to clearly negate any potential advantage gained. If the cut is major, the lap should be aborted. Failing to do this may result in post-race punishment.
- 1.4 Qualifying etiquette
- 1.4.1In qualifying, it is your own responsibility to find free space on the track when starting a flying lap. A car on a flying 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.
- 1.4.2In qualifying, it is not permitted to retire from the session while you are out on track, as this may cause your AI car to park on or next to the track and hinder or distract other drivers. If you wish to retire from the session, you must do so while in the garage.
- 1.4.3In qualifying, it is not permitted to cut or miss sections of track at any time, including on in-laps and out-laps. Doing so to gain an advantage or to save time will be penalised.
- 1.4.4If a driver has a qualifying ban, they are not permitted to do multiple outlaps / inlaps. Furthermore, drivers must not assist any other drivers (through slipstream, or otherwise) whilst serving a qualifying ban. The driver may only do one out & in lap to load their setup for the race. Any driver found to be doing so will be penalised.
- 1.5 Race etiquette
- 1.5.1It is not permitted to deliberately cause a yellow flag situation, even if the driver is not being particularly hazardous. If a driver is found doing this, the stewards may penalise them.
- 1.6 Spacial Awareness
- 1.6.1It is important to have good awareness of where other cars are around you on track, so taking extra care is vital both at the start of a race and in battles.
- 1.6.2If you spin off the track while other cars are close behind, make sure to wait with rejoining the track until it is safe to do so. As a suggestion, use the mini-map to ensure that no cars are close by when you rejoin. Please do not take the risk of trusting the game to ghost your car while recovering, as the ghosting system may not always work as intended.
- 1.6.3If you spin and end up sideways or backwards on the track, stay still until any oncoming cars have gone past. It is far easier to avoid a stationary obstacle.
- 1.6.4When you're coming up to lap another car, it is advised to alert that driver through the voice chat (if possible) so they are aware that you will soon be lapping them.
- 2.1 In-game penalties
- 2.1.1If you feel that the game has awarded you an unfair time penalty, you can apply for a penalty removal in the Stewards Panel after the race. More information about this can be found under the Rule Enforcement section. Compensation for unfair drive throughs or stop-go penalties will not be possible, as this affects your position on the track during the race.
- 2.1.2If you feel the game has unfairly disqualified you from the race, you can submit your full race footage to the stewards. If it is deemed that the disqualification was justified, it will remain. However, if the disqualification is deemed to have been clearly unfair, or came as a result of a game glitch, then you will be classified as the last finisher and score full points for that position.
- 2.2 Being lapped
- 2.2.1When the game shows you the blue flag, you have been caught up by a car on a lap ahead of you. When being lapped, it is your responsibility to let the leaders through safely at the earliest opportunity, without costing them any time.
- 2.2.2If you are going faster than a car that has lapped you, do not attempt to unlap yourself unless it is safe to do so and doesn't hinder the car in front.
- 2.3 Safety car & virtual safety car guidelines
- 2.3.1During a virtual safety car, or while catching up to the train during a safety car period, you must not exceed the delta time indicated by the game.
- 2.3.2If you are the lead car and driving to catch up to the safety car, please take caution when approaching it, as it will be moving very slowly while waiting to pick you up. Approach it slowly and then the safety car should pick up its speed. Make sure you keep a safe distance to the safety car to avoid potentially hitting it if lag or other inconsistencies occur, as this may lead to the game disqualifying you from the race.
- 2.3.3β As the leader of the pack following the safety car, do not intentionally slow the pack down to a dangerously low speed when controlling the pace ahead of a restart. However it is at the leaders discretion to back the pack up accordingly to have an orderly restart.
- 2.3.4β While under virtual safety car periods, driving unnecessarily slower than the delta and therefore backing up cars behind is not acceptable. Any driver found to be doing so will be penalised.
- 2.3.5β While in the safety car queue, do not drive dangerously by suddenly slowing down in front of someone. (i.e brake testing) Keep a safe distance to the car ahead, but without creating an unnaturally big gap in the queue.
- 2.3.6β Overtaking under safety car conditions is prohibited. Even if the car ahead of you is a ghost car driven by the AI, or a car that is lapped. Although it may be frustrating to sit behind a slow-moving ghost car until you reach the pit-lane or catch up to the pack, this will avoid problems such as illegal overtake penalties being awarded.
- 2.3.7β During a Safety Car restart it is forbidden to overtake until the start/finish line. Any driver overtaking before this will be penalised, if not done so by the game.
- 2.3.8β It is prohibited to park or crash your car for the purpose of initiating a safety car situation. Anyone found to have deliberately crashed out or retired their car on track will be severely penalised, regardless of whether this actually ended up causing a safety car or not.
- 2.3.9β If we experience a major glitch with the safety car (for example someone being unfairly and unavoidably disqualified due to a safety car glitch), we reserve the right to disable this feature with immediate effect if deemed appropriate.
- 2.4 Formation lap guidelines
- 2.4.1For the sake of fairness with regards to tyre wear, all drivers are required to complete the formation lap. It is not allowed to skip the formation lap by intentionally driving in a manner that sends you back to the grid. Doing this, or being at fault for an incident that sends you back to the grid, will see you awarded with a post-race penalty if reported.
- 2.4.2At the start of the formation lap, please do not move away from your grid slot until every car ahead of you have started moving.
- 2.4.3β During the formation lap, do not drive dangerously by suddenly slowing down in front of someone. Keep a safe distance to the car ahead, but without creating an unnaturally big gap in the queue.
- 2.4.4Pausing the game during the formation lap is allowed, but not advised. If you do pause you must take care, so as to avoid obstructing others or causing a collision.
- 2.5 Tyre rules
- 2.5.1Drivers who qualify in the top 10 are forced to start the race on the tyre set they used to set their fastest qualifying lap. Drivers who qualify outside the top 10 may choose whichever set of starting tyres they want.
- 2.5.2β Should the session have to be restarted between the end of qualifying and the start of the race with a custom grid all drivers in the top 10 are required to start on the same compound of tyre that they qualified on in the original session.
- 2.5.3β In qualifying, it is not allowed to deliberately crash your car in order to destroy the tyre set you would have started with upon qualifying in the top 10. If you happen to accidentally crash out and ruin your starting tyres, you must start the race on a different set of the same compound of tyre.
- 2.5.4β You must use one of the two mandatory tyre sets (as specified by the game) at some point during the race.
- 2.5.5β If a driver uses a wet tyre compound in wet conditions during the race, the dry tyre rule becomes invalid. It doesn't become invalid if a driver mistakenly puts wet tyres on in dry conditions.
- 2.5.6β In qualifying, it is not allowed to run laps on wet tyres (intermediates or wets) while the track conditions are clearly dry.
- 2.6 Pit stops
- 2.6.1β Upon entering and exiting the pits, the whole car must stay within the white lines from the very beginning of the pit-lane markings. 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.
- 2.6.2With manual pit stops enabled, you will need to apply the brakes yourself when going into the pits. Slow down to the required speed limit (which can vary from track to track) before the marker boards at the start of the pit lane.
- 2.6.3With manual pit stops enabled, you will need to perform the start procedure upon leaving your pit box, once the pit light goes green. This procedure is the same as launching the car at the start of the race.
- 2.6.4With manual pit stops enabled, you will need to manually disengage the pit limiter upon leaving the pit lane. Make sure you have a button assigned for this.
- 2.6.5It is not allowed to pause the game in order to have the AI perform the pit entry for you.
- 2.7 DRS
- Driving in a dangerous or unsporting manner in order to gain the use of DRS in the race is not allowed and may be penalised retrospectively. This kind of driving includes - but is not limited to - violently decelerating and/or steering when clearly in front of the following car, or deliberately letting another car go past for the purpose of ensuring DRS activation.
- 2.8 Jump starts
- 2.8.1Any jump start should be penalised by the game with a drive through penalty. However, drivers must still take the safest possible action they deem fit at the time. That may be to stop, but that may depend at what stage in the start sequence we are at
- 2.8.2Many jump starts will take place when all 5 lights are lit up and the driver will go a millisecond before the lights go out. If this happens, being this close to the start, the driver should just continue in position until the end of the lap. If the jump start happens a couple of seconds before the race start and the driver decides to keep going with stationary cars, this is fine as long as they do not make contact.
- 2.9 Pausing the game
- 2.9.1We advise against intentionally pausing the game during safety car periods and when you are close ahead of another car during the race, as this will cause your car to slow down and may lead to surrounding cars taking avoiding action, even if your car is ghosted.
- 2.9.2You are fully responsible for your car's actions even while the game is paused, and any incidents or dangerous situations caused as a result of this will be penalised normally.
- 2.9.3It is not permitted to use the 'Reset to Track' function of the pause menu in order to recover quickly. Failure to adhere to this could lead to a penalty being applied retrospectively by the stewards.
- 2.10 Recording
- 2.10.1By default, the leagues will not enforce rules about mandatory recording of either qualifying or the race. However, if a league is seen to be suffering from extreme issues of drivers not respecting track limits, some level of mandatory recording may be enforced for that league - if possible - on the coordinators' judgement.
- 2.10.2Even though it's not mandatory, we do encourage drivers with recording possibilities to record their races, in order to have evidence for use in the stewards panel, both to be able to report incidents you witness or get involved in, or to show your side of the situation if another driver reports you for something.
- 3.1 Communication
- It is advised to use a headset/microphone while in the race lobby in order to effectively receive any potential messages or instructions from the League Coordinator. Having the ability to communicate with other drivers during the race can also make it easier to avoid - and resolve - any on-track incidents that may occur. Using a voice communications is not mandatory, but desirable. Please note that you should set your microphone to "Push to talk"-mode if possible. All leagues will have access to our Discord server which acts as the official game chat. There will be specific voice channels for each league on each platform, however we only really expect the PC leagues to use these as the consoles have their own chat services. Push-to-talk will be mandatory in the leagues' voice channels.
- 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 they are giving a message, and accept the decisions they make. If you feel any actions/decisions are wrong, address the issue calmly and maturely. Coordinators' decisions are final within the lobby, but may be reviewed later if you feel an error has been made. Please accept that making a call instantly can be tricky, and the Coordinator (even if participating in the race) is expected to be entirely neutral.
- 3.2.4Only the Coordinator - or the lobby host after consulting with the Coordinator - will start the lobby, continue over to the race and start the race. So please, as a normal driver, do not press the button which initiates the timer. This is to ensure that all the drivers are present, and also that all necessary screenshots of the results can be taken.
- 3.3 Race etiquette/Quitting the race
- 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.
- 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 always has to be at the back.
- 3.3.4Deliberately retiring your car ("rage-quitting") is prohibited. If you do so, you are still fully responsible for your car's actions after you leave the session / retire the car. If your AI causes crashes or brings out a Safety Car, you will be punished. You have been warned.
- 3.4 Discord / Forum activity
- 3.4.1β You need to be an active member on our AOR Discord server while being a driver in our leagues. Previously, activity on the forum would be required, but as long as you are around on the discord and signing out of races via the signup site, that will suffice. It's encouraged to get involved with the community in the chats on discord. Activity on the forum is still encouraged but not necessary. If staff are trying to find out why you haven't signed out of a race, we are likely to message you on discord. If no response then we are likely to check activity in the discord channels, and if no sight of you there, you are likely to be removed from the league.
- 3.4.2β You are expected to behave in a respectful manner on the discord, like in the race lobbies. Please avoid name-calling, baiting and other behaviour that is intended to aggravate other members of the community.
- 3.5 Discord / Forum activity
- 3.5.1You need to be an active member on our AOR Discord server while being a driver in our leagues. Previously, activity on the forum would be required, but as long as you are around on the discord and signing out of races via the signup site, that will suffice. It's encouraged to get involved with the community in the chats on discord. Activity on the forum is still encouraged but not necessary. If staff are trying to find out why you haven't signed out of a race, we are likely to message you on discord. If no response then we are likely to check activity in the discord channels, and if no sight of you there, you are likely to be removed from the league.
- 3.5.2You are expected to behave in a respectful manner on the 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 Connection & Lag
- 4.1.1It's an unfortunate aspect of online racing that having a stable connection is critical to being able to race closely with other cars. While we understand that not everyone can have a perfect connection, and that occasional lag can't be avoided, we reserve the right to remove a driver from the league if their connection is persistently causing major issues for other drivers.
- 4.1.2If your connection causes issues in a race, you will be warned to find a solution for the next race. If in the next race it is still a problem, you are likely to be asked to leave the league until you can fix it.
- 4.1.3We do our best to ensure that the best available connection in each league acts as the lobby host, so that any connection issues are most likely a result of a fault on the driver's end. Please ensure that your internet connection is in an optimal state - and that your NAT type is open - before entering the race lobby.
- 4.1.4In an effort to minimize the chances of bugs, we advise drivers to restart their game immediately before connecting to the race lobby.
- 4.2 Disconnections & rejoins
- 4.2.1If a driver loses connection during qualifying or the race, they are allowed to re-join the lobby through a pre-session backup invite if they have one available, or via a fresh invite from a spectator or other driver in the lobby if you are lucky (however please don't spam drivers or coordinators for new invites while they are racing). If you are dropping from the same lobby multiple times due to connection issues, it is however best to stay disconnected. Please only attempt to re-connect once in order to avoid causing unnecessary stress on the lobby. If it doesn't work on the first try then it's tough luck.
- 4.2.2If a league is experiencing notable or recurring issues (connection-related or otherwise) caused by drivers re-joining race lobbies, the coordinator(s) reserve the right to ban re-joining from being allowed within that league.
- 4.3 Mass disconnections
- 4.3.1During qualifying, if 4 or more drivers lose connection to the lobby and are unable to get back in, then the lobby will be restarted and qualifying run again from scratch.
- 4.3.2During the race, if half (or more) of the drivers in the lobby lose connection at the same time, or over a short period of time, that counts as a mass disconnection. A "short period of time" would generally mean a couple of minutes, up to a maximum of 5 minutes. This also includes major de-syncing where the lobby gets split up or the other drivers turn into slow-moving ghost cars on everyone else's screen, even if they are technically still racing on their own screen.
- 4.3.3If less than 50% of the race was completed at the time of the mass disconnection, the race will be restarted immediately, preferably with a new lobby host. The new lobby will be created without another qualifying session, and the grid will be set up in the same order as the original qualifying results, using the 'grid editor' feature.
- 4.3.4If more than 50% of the race was completed at the time of the mass disconnection, the race will end and the race order from the time of the first disconnection becomes the final result. Half points are awarded to all drivers.
- 4.3.5If more than 90% of the race was completed at the time of the mass disconnection, the race will end, and the race order from the time of the first disconnection becomes the final result. Full points are awarded to all drivers.
- 4.4 Lobby restarts
- 4.4.1The lobby may be restarted by the coordinator in the event of a major issue that affects the normal progression of the session(s). This includes mass disconnections (as per section 4.3 above) and the lobby getting stuck on the loading screen before qualifying or between qualifying and the race.
- 4.4.2If the lobby restart happens after the qualifying session has concluded, the new lobby will be set up with only a race session. In this scenario, the 'grid editor' will be used to place the drivers into their correct qualifying positions. All drivers who qualified in the top 10 will have to select the same tyre compound as they used to set their fastest qualifying lap.
- 5.1 Missing races
- 5.1.1If you are unable to attend a race, you must visit the sign up site (apexonline.racing) and 'sign out' of the race on the Calendar tab. You must do this no later than 30 minutes before the race, otherwise you will receive a no-show reprimand.
- 5.1.2Upon signing out of the race, it is your choice to give a reason but is not required. However if you are repeatedly not attending due to playing other games at the time, then your position in the league will be put under review.
- 5.1.3Using the tier specific discord channels as a way of signing out of a race won't be accepted.
- 5.1.4Accumulating 3 uninformed no-shows will lead to the driver in question being removed from the league and placed on the blacklist.
- 5.1.5If a driver is persistently failing to turn up to races, even if they are signing our of races, their coordinator and the F1 Team may look at reviewing their position in the league for the remainder of the season. It may be that, if no change is possible, a driver may be placed on the reserve list instead of a full time seat. If a driver goes through an extended absence period but will be returning back to full activity, this is acceptable and no action will be taken.
- 5.1.6Getting another driver to race under your name is prohibited and will result in an immediate blacklist from the league.
- 5.2 Pulling out mid-season
- 5.2.1If you have to pull out of the league while the season is ongoing, you must inform your League Coordinator about the situation. If you leave by simply not showing up for the races, without informing anyone, you will be placed on the blacklist (see section 6.5 for info about the blacklist).
- 5.2.2It's impossible for us to stop you from leaving if you've made your 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 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) render you unable to carry on. However, choosing to quit due to getting bored of the game, having a bad season or because something goes against you, is not a good reason. Remember, when signing up you commit yourself to racing for a full season, not only for a few races.
- 5.2.3If you find yourself in a situation where you are not enjoying your league because all other drivers are too quick or too slow compared to yourself, contact a member of the F1 Team 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 circumstances allow it.
- 5.2.4Note that the above rules only apply while the season is ongoing. We obviously don't have a problem with drivers choosing to leave after a season has finished, for whatever reason.
- 6.1 Stewards Panel
- The 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 F1 Stewards (consisting of various members of the F1 Coordinating Team from all 3 platforms, along with other experienced members) and appropriate action will be taken.
You can make a stewards enquiry for the following:
- On-track incidents: If you feel another driver has caused an incident - eg. hitting your car, forcing you off the track, rejoining the track unsafely, or generally driving too aggressively - you should report this to the stewards for investigation.
- Track limits: If you witness another driver is persistently gaining time by abusing the track limits, you should report this to the stewards.
- General rule-breaks: If you witness another driver breaking any of the rules or guidelines regarding lobby behaviour (on-track or off-track), you should report this to the stewards.
- Removing an unfair time penalty: If you receive a time penalty from the game, and you feel this was awarded unfairly, you can make an enquiry for the penalty to be removed. When making such an enquiry, you need to provide evidence in the form of video footage and a picture of the post-race race director screen showing what the penalty was for and the time of when it was applied. Any appeals without this will be dismissed.
- 6.1.1Time limit for enquiries: Note that there is a time limit of 36 hours after the race has finished (Tuesday 9am) to make a stewards enquiry for an incident you have been involved in or witnessed during the race. 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 would not have been visible to other driver(s) in the race at the time it happened.
- 6.1.2Uploading video evidence: Any video evidence submitted in a stewards enquiry must be uploaded to Youtube or Twitch (Xbox users may use GamerDVR) and linked in the enquiry thread. 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.
- 6.2 Penalties
- 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 are sorted below, in order of severity. Breaking a rule also leads to penalty points being added to your name - 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)
- 5-second time penalty
- 10-second time penalty
- 15-second time penalty
- 20-second time penalty (or higher)
- Qualifying ban for the next race (may also be applied in place of a time penalty if the driver did not finish the race)
- Disqualification from the race
- One-race ban
- Multiple-race ban
- Permanent removal from the league
- 6.3 Penalty points system
- The penalty 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. Penalty points will be applied alongside normal race penalties, as per the list below.
- 1 point - Blocking another driver in qualifying
- 1-3 points - Excessively abusing the track limits (depending on severity)
- 1 point - Using the reset car to track function
- 1 point - Causing a minor avoidable collision
- 2 points - Causing a moderate avoidable collision
- 3 points - Causing a significant avoidable collision
- 4 points - Causing a major avoidable collision
- 1-2 points - Driving dangerously or un-sporting conduct
- 3 points - Crashing on track on purpose (can cause a Safety Car)
- 12 points - Deliberately crashing into another driver
- 6.4 Reprimand system
- While the race penalties and penalty points system are mainly aimed at dealing with on-track issues - the reprimand system mainly deals with issues that may off the track, however there may be crossover and some situations where on-track issues are dealt with by a reprimand.
If you receive 3 uninformed no-show based reprimands, you're out. (see section 6.5 for info about the blacklist). If you receive 5 reprimands, (includes both uninformed no-shows and/or on track incidents) you'll also be removed from the league and placed on the blacklist
You can receive a reprimand for the following:- No-showing a race without giving prior notice to the League Coordinator
- Showing abusive behaviour towards another driver, either in the race lobby or on the forum/discord
- Pressing the start button early between sessions (after an initial warning) (if proven)
- Retiring whilst still on track, without a valid reason (can cause a Safety Car) see rule 3.4.1
- Leaving a session early without retiring
- Deliberately getting yourself disqualified in qualifying (accompanied with a qualifying ban)
- Causing a danger to other vehicles through lag/connection issues
- Inactivity on the AOR platforms
- Rejoining the lobby during the race while the rejoining rule is in effect
- 6.5 Blacklist
- The blacklist contains the names of drivers who have been removed from the leagues - either through accumulating 12 penalty points or 5 reprimands (or 3 uninformed no-shows) - and drivers who have left the leagues during an ongoing season with no good reason.
- Drivers who are placed on the blacklist may be given a second chance in the future, but only after sitting out the rest of the season they were blacklisted from and the following season (so a driver blacklisted in Season 20 may be given a second chance in Season 22).
- Drivers who are placed on the blacklist again after having been given a second chance will be placed on the blacklist permanently. No further chances will be given.
- Drivers who have been blacklisted for deliberate crashing, cheating/hacking, or other extreme offences will be immediately placed on the permanent blacklist and not be given a second chance.
Discord name | Social | Car | Number | |
---|---|---|---|---|
@Floudy | Alpha Tauri (2022) | 15 | ||
@ΠΠΈΠΊΠΎΠ»Π°ΠΉ ΠΡΠ°Π²ΡΡΠ½ΠΎΠΊ | 0 | |||
@MaxAMG | Mercedes (2022) | 69 | ||
@lukas_ | 0 | |||
@Felix1000 | Alpine (2022) | 35 | ||
@Gelbewand | Ferrari (2022) | 57 | ||
@Crusix | Alpha Tauri (2022) | 15 | ||
@ | 0 | |||
@tfunk1030 | 0 | |||
@Tr0kyo | Alpha Tauri (2022) | 32 | ||
@Jons | Aston Martin (2022) | 12 | ||
@Robin.w | Ferrari (2022) | 37 | ||
@Tagnemon | 88 | |||
@Pulkkis | Alpha Tauri (2022) | 2 | ||
@vaga | Alpha Tauri (2022) | 74 | ||
@N3j_ | 60 | |||
@Ved | 0 | |||
@dominiik18 | McLaren (2022) | 87 | ||
@Luzzio | Aston Martin (2022) | 58 | ||
@boriszakk42 | 15 | |||
@Daniel Rocker | Alpha Tauri (2022) | 27 | ||
@Der_Kaya | Red Bull (2022) | 19 | ||
@Bario | 93 | |||
@tko survivor | Mercedes (2022) | 20 | ||
@Azure | Ferrari (2022) | 97 | ||
@Cure | 19 | |||
@Ioseba Solís | 0 | |||
@Atrocity | Aston Martin (2022) | 92 | ||
@Jersias | McLaren (2022) | 15 | ||
@mulchiantobi | Alpine (2022) | 84 | ||
@Sauerbraten | Alfa Romeo (2022) | 87 | ||
@magda1111 | McLaren (2022) | 13 | ||
@ΕEØN4RD | Red Bull (2022) | 54 | ||
@t0m1039 | Red Bull (2022) | 98 | ||
@.callmemagic | McLaren (2022) | 95 | ||
@the_german_hermann | Alfa Romeo (2022) | 26 | ||
@Pingu | Alpha Tauri (2022) | 23 | ||
@Matti_29 | Red Bull (2022) | 20 | ||
@Shift4 | Mercedes (2022) | 97 | ||
@daigoro6 | Ferrari (2022) | 60 | ||
@Gh0ds | Mercedes (2022) | 66 | ||
@CRX_Mars | Haas (2022) | 21 | ||
@revitaliz | Williams (2022) | 23 | ||
@Juca | Aston Martin (2022) | 30 | ||
@SkyKartoffel | Alfa Romeo (2022) | 89 | ||
@matrixschlange | Aston Martin (2022) | 2 | ||
@Skatie | Mercedes (2022) | 37 | ||
@Elliota | 94 | |||
@ripsn | Alfa Romeo (2022) | 39 | ||
@Flyskills | 21 | |||
@dreadis. | 69 | |||
@Clint58 | Ferrari (2022) | 12 | ||
@tomjd | Haas (2022) | 25 | ||
@FeelRacing_Seb | Alpine (2022) | 21 | ||
@Nikolay | 38 | |||
@persegeeli | Mercedes (2022) | 66 | ||
@Simax | Alfa Romeo (2022) | 88 | ||
@Bartaaron04 | Mercedes (2022) | 66 | ||
@0.Oria | Red Bull (2022) | 20 | ||
@Hy77inen | 0 | |||
@The AM | Alpine (2022) | 34 | ||
@gregoryballati | Williams (2022) | 84 | ||
@BoxAFrog | Mercedes (2022) | 24 | ||
@rivershan | Mercedes (2022) | 34 | ||
@_sergo45 | Haas (2022) | 49 | ||
@RFGangster | Alfa Romeo (2022) | 26 | ||
@guilmauv | Williams (2022) | 68 | ||
@f1racer29 | Ferrari (2022) | 29 | ||
@Grigor | Ferrari (2022) | 13 | ||
@m0rpheus1975 | Alpine (2022) | 75 | ||
@T A R O X | Tim | 0 | |||
@Captcher | 62 | |||
@Azbi | 8 | |||
@tphuc.l | 65 | |||
@Blue Inquisitor | Aston Martin (2022) | 74 | ||
@Kevgenetics | Alpine (2022) | 94 | ||
@Bruno Hernandez | 0 | |||
@sp3ed9 | Williams (2022) | 39 | ||
@BallakSenior95 | Ferrari (2022) | 95 | ||
@Bebix | Alpha Tauri (2022) | 29 | ||
@ | 0 | |||
@Gar3d | Alpha Tauri (2022) | 19 | ||
@supersonic_frisbee | 2 | |||
@kiinakop | Haas (2022) | 23 | ||
@fortnites4idiots | Aston Martin (2022) | 69 | ||
@Neurux | 0 | |||
@VegaZ | Alfa Romeo (2022) | 32 | ||
@Tobias | 0 | |||
@YouSeven | 8 | |||
@Roy Lijnsvelt | 32 | |||
@ronnin1978 | Red Bull (2022) | 78 | ||
@Cr4igY2 | Mercedes (2022) | 62 | ||
@coachcurtcuh | Haas (2022) | 13 | ||
@Levingston | Alfa Romeo (2022) | 15 | ||
@TheGaffa | 25 | |||
@ | 65 | |||
@Patrick16 | Williams (2022) | 26 | ||
@ZOR_MrJoshua | Williams (2022) | 51 | ||
@galaxxy_rd | Red Bull (2022) | 13 | ||
@OBEN INNA SÜD | 61 | |||
@recreight | 67 | |||
@ThatLithium | 69 | |||
@balazsbekes_2804 | Haas (2022) | 28 | ||
@yanduu | Alfa Romeo (2022) | 46 | ||
@greenamit | 36 | |||
@Visquin | 12 | |||
@29 Balu | McLaren (2022) | 29 | ||
@Tom Walstra | 0 | |||
@.potato06 | Red Bull (2022) | 67 | ||
@creepydrive | Aston Martin (2022) | 15 | ||
@lior | Aston Martin (2022) | 24 | ||
@hd_storm | 78 | |||
@S.L.I | Alpine (2022) | 64 | ||
@Flow7L | 0 | |||
@Finnsen | Aston Martin (2022) | 29 | ||
@MurphysLawl | Williams (2022) | 48 | ||
@Isaac Barclay2 | 36 | |||
@β¨π·ππ πΎπππππβ¨ | 45 | |||
@luisoracing | Haas (2022) | 95 | ||
@Frihman | 91 | |||
@Scott (_ScraG) | Alfa Romeo (2022) | 28 | ||
@Sulphix | Ferrari (2022) | 27 | ||
@erti147 | Williams (2022) | 74 | ||
@LuDAMer22 | Alpha Tauri (2022) | 23 | ||
@Beken26 | 0 | |||
@rmate40 | Red Bull (2022) | 40 | ||
@RockyOoze | 37 | |||
@TTv/MrDaleJE WP™ | 0 | |||
@f1manu | Alpine (2022) | 2 | ||
@norekakrobata | 37 | |||
@Tobi π | Alpha Tauri (2022) | 19 | ||
@Mtw1man | Alpha Tauri (2022) | 2 | ||
@Cedyyy | Alpha Tauri (2022) | 71 | ||
@Rarecax | Alpine (2022) | 82 | ||
@Alwin Reid | 0 | |||
@XV_VIPER_VX | 57 | |||
@Nexes | 8 | |||
@.marcel96 | Williams (2022) | 24 | ||
@Like-Tom | 12 | |||
@p403n1x87 | Alpha Tauri (2022) | 87 | ||
@St_Jonh | 12 | |||
@szollosiati | 8 | |||
@ibluechelsea | Alpha Tauri (2022) | 8 | ||
@jtrey1 | Red Bull (2022) | 21 | ||
@xTheox | Alpine (2022) | 88 | ||
@Tom Danel π«π· | Aston Martin (2022) | 15 | ||
@shyguy2008 | 92 | |||
@Márk | Alfa Romeo (2022) | 25 | ||
@RampageJackson | Alpine (2022) | 66 | ||
@MrZOCKson | Alpine (2022) | 25 | ||
@aurelijusmiciulis | Alfa Romeo (2022) | 80 | ||
@MinTy | Mercedes (2022) | 23 | ||
@zanelu | Mercedes (2022) | 28 | ||
@Yohann | Ferrari (2022) | 69 | ||
@Arphaxad | Red Bull (2022) | 89 | ||
@donuthole | McLaren (2022) | 78 | ||
@maxduca | Alfa Romeo (2022) | 27 | ||
@KStrike | Aston Martin (2022) | 42 | ||
@richyb | Haas (2022) | 74 | ||
@Siny | Williams (2022) | 32 | ||
@victorwasa | 19 | |||
@Fehler3 | McLaren (2022) | 96 | ||
@bachelightyear | McLaren (2022) | 43 | ||
@steviejay69 | Williams (2022) | 66 | ||
@tYsU^ | Alpine (2022) | 21 | ||
@strusieek | McLaren (2022) | 42 | ||
@SirBrokealot | 42 | |||
@KeystoneAlfisti | Ferrari (2022) | 88 | ||
@Neo Sieben | 0 | |||
@pezi | McLaren (2022) | 76 | ||
@MadLad | 0 | |||
@Nevoππ€ | Haas (2022) | 24 | ||
@tudor900 | Haas (2022) | 72 | ||
@Exodium | Red Bull (2022) | 2 | ||
@okaui | Ferrari (2022) | 15 |