top of page
Untitled-249.jpg

Our Racing Rulebook

Our rules. Please read these carefully and respect them when you race and interact with us and our community.

Starting with 1.1: All oNiD admins are volunteers. Please treat us how you would like to be treated. We understand you may not agree with a decision or situation that goes against you but this is not an excuse for abuse.

Last Updated: Nov-2024

1. General Rules

1.1     All oNiD admins are volunteers. Please treat us how you would like to be treated. We understand you may not agree with a decision or situation that goes against you but this is not an excuse for abuse.
1.2     Drivers must never exploit known game glitches or loopholes.
1.3     Use of cheat software, scripts, or anything outside of the terms & conditions of the sim you’re racing on are not acceptable.
1.4     Respect all other drivers and event organisers by driving professionally, never disadvantage yourself deliberately during any session.
1.5     No discussing incidents in any public discord voice channel or public text channel. Be courteous to other users in public voice channels, in-game chat, Twitch and Discord chat.
1.6     Never use the in-game chat box during qualifying or race sessions.
1.7     There is a Mandatory Driver Briefing before each race, everyone (or one driver per team) needs to be in the appropriate Voice Channel at the specified time and remain in the pit lane during this time. Once finished, you are free to join private channels or stay in the oNiD one.
1.8     Where a social event does not have a Driver Briefing we still expect the same driving standards as usual in line with .
1.9     If there is a server issue or any other serious problem during a session this will be communicated within the in-game chat box or discord.
1.10     Where different classes are utilised within a race/league oNiD Racing may adjust drivers classes if it’s identified the selected class is not suitable for a driver/team.
1.11     Only sign-up to races and leagues you intend to take part in. No shows for races or leagues with no notification may result in bans from current/future races and seasons. Use the driver ‘skip rounds’ function within SimGrid in line with the relevant League rules where required.
1.12    Rage quitting races without an adequate reason is not permitted. If you have damage pit, fix the damage, and continue your race. Repeat offenders may be banned from current/future races and seasons.
1.12     oNiD Racing reserves the right to update these rules where required. Drivers will be notified of any updates.
1.13     oNiD Racing reserves the right to any remove any members from the Discord and Race Events where severe breaches to the oNiD Racing rules are encountered. All decisions go through the oNiD Execs to ensure clarity and fairness when dealing with rule breaches.

2. Practice Server Rules

2.1     Please follow the oNiD Racing rulebook in the practice servers we provide, including all rules within section 1.
2.2     We look to provide practice servers where available; however, this does not mean all race events will have an associated practice server setup.
2.3     Where available the event BOP and weather conditions will be assigned to the relevant practice server. oNiD Racing reserves the right to update the BOP/weather as we see fit prior to the event, so please ensure you check the SimGrid page/Discord for any changes to the event prior to this commencing.

3. General Race Server Rules

3.1         Drivers found to be intentionally abusing track limits to their advantage will be disqualified from the event at the first available opportunity. 
3.2     You must never intentionally hit any other car at any point of any session. You may be banned from current/future races and seasons, and all instances will be passed to the oNiD Execs to investigate.
3.3    Automatic penalties given to drivers by the server will not be removed, such as drive-through penalties for jumped starts or track limit violations.
3.4     Practice sessions pre-race do not follow the same blue flag rules as Qualifying or Race sessions. All cars are entitled to practice what they wish, so for example if you’re practicing a qualifying lap please find a space to do this.
3.5     Unless otherwise instructed within specific race briefings please follow the pit entry and exit lines at all times.
3.6     Return to Garage (RTG) is allowed in all oNiD Racing sessions. Please ensure you pull over away from the racing line predictably and safely to do this.
3.7    Causing yellow flags for multiple laps, either parked at the side of the road, or idling in the pitlane, is not accepted and may cause your car to be disqualified from the session.
3.8     Excessive use of flashing headlights is not permitted. It’s recommend flashing of headlights is limited to blue flag overtakes, and only in moderation. This is a reportable offence, and consistent offenders will be penalised.
3.9     Reminder that this is an inclusive community with all levels of racing experience. Behaviour identified as unsportsmanlike may result in penalties or bans being applied.

4. Qualifying Rules

