One Off Events - Rules & Regulations

0.0 - Contact Information


Should you have any questions please contact CFS via our email @ chequeredflagsimsports@outlook.com OR
Contact us via our Discord channel @ https://discord.gg/ucNBAxH Please ensure that you include your name + team before sending your message.




1.0 - General Information


1.1 - Content (Cars)
Please check the relevant news post for required content for your chosen event.

1.2 - Content (Tracks)
Please check the relevant news post for required content for your chosen event. 1.3 - Grid Size Grid size is specified by the content being used. Typically the event will use the maximum grid slots available. Please check the relevant news post for the grid slots available. 1.4 - Reserve Teams Should the event become full, reserve teams can be accepted, with contact being made via email and/or Discord to confirm their attendance should a vacancy appear. 1.6 - Event Times Please check the relevant news post for event times. 1.7 - Track Conditions Track conditions typically replicate real life weather, Please check the relevant news post for details relating to your event.




3.0 - Qualifying Procedure


3.1 - For each event, drivers will be provided a window to complete their qualifying laps. 3.2 - If there is more than one class, the Qualifying session will be divided equally. Please check the relevant Forum post for these details. 3.3 - If the event requires Teams, then one must be elected to Qualify for the team. 3.4 - The driver that has qualified for the team MUST start the race. 3.5 - Other teams mates are NOT permitted to join the server while Qualifying is in effect to avoid high ping/s. 3.6 - If a driver is on his "out lap" they MUST NOT block or obstruct other cars on a "flying lap", any blocking will result in a penalty. 3.7 - If a driver gains time by cutting the circuit, they must surrender the time immediately or face getting a penalty after the race start.




4.0 - Race


Warm Up Lap 4.1.1 - The driver who has Qualified MUST start the race for the respective team. They will have 60 seconds to GRID their vehicle before the race begins. 4.1.2 - If a warm up lap is required, all Drivers MUST remain BEHIND the car ahead of them, remaining in a two wide formation at all times. 4.1.3 - Near the end of the warm up lap, seperate classes are expected to leave a gap of 5 seconds to the cars ahead to avoid a Turn 1 accident. 4.1.4 - All Teams are to IGNORE the green flag announced by the game. (Excludes standing starts) 4.1.5 - The Race will begin when the leader of EACH class reaches a designated point on the start/finish line. This start line is confirmed in the driver briefing and on our discord channel. 4.1.6 - IF the LEADER does NOT start the race once they reach the designated start line, the rest of that class can still go racing. 4.1.7 - If the LEADER, or any other driver begins the race before this time, then they shall receive a DQ penalty 4.1.8 - Drivers should not apply the brakes suddenly in an attempt gain temperature. Those who do so and cause a collision on the warm up lap will be reviewed. Race 4.2.1 - Drivers are expected to remain "calm" in the first few laps of the race to avoid unecessary collisions/DNF's. 4.2.2 - All Incidents/Collisions that occur on Lap 1 of the event, shall be penalised harshly, so ensure the move in done cleanly. 4.2.3 - Once the race is underway drivers must be aware of their surroudings at all times while in charge of a car. 4.2.4 - Teams must complete the race distance under their own power. Teams who retire before the chequered flag will be classed as DNF. 4.2.5 - Teams who suffer extensive damage will be required to pit for repairs to avoid posing a risk to other Teams. 4.2.6 - If a large accident occurs, a message will be posted in the Discord Channel advising drivers to take caution. 4.2.7 - Drivers are not permitted to type in chat when on the server to avoid distracting other drivers. Restarts 4.3.1 - Restarts may occur in order to: - Allow disconnected teams to rejoin (if a large quantity have dropped) - Allow the server to reboot after suffering a malfunction 4.3.2 - Once the race has begun without issue, it will not be restarted. 4.3.3 - If they Server crashes before the chequered flag is flown, points will be awarded to the teams based on their position at the time of the server failure. Spectators 4.4.1- Spectating is forbidden while the race is underway, please use our youtube channel to view the race. 4.4.2 - If you are conducting a driver change, please do so within a 5 Minute window. 4.4.3 - Drivers who sit in the server spectating will be kicked, and may find themselves unable to rejoin to help finish the event.




5.0 - Driver Stints + Pit Stops


