Rules and Regulations
V0.5 MAR 2023
V1.0 APR 2023
V1.1 MAY 2023
1. Competition Overview
1.1 Tournament Overview
The Moza Endurance Championship is an endurance racing competition provided by Simracing.GP and Moza Racing designed to bring the teams together in a competitive race environment
This competition will be organised by Simracing.GP using Assetto Corsa Competizione. The SGP Endurance Series will feature up to 500 teams, each with 3 drivers split into grids of 32 teams.
Round 1 – 04-JUN-23 1400UTC – 6 HOURS OF WATKINS GLEN
Round 2 – 02-JUL-23 1400UTC – 6 HOURS OF SPA FRANCORCHAMPS
Round 3 – 06-AUG-23 1400UTC – 6 HOURS OF BATHURST
Round 4 – 03-SEP-23 1400UTC – 6 HOURS OF VALENCIA
Round 5 – 01-OCT-23 1400UTC 6 HOURS OF MONZA
Round 6 – 15-NOV-23 – TBA
*These tracks maybe replaced by a track from the upcoming DLC for Assetto Corsa Competzione, team managers will be made aware of any changes within 14 days of the round
Visit Simracing.GP for more information about the schedule of the Simracing.GP Endurance Series by Moza Racing
In order to participate in the Simracing.GP Professional Trophy, each team must:
- Own an original copy of Assetto Corsa PC Version playable on Steam
- Own the relevant DLC required to compete in the competition.
- Have a valid Simracing.GP account, including associating their discord account to your driver profile
- Set driver profile to driver’s real name and surname.
- Minimum 16 years of age.
1.4 Simracing.GP Discord
All competition relevant communication will be handled in the Simracing.GP Racing DISCORD SERVER. Access to this server can be obtained via this link – https://discord.gg/TurGbmR3ar
This will be the main hub for the competition when it comes to communication and support.
To ensure a fair playing ground for all participants, the organiser reserves the right to request replay footage and MOTEC data from drivers at any point of the tournament, to which the participant must adhere within the time frame specified in the request. Failure to do so may result in the participant’s removal from an event or the entire competition and any other subsequent competitions held by the organiser.
1.6 Driver etiquette and code of behavior
The organiser considers the code of conduct a fundamental aspect in every esports competition. It is precisely for that reason that if any Driver involved in the competition acts in any of the following ways, the organiser has the right to disqualify the player with immediate effect.
- Unsporting conduct (insults in the game chat directed to other players, marshalls, organiser etc);
- Driver Ping being unstable or over the agreed upon limit of 150m/s for a consistent period of time.
- Obscene insults to the organising staff and subjects involved (online and offline) on any social platform, websites, forums etc;
- Any kind of cheating will bring the guilty player to an instant ban from the championship and from our future events;
- Please beware to keep discussions, feedback and opinions in a reasonable and constructive manner.
- Any postings on social media, discords or other communication channels which damage the brands involved in the ADAC SimRacing Expo, its competitions, employees, exhibitors or partners will be sanctioned.
The full details of the prize pool are yet to be released, V1.2 will come once the prize pool has been announced by Moza Racing.
For this competition, we will be supplying all teams with a sponsor layer for their cars to be used during the competition. All cars racing in SPLIT 1 must use this layer as it will hold the relevant branding for the competition.
Teams are allowed to customize the decals layer to their own specification to design a car they will identify with whilst racing.
During the competition, teams will be able to upload their own custom liveries. Each team is responsible for its own liveries and the organisation holds no responsibility to ensure that they are uploaded correctly to the livery sharing platform.
To upload your livery, please complete the following steps:-
i) Head over to the Awesome-Simracing livery sharing platform
ii) Create an account, and follow the instructions in the FAQ
iii) Add your livery to the Simracing.GP Community Collection relevant to your competition.
1.8.1 Livery Expectations
We will be working with a variety of partners during this competition. Their branding is expected to be visible on all cars competing in the competition. We will supply a sponsors file with relevant branding in expected positions for each round of the competition via the Simracing.GP Racing discord server. Brands not related to the competition are not to be used on custom liveries for the competition, unless they have an exception from the Simracing.GP Staff. This exception can be applied for by contacting the Simracing.GP Staff via discord.
1.9 Broadcast Expectations
During all rounds of the competition, SPLIT 1 we will be broadcasting the races live at https://twitch.tv/SGP_Racing
2. Competition Format
Once a team manager signs up for the event, they will have 24 hours to complete their roster of 3 drivers.
Teams who register to take part and do not take part in the event will have their drivers access to all future Esports competitions on Simracing.GP revoked for 12 months
The race format for the Races is as follows :-
Free Practice – 10 Minutes
Qualifying – 15 Minutes
Race – 360 Minutes
2.1 Points distribution
At the end of every round, the cars involved will be awarded the following points
|Pos.||Qualifyingapplied post race||Race||SOF Multiplier (Up to)||Points Multiplier|
Bonus points are up for grabs for teams who race in the same machinery for multiple rounds of the competition.
For every additional round a team stays in the same car, they will receive 5 additional points for each driver, giving a total of 25 additional points up for grabs for a driver who uses the same car in all 6 rounds.
In case 2 or more teams end up with the same amount of points, these will be used as criteria to break the ties:
- Most races won;
- Most second places, then third places, and so on;
3. Incidents, Reporting and Stewarding
We will be providing live stewarding for each race event.
All past and currently investigated incidents are available in the stewards race report.
The location of the report will be made public in the relevant race discord channel.
Should an incident not be on the stewards race report, a driver can submit a protest and have said incident be reviewed without using up one of their two protest attempts.
Drivers will be made aware of impending penalties via the in-game text chat during the race itself.
Drivers will be issued the following penalties during any competition race. Please make yourself familiar with these. They are designed to be severe so that drivers are more safe out on track.
3.1.1 Software Provided Penalties
The Race Director will not remove any penalties issued by the software for issues including, but not limited to, being out of position at race start, or exceeding the warranted 3 track cuts during an event
3.1.2 Racing Penalties
Drivers will be awarded a variety of penalties should any of their actions become noticeable to our stewarding team. The stewarding team can issue any penalty they feel fair after reviewing the incident. The penalty is not expected to reflect the outcome, but punish the decision making of the driver to cause the incident in the first place.
126.96.36.199 Warnings: Drivers can be awarded up to a warning for any minor contact. Multiple warnings can lead to a penalty being given for an incident that would usually reward a warning.
188.8.131.52 Major Incident penalties include, +5, +10 +15 Second Penalties and +30/+60 Second Penalties added to the drivers total race time. These penalties will be given as a result of review of an incident, the penalty is not an ‘eye-for-an-eye’ penalty to directly reflect the outcome of the incident, but as a deterrent to cause further incidents.
The Race Control team also have the ability to give a driver or team a Drive Thru Penalty, or Stop & Go Penalty of either 10 or 30 Seconds should they feel that a driver caused an incident that warrants a severe penalty such as this. An example of this may include causing avoidable collisions with multiple cars or deliberate attempts to affect another cars race
184.108.40.206 After 3 Major Incidents, The Race Director has the right to DSQ your car from the race should any further incident occur.
3.1.3 Blue Flagged Vehicles are not to fight drivers on the lead lap. They can continue to race as normal and drivers on the lead lap are to ensure they make a safe overtake on any cars that have been blue flagged.
Cars are allowed to get a lap back if they are faster than the car in front. Drivers must be civil and respectful if a lapped car is attempting to gain a lap back and not go out of their way to defend from them.
3.1.4 Non-Racing Related Penalties
Any driver committed to performing un-sportsperson like conduct, will be subject to race penalties, and potential disqualification from the competition. This includes, but is not limited to, messaging using in-game text chat during live race track, deliberate removal of any of the braking markers or pit boards or abusing game mechanics to gain an advantage.
Should you wish to protest a penalty on your car, you can do so using the Protest Form.
The protest must include video footage of the incident with all of the following views:
- Your Cockpit view with the Steering Wheel and HUD visible
- Your Chase cam with HUD visible
- Their Cockpit view with Steering Wheel and HUD visible
- Their Chase cam with HUD visible
- The Helicopter cam with HUD visible
The protester must make sure to include 15 seconds before and after the incident and that the footage is normal 1x Speed. The video footage may be recorded with a screen capturing software (OBS, ShadowPlay, etc.) or a smartphone and uploaded to YouTube. If any of the named criteria are missing, the protest will be dismissed.
The Race Director will make a decision before the next event and will announce it publicly in the relevant channel on Discord. Should the Race Director decide in favour of the protester, they will not lose this protest attempt. If the stewards decision was upheld or the decision is against the protester, the protester will therefore lose this protest attempt.
Cars are allowed 2 Protests during each a single event; or 2 protests during an entire championship, they must be submitted on the official discord server.
4. Disconnecting during a live race session
Should a driver or a team disconnect during any session on the server, they must contact a steward to request to rejoin the server. The steward will inform you when you are allowed to join the server so that you do not affect any other team’s race.
4.1 Full Course Yellows & Red Flags
In the very rare occasion that we would need to initiate a Full Course Yellow (FCY) or Red Flag situation in the race event, we will communicate this with the drivers via the in-game text chat.
During a FCY we ask drivers to drop down to the pit-limiter speed and apply the pit-limiter by the end of the FCY Countdown. Cars can return to full speed at the end of the FCY Countdown.
Examples of when we may use FCY would be for reconnections of cars.
We will only issue a Red Flag to the race should 2 reasons happen, the first is simple, any major impending server related issue, the race will be red-flagged and restarted with the grid order at the previous hour mark set.
The second would be for a major incident during LAP 1 of any race event that involved 33% of the cars taking part. This decision will only be made by the Head Steward for the start of the race. The race will be restarted using the starting grid.
4.2 Server Protection
With the recent increase in the number of DDoS attacks on sim racing events we deemed it necessary to improve the security of our servers. All Simracing.GP Sanctioned Competitions will run the “Server Protection” option in its competitions.
With this turned on, drivers will need to login to Simracing.GP from the PC they are planning to use for the race before the server launches. This will enable SGP to detect the exact computer which is participating in the event. Quite simply, if your PC is not recognised you won’t be able to see the server in game.
Some things to note:
* You do not need to keep your web browser open while your game is running
* We will ignore mobile devices such as smartphones and tablets, so you can continue to browse SGP ahead of your event without fear that your computer won’t be detected
* If you login to Simracing.GP from a different laptop or desktop before the start of your race, make sure to log back in from your gaming PC before the start of your race.
For more information related to Server Protection, please check out this short video – https://youtu.be/JA7aSEt4ImY
4.3 Server Restarts
Each team is required to join the server in the correct order, with driver 1, denoted by the ‘crown’ icon on Simracing.GP connecting the server first, before instructing their teammates to join the server.
The server will not be restarted to allow for teams to join in the correct order.
In the event of a server crash, the Race Director will coordinate with the Server Admin Team and the competing Team Managers an outline plan going forward. Should a race be Red Flagged and unable to be restarted points will be rewarded for the positions at 25/50/75% race distance.
Should a Race be Red Flagged and able to be restarted, the grid will be set at the last recoverable point in the previous race. This will be communicated to the Team Managers at the point of decisions being made.
The Competitions Promoter (Moza Racing) is responsible for fulfilling prizing requirements for the competition. Any drivers who win a prize during the competition should contact the promoter regarding their prizes should they have any issue.
Simracing.GP is not responsible for any extra charges relating to prizing including and not limited to localized tax duty charges and additional shipping costs. Those will be the responsibility of the prize winner.
Any action deemed by the stewards to represent unsportsmanlike conduct may be penalized at their discretion.