4.1     No racing in qualifying under any circumstances.
4.2     If you are not on a valid qualifying lap, please do not block any cars who are on a valid qualifying lap. This also applies if you invalidate a fast lap.
4.3    You need to make room for yourself during a qualifying session. If you are being held up by another car on a valid lap that is unfortunate, but you must not interfere with their qualifying session.  
4.4    Be aware of cars entering or exiting the pits.
4.5    Drivers must always try to set a lap time that is representative of their ability. Intentionally not setting a time or artificially manipulating your starting position by any other means is strictly prohibited and will be penalised at the first available opportunity.
4.6     For split qualifying sessions with different classes of cars please do not leave your pit box until the time when your qualifying section begins.
4.7    At the end of your split qualifying section please finish the lap in line with the driver briefing and return to garage from the track when safe to do so.

5. Blue Flag Rules

5.1    Faster Car Must Pass Safely, slower car must behave predictably.
5.2    Slower Car must allow the move to happen and not defend the position.
5.3    We encourage slower drivers to lift off and allow faster cars through at the earliest opportunity.
5.4    Faster car may flash to indicate they are within one second and ready to pass, but this must not be excessive. Drivers are encouraged to report excessive flashing as per rule 3.8.
5.5    Failure to allow a blue flag pass to happen, through active blocking, or actively not allowing a pass to happen willingly, will result in penalties.

6. General Race Rules

6.1     We encourage drivers not to wait if they feel they caused an incident, this might cause more incidents.
6.2    Drivers must Obey the session rules regarding pit stops. Deliberate failure to do so will see you disqualified from the event afterwards.
6.3    Intentionally hitting other cars after the finish line is a serious offence and may result in removal from a current/future season.
6.4    Drive-through and stop-go penalties must be taken within the outlined time period.
6.5    If a penalty is applied in line with 6.4 in the final two laps the sim will automatically apply a time penalty to the affected driver/team and will not be removed.
6.6    Red flags may be thrown after a major lap 1 incident, or due to a server issue. These are used at the discretion of oNiD Execs, and will be communicated via the in-game chat window of the relevant sim.

6.7    Excessive weaving and late changes of direction while defending is not accepted.
6.8    Actively moving under braking to defend a position is not accepted.

6.9    Reminder to drivers that where the overtaking car does not have a sufficient overlap when making a move the overtaking car may be deemed as at fault for an incident. For clarification an overlap is defined as ‘the car behind having their front wheels level with the rear wheels of the lead car’. 

  • Thus ‘dive-bombing’ and expecting cars in front to move out of the way, or late moves with cars in front already turning for corners are situations punishable with penalties if incidents are caused.

6.10    Where a car has an overlap you must ensure you leave sufficient space for them without running them off the track.

7. Endurance Event Rules (ACC Specific)

7.1    The 1st driver (marked as the Team Manager on SimGrid) must enter the race server first. Once they have successfully joined, other team members can join.
7.2    If a disconnect occurs for the active driver during the race all drivers must disconnect and follow rule 7.1 to rejoin the server.
7.3    Failure to follow rules 7.1 and 7.2 may mean you are unable to join the team and complete the race.
7.4    The race server will not be automatically restarted if you break your entry by not following rules 7.1 & 7.2 – as a team it is your responsibility to follow these rules and not potentially impact other teams entries.
7.5    The custom driverswap command (&swap) can be utilised during the event. Given the issues sometimes encountered utilising this command using this command within the race server is at your own risk.
7.6    All drivers must complete at least one stint to avoid post-race penalties.
7.7    Driver stint timers must be followed at all times – penalties automatically assigned will not be removed.
7.8    Max driver timers must be followed at all times – penalties automatically assigned will not be removed.
7.9    Intentional disconnects in any session to reset tyre usage/brake usage with result in severe penalties being applied within race sessions, potentially leading to your team being disqualified.
7.10     Where qualifying falls on the same day as the race start your driver who does your fastest lap in qualifying must start the race.
7.11    Where qualifying is completed the day(s) before the race any driver may start the race for your team.
7.12     As per usual standard oNiD Racing Rules if you have any issues raise a manual report or appeal. Calling out other teams in Discord, arguing with other drivers and organisers etc will not be tolerated and will be dealt with accordingly.
7.13    Please ensure you have read and understood the above rules. Taking part in our Endurance events is subject to the above, and all teams have a responsibility to understand these rules and attend the required Driver Briefing.

8. Custom Livery Rules

