Trofeo Sprint Cup- Rules & Regulations

0.0 - Contact Information

Should you have any questions please contact CFS via our email @ OR
Contact us via our Discord channel @ Please ensure that you include your name + team before sending your message.

1.0 - General Information

1.1 - Content (Cars)
You will need to have access to the Lamborghini Huracan Super 2015 on ACC (Comes as standard)

1.2 - Content (Tracks)
You will need to own/have access to the following circuits.
- Brands Hatch GP
- Catalunya GP
- Laguna Seca - Misano - Nurburgring GP - Spa Francorchamps 1.3 - Grid Size A Max grid size of 30 Will be allowed for the series. 1.4 - Reserve Teams Should the grid 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 ALL races will take place on WEDNESDAY, followed by the times outlined below in GMT:
Practice -18:00pm
Briefing - 18:45pm
Qualy - 19:00pm
Warmup - 19:15pm
Race - 19:20pm 1.7 - Track Conditions Track conditions WILL replicate real life weather, as best as possible (it will be winter after all). Information will be posted on discord closer to each round as to what the conditions will be.

3.0 - Qualifying Procedure

3.1 - For each event, drivers will have 15 minutes to complete their qualifying lap. 3.2 - There is NO limit to the amount of Qualifying laps you can do during the 15m window. 3.3 - Drivers CAN return to the pitbox by pressing ESC, however, drivers are responsible for the placement of their vehicle when doing so, with blocking, whether intentional or not, resulting in consequences. 3.4 - 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.5 - 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 - When the race starts, a warm-up lap will commence. Please adhere to the on screen instructions until the race begins. 4.1.2 - The Race will begin when the game announces the start under ROLLING conditions. 4.1.3 - 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 announced via TeamSpeak to advise others of the danger. A code 80 may also be enforced (see 7.3 for full details) 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.3 - Drivers who sit in the server spectating during the race will be kicked, and may find themselves unable to rejoin to help finish the event.

5.0 - Driver Stints + Pit Stops

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, as well as the mechanics built into the game) 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 - The GAME mechanics, which monitors track limits, will be in effect for each round. So Points 6.1 & 6.2 will only be enforced when an error/exploitation has been identified. 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, their lap time will be invalidated. 6.6 - 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 communicated via Teamspeak, as well as being posted on Discord for our records.

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.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
Code 80 Visual Tutorial - 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 "three" (3), 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 hosted by CFS.
7.5.2 - When out on circuit, all competitors must meet a target race pace of 104% from the leader in class.
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 drivers must be in the "Briefing Room" channel on Teamspeak (details can be found on discord) 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 - Should a driver fail to attend the briefing, they will not be allowed to participate in the event.

9.0 - Results

9.1 - All results will be posted on our website under "Results"
9.2 - Championship standings will be posted under "Results" under this website.
93 - Any post-race penalties, will be placed on the results and the standings affected accordingly.

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 disocrd & Teamspeak 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 can be reported post race, however Race control will monitor as many accidents as possible as the event unfolds. 8.7 - Penalties can NOT be served as part of a normal pit stop or when UNDER CODE 80 conditions. 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