Driver Stints 5.1 - Please check the relevant news post to confirm stint limitations/minimum requirements for your event. 5.2 - When conducting your driver change, you are permitted a window of 5 minutes to change drivers without being liable to a penalty. 5.3 - Once a driver steps into the car, they are required to complete X minutes of driving time before they are allowed to get back out again. (pit lane time does not count). Please check the relevant forum post for this information as each one is different. 5.4 - Once 5.1 and 5.3 have been satisfied, there are no limitations on the driver stints. Note: Not all One Off Events require the above Regulation, please check the relevant news post to confirm. Pit Entry/Exit 5.5 - When entering or exiting the pits, drivers must NOT exceed or go over the SOLID white lines, Those seen doing so may find themselves being issued a drive through penalty. 5.6 - When driving in the pit lane, drivers are required to only use the higher lane (if the track provides one) after they have reached top speed. 5.7 - When driving in pit lane drivers are expected to respect the pit lane speed limit. Any breaches shall be issued a penalty.




6.0 - Track Limits


6.1 - Do NOT exceed the track limits or Cut any part of the circuit, with the intention to gain time unfairly against another competitor (the track limit is defined by the outer white lines of the circuit) 6.2 - A car is considered off limits when they have all four (4) wheels outside the Solid white lines. (Pictures below as example) 6.3 - If there are any exceptions to rule 6.1 + 6.2, it shall be highlighted in the driver briefing prior to the event. 6.4 - It is deemed acceptable for a car to exceed track limits if they are avoiding an accident. 6.5 - During Qualifying, if a driver exceeds track limits, they must surrender the time immediately. If they continue to complete the lap without doing so, a drive through penalty will be issued at the start of the race. 6.6 - The only way to have this penalty removed, will be to post a faster lap time within the track limits during the session. 6.7 - During the Race, teams will receive warnings relating to track limits. If the team fails to comply they shall receive a penalty. 6.8 - All warnings and penalties are posted on our discord channel. We advise that a team member keeps an eye on discord, ensuring there are no outstanding penalties for your team.




7.0 - Behaviour/Driver Responsibility


General Behaviour 7.1.1 - It is the Responsibility of the driver to behave in a courteous and acceptable manner at all times when on and off track. Intimidation, trash talking or insults will not be tolerated on any level and may lead to the team being removed from the community 7.1.2 - Any form of cheating will result in a community ban. 7.1.3 - If a team is applying, they are responsible for the behaviour of their drivers both on and off track. If a driver within the team cheats, is disrespectful or breaches CFS rules, the team will be penalised. (each case is reviewed, the nature of what has happened will determine the outcome) 7.1.4 - Drivers and teams are expected to practice and prepare for upcoming events. A consistent failure to do so may result in the teams removal from the championship. 7.1.5 - If a team is not going to attend, they are expected to relay this information onto the admin team in writing in good time. Failure to do so may result in being black listed. 7.1.6 - CFS maintains the right to remove any team/driver from its championships/events provided their is sufficient evidence to support their conduct does not meet CFS standards. Track Behaviour 7.2.1 - Do NOT block the track, or position your vehicle with the intention to cause another competitor to Lose time, have an accident or Collide with your own vehicle or another object. 7.2.2 - When rejoining the circuit after an accident, it is the responsibility of that driver to ensure that they do so without impeding or causing another competitor (Whether they are rejoining or not) to lose time, have an accident or collide with another vehicle or object. 7.2.3 - When defending a position, competitors are restricted to making ONE Defensive maneuver in order to defend that position. Any Competitor who Blocks in an unsportsmanlike manner is open to investigation. 7.2.4 - When defending a position, the Defender must make his intentions clear. Defenders who force another vehicle off track (as a result of defending “too late”) will find themselves under investigation 7.2.5 - When attacking or overtaking, the vehicle must be alongside in order to have "the right" to be there. Typically an acceptable position would be to have the nose of the car up to the defenders drivers door. It is on the attacker to ensure that they pass cleanly provided the defender has complied with 7.2.3 & 7.2.4. Behaviour When Under Flags Yellow Flag 7.3.1 - Local yellows will be in effect on race day alongside Code 80's 7.3.2 - When the local yellow flag is displayed (Typically for a corner/sector), all vehicles must reduce their speed until they have safely passed the incident. No Overtaking is permitted during the Yellow flag regardless of class. 7.3.3 - If a further incident occurs during a Yellow sector, they will come under review by race control.