8.1     Custom liveries are utilised within some of our Events. Please see our Discord for further details.
8.2     When creating custom liveries small oNiD logos can be displayed; however please only use oNiD Partners liveries with prior agreement with the partners themselves.
8.3     Downloading and adapting oNiD liveries is not accepted; any instances of this occurring will be raised via oNiD Exec.
8.4     If you utilise a livery please ensure you are entitled to use the livery; for instance a team livery should only be used by a team driver. This includes the use of oNiD Racing liveries; these should only be used wtih prior permission from oNiD Exec.
8.5     oNiD Racing prides itself on being an inclusive community to all; as such, please ensure any custom liveries are appropriate for broadcasting and to other users. Any offensive messaging, political statements, sexual/NSFW images etc will not be tolerated.
8.6     Queries around custom liveries can be raised with Ben Brown/Ben Myatt if unsure over suitability.

9. Incident Reporting (Post-Race)

9.1     We encourage drivers to submit reports if they encounter issues during a session.
9.2    Information regarding how to submit post-race incidents is available on our Discord, and will be made clear in your relevant league Discord channels.
9.3     For non-live stewarded events you have 24 hours from the end of the race in question to submit your forms.
9.4    You must follow the incident report submission guidelines when submitting a report. Any reports received which do not meet these standards will automatically be rejected.
9.5    All outcomes will be communicated with the drivers and explanations will be available upon request.
9.6    If you receive a penalty in a post-race report you have up to 24 hours to appeal this penalty with new evidence if you wish.
9.7    After one appeal is submitted and resolved no further appeals can be submitted regarding the same issue.
9.8    Section 9 Incident Reporting only applies to sessions without live reporting. Live reporting is covered separately within Section 10 along with additional details on what may be penalised.

10. Incident Reporting (Live Steward Events)

10.1     All reports will be investigated with a decision being posted in-game and on Discord.
10.2    All incident reports will be listed outlining the incident and relevant decision from the Stewards. This will be linked via the appropriate channel in Discord.
10.3     Live stewarding will be watching the event and tracking in-game incidents to note potential incidents.
10.4    If you feel an incident has occurred but it wasn’t identified on the live steward log, please use the incident report form provided in the relevant discord channel to report any incidents.
10.5     Penalties for the event are set out as follows:

  • 1st – 3rd Penalty: 5/10/20 second time penalty (depending on incident severity)

  • 4th Penalty: 15/30 second time penalty (depending on incident severity)

  • 5th Penalty (and subsequent penalties): 30 second penalty or Stop-Go penalty (depending on incident severity)

  • Warnings may applied where an incident is minor or no advantage being gained

  • Where continuous penalties are given (anything past 4 Penalties) or severe rule breaches (intentional wrecking etc) the team in question may be disqualified from the race if they are deemed a danger to other teams.

10.6     If a team causes any incident on the first lap a more severe penalty than the above penalty instances may be applied.
10.7     If a team is determined to be the cause of a Red Flag incident the Stewards will apply the appropriate penalty after the race restart has been completed.
10.8    Unsportsmanlike conduct, such as intentional wrecking of other cars, will result in immediate disqualification for a team.
10.9    If you require further explanation as to why a penalty has been applied, or wish to appeal a penalty please complete an appeal form and a response will be completed. 
10.10     All oNiD Stewards follow our own stewarding guidelines which look at the following :

  • Causing a Collision

  • Forcing a Car Off-Track

  • Poor Rejoins

  • Qualifying/Practice Infringements

  • Blue Flag Infringements

  • Poor Driving Standards

  • Intentional Incidents

  • Unsportsmanlike Conduct

  • General oNiD Racing Community rule breaches

  • General Dangerous or Reckless Driving

10.11    If an appeal is received the Race Director will endeavour to remove any outstanding penalties whilst the item is investigated.
10.12    Appeals are investigated by a different Race Steward to whom gave the penalty, or the Race Director depending on severity.
10.13    Once investigated Appeal outcomes are posted on Discord and the relevant reporting sheet, and any penalties (if still relevant) will be reapplied.
10.14     Towards the end of a race, usually around 15 minutes to go, Race Control will close live report outcomes. Any further identified live reports will be completed post race.
10.15     Manual reports can be submitted only up to 30 minutes after the live stewarded race has been completed.
10.16     Outstanding race reports will be posted on Discord with any changes to the Race Results being completed prior to the full race results being published to SimGrid.
10.17    Steward decisions are final. Aggression towards organisers, stewards, or other participants will be dealt with appropriately.

bottom of page