Code 80's 7.3.4 - If the incident is of significant size, a code 80 will be issued by race control. 7.3.5 - In the event of a Code 80, a countdown from "Ten" (10) will be announced by race control on TeamSpeak. Once Race control States "Code 80 in effect", all competitors must apply their pit limiters immediately. 7.3.6 - Once the incident has been cleared, race control will count down from "Ten" (10), before stating "Green Green Green". Only on the call of Green x3 can competitors come off the pit limiter and return to racing pace. 7.3.7 - Example of Code 80 Communications:
- Code 80 announced - "Code 80 in 3, 2, 1, Code 80 in Effect" - Back to Racing - "Standby for Green in 3, 2, 1, Green Green Green"
7.3.8 - Failure to adhere to the above will result in harsh penalties. 7.3.9 - If you have been involved in the incident that caused the code 80, you must still return to the pit lane on the pit limiter. Blue Flag 7.4.1 - Blue flags MUST be obeyed by all cars whether in the same class or not. 7.4.2 - when the blue flag is displayed drivers must prepare to concede the position in a safe manner. 7.4.3 - Drivers are expected to remain “predictable” when conceding their position and should remain on the racing line as much as possible to allow the faster car to judge their overtake easily. 7.4.4 - If you are battling with someone on the same lap as you when the blue flag is displayed, you may continue to battle for a period of 1 lap before being required to concede to the car behind causing the blue flag. 7.4.5 - Should a car fail to concede their position while under a blue flag (and without good reason) then they shall receive a drive through penalty 7.4.6 - Definition of a Battle: So close to the next competitive car ahead that an overtake is possible.
Race Pace

7.5.1 - All competitors are expected to practice for ALL events hoasted by CFS.
7.5.2 - When out on circuit, all competitors must meet a target race pace of 104% from the leader in class.

Example: Leaders Race Pace = 2 minutes = 120s Divided by 100% = 1.2,
1.2 x 104% = 124.8 divided by 60 = 2m 08s - 2m 08s is the slowest a team can race without being reviewed.

7.5.3 - The purpose of this regulation is to ensure that teams practice for the events, as well as promoting closer competition within our events for a better experience.
7.5.4 - Those who fail to meet the 104% could find themselves removed from the event due to posing a safety problem 7.5.5 - CFS will remove Any car that drives erratically or poses a risk to other competitors, IF, after several warnings there is no sign of improved performance.




2.0 - Driver Briefing


2.1 - Before the start of Qualifying, all teams must have a minimum of x1 driver in the "Briefing Room" channel on Discord./Teamspeak (https://discord.gg/ucNBAxH) 2.2 - During the driver briefing drivers are expected to not "Talk over" or interupt the organisers unless invited to do so. 2.3 - Drivers are free to ask questions once the organisers have completed the driver briefing, or unless prompted to ask questions after a certain topic. 2.4 - It is mandatory for the driver starting the race to be present during the driver briefing. 2.5 - Should a driver fail to attend the briefing, they will not be allowed to participate in the event. 2.6 - Check the relevant news post to obtain DB date & time.




9.0 - Results


9.1 - All results are logged and placed on a database. These logs will then we used to determine a driver/teams performance. 9.2 - Once the data has been evaluated, teams/drivers may find themselves invited to official championships such as the WSCC.
9.3 - All results will be posted on our website




8.0 - Penalties


8.1 - If live marshalling is in effect for the event, then penalties can be awarded by the stewards during the event. 8.2 - Should a team receive a penalty/warning, they will be notified on Discord in the relevant chat channel. 8.3 - The team/driver will have x3 laps to perform the penalty or face being disqualified from the event. 8.4 - Each incident is reviewed from several angles, with the outcome being final 8.5 - If the GAME issues your team a penalty, please contact the race director to have it removed. (penalty will only be removed if deemed unfair by race control) 8.6 - Incidents must be reported to race control during the event itself, Reports received after the race may be rejected depending on the circumstances. 8.7 - Penalties can NOT be served as part of a normal pit stop. 8.8 - Examples of penalties - Warning (typically for exceeding track limits) - Drive through (for various reasons) - Stop&go - Race ban - Championship Ban - Full Community Ban





Click on each box to expand and read the contents. Regulations are split into categories as seen below

Copyright © 2020-2022 ChequeredFlagSimsports.com .All Rights Reserved