REGULATION

The Organization decides that the Technical and Sporting Regulations must obey the following directives:

1.    General Rules
1.1.    Drivers must have a stable internet connection. This means they must maintain a ping of no more than 150ms (as viewed on the race server). 
1.1.1.    WIFI and GSM/3G/4G connections are known to cause extremely high ping and lag – do not use these types of connections.
1.1.2.    Drivers over 160ms may be asked to abandon driving by being directed to the pits to replace a driver.
1.1.2.1.    If you do not meet the minimum period of driving interval, the car will suffer penalties, being subject to disqualification.
1.2.    drivers must use their full real name on the Assetto Corsa – any driver who fails to do so will not be able to participate in the event until the problem is corrected, at the risk of losing it and being disqualified.
1.2.1.    Drivers must not use special characters in their in-game names to avoid incompatibilities in collecting results and data.
1.3.    Apps, patches and plug-ins are allowed as long as they do not affect the functions of the simulation, create an unfair advantage or affect other drivers and as long as they are authorized by the event organization.
1.4.    Each car can register between 3 to 4 official drivers who will participate driving, to be defined in advance.
1.4.1.    Each team must enter an engineer, who cannot be entered in any other team or car. This engineer is not a driver and should not be driving during a race.
1.4.2.    Each team must register a reserve driver to cover contingencies with main drivers.
1.4.3.    The deadline for changing drivers is 48 hours before the start of the event's official qualifying event, according to the event's schedule. The substitute pilot must, necessarily, have been registered and participated in the selective test.
1.4.4.    A maximum of 2 driver line-up changes will be allowed during the entire course of the event. The change will be communicated in advance to the race direction and is counted each time a driver is added or removed from the official entrance of the team.
1.4.5.    A driver who is not registered for the car will not be able to race unless permission is given by the race organizers.
1.5.    This is an endurance race where each car is shared between several drivers. Each car is required to have registered the participation of all drivers at least once in the race cycle.
1.5.1.    Use of the Assetto Corsa driver switch feature is mandatory – this specifically means that drivers on a team cannot participate using the same computer.
1.5.2.    A single driver must not cover more than the percentage of laps obtained by dividing the total race time (12 hours) by the number of drivers in the car. For teams of 3 drivers 4 hours and for teams of 4 drivers 3 hours, respectively.
1.5.3.    A single driver must not cover less than the percentage of laps obtained by dividing the total race time (12 hours) by the number of drivers in the car divided again by 2, i.e. for teams of 3 drivers 2 hours and for teams of 3 drivers of 4 drivers 1.5 hours (1h30min), respectively.
1.5.4.    The minimum interval of stay on the track driving the car will be obtained by dividing the total time of the race (12 hours) by the number of drivers in the car, divided again by 4, that is, for teams of 3 drivers 1 hour and for teams of 4 drivers 0.75 hours (45min), respectively.
1.5.5.    Once a driver drives a particular car in a race, he cannot drive any other car (in any class) or team during the race.
1.6.    The race starts at 24:00 local time in Curitiba, unless a change is communicated by the team management. Curitiba uses the Official Time of Brazil GMT-3 and currently there is no daylight saving time.
1.6.1.    The race will last 12 hours plus one complete lap after crossing the start/finish line after the 12 hours have been completed.
1.6.2.    Upon completion of the final lap, it will be mandatory to run an additional full lap at a lower speed level than for promotional purposes. On this additional lap, cars must travel no more than 2 cars away from the car in front and no overtaking must be made. After the conclusion of this promotional lap, the cars must open another lap, go to the pits at the end of it and park, without any incident or contact between the cars.
1.6.2.1.    Cars must have enough fuel to arrive at the pits after the event is concluded, under penalty of disqualification, including the laps after the flag until a total stop in the pits.
1.7.    If a team knows that it will not be able to participate in the event, its manager must notify the organization of the event through the team contact section via the group on the event's website.
1.7.1.    If a team misses the presentation time for the race, the entry will be removed and replaced by another team that is in the queue. However, exceptions can be made if the race direction is contacted in advance and penalties may apply.
1.8.    Exceptions to any rule will be posted in a race-specific thread on the event's official website.
1.9.    The organizers reserve the right to change the rules.
1.10.    The organizers reserve the right to change mods.
1.11.    Any content releases such as car updates, track updates are PROPRIETARY content and we are entitled to use them in any way we see fit.
1.12.    Any content release will only be allowed on our servers, do not host our car updates, track updates or any other updates on your own server.
1.12.1.    Any violation of the rule will be punishable by cancellation of the entry and, or, disqualification has proof time or later.

2.    Car identification, livery and carmake
2.1.    Teams will be required to provide an approved livery for their car before being allowed to participate.
2.2.    Profanity, nudity, or anything else that the organization's commissioners deem offensive is not allowed as part of a painting.
2.2.1.    Teams are responsible for the content of their paintings. Names, logos, websites, slogans or other information relating to any real company, organization or association must be used with the consent of their respective owners.
2.3.    The organization will provide templates for car paints and these will include a mandatory nameplate design.
2.3.1.    Teams cannot change the location of the plate.
2.3.2.    Teams are allowed to change the plate font.
2.3.2.1.    Teams can create team numbers, but the base color of the number must be #f5f5f5 so it is visible.
2.3.3.    Class category decals should not be removed.
2.4.    Paintings must be submitted using the virtual drive link provided by the organization.
2.4.1.    Entries must follow the rules as established in the topic of sending paintings (livery) available on the event's website.
2.4.2.    Colors can only be accepted if sent before the deadline indicated in the painting submission (livery) topic.
2.4.3.    New deadlines for delivery of paintings may be offered by the organization's team during the course of the event.
2.5.    Teams must use the Reconnaissance time to walk through all categories and cars to choose a model for the race, until the deadline before the selective test.
2.5.1.    After the start of the selective test, no change of car and class will be allowed.
2.5.2.    The organization can make exceptions only in cases of maximum necessity and only in cases where the execution of the test may be compromised. In this case, the use of the team during the Recognition phase will be used as a basis for information and reference.

3.    General conditions for the use of time on the track and specific to each phase.
3.1.    The organization of the event, aiming to provide the best conditions for the drivers and teams to be properly able to make it a success, will make use of several phases of opening time on the track, they are:
3.1.1.    Recognition, Selective Test, Free Practice, Race Test, Warm-up and the Curitiba 12h Main Event.
3.2.    The teams and each registered driver (starter or reserve) must, necessarily, use the minimum time/laps and respect the maximum time/laps in each session.
3.3.    Ethics, impeccable sporting conduct and total commitment from each team and driver will be required at each stage of the event.
3.4.    During the Reconnaissance, Selective and Free Practice phases, teams must:
3.4.1.    Monitor the session time and avoid leaving the pit if there is not enough time to open and close the laps before returning to the pits, by way of a full lap.
3.4.2.    Teams should practice starting, pitting, changing drivers and pit stops as part of their preparation for the main event.
3.4.3.    Drivers can use the car in front of them to make use of the “vacuum”, in order to prepare for overtaking conditions in a race. However, they must avoid excessive use of this resource, as a way of avoiding contamination of their time and lap results, being subject to denouncement by other teams and analysis by the race direction, subject to penalty.
3.5.    Any and all penalties will be at the discretion of the commissioners.
3.6.    Any and all unsportsmanlike, unethical, irresponsible, inconsequential, ostensible behavior, at any stage of the event, that violates this regulation or even attacks people, is socially and morally dubious or questionable, will be punished with disqualification and banishment from the current event and of futures. 

4.    Drivers' assessment
4.1.    The driver's behavior on the track will be scored according to criteria and parameters defined by the organization and direction of the race. All track time will be logged and each entry on the server and exit to the track of each driver will compute points for evaluation of their performance.
4.2.    The Recognition and Selective Test phases will have special weight for the evaluation of the drivers, so that each pilot and team must use this time on the track in an optimal way, with ethical and responsible conduct, avoiding crashes, spins, cuts and departures from the track, as well as any other penalty imposed by the direction of the race, in order to maximize your score and that of your team.
4.3.    The drivers' scores in the Recognition phase will not be used for qualification in the Selective Test, but will serve as a criterion of choice/decision for contingency cases, such as penalties, absences, need to change class or replace teams, so it must be taken with the utmost seriousness and responsibility by the drivers.
4.4.    The drivers' scores in the Selective Test phase will be used to define the participants of the Main Test (12h Curitiba). The classification of each team will be based on the arithmetic average of the sum of their drivers' points divided by the number of drivers in the team, including the performance of the reserve driver.
4.5.    The score will be defined by the “KissMyRank” tool system that will be automatically configured in the event servers.
4.5.1.    The criteria and system parameters to be used as an evaluation will be published in a topic on the event's website.

5.    Recognition
5.1.    A Recognition session will be used to provide drivers with an opportunity to familiarize themselves with the track and the cars offered for the race.
5.2.    Teams should use this time in a dedicated, responsible, organized and coordinated manner, making sure to test one car at a time for the period of time necessary to gain a good understanding of its dynamic behavior as well as the characteristics of the track.
5.2.1.    Each team must use each chosen car for a minimum of 30 laps for each driver before the exchange takes place. The standard setup offered is the basis of training and should be used as an initial reference for knowledge of the car.
5.2.2.    It is STRONGLY RECOMMENDED that each team dedicates itself, after the initial passage through all models, to only one class and car during the Reconnaissance stage.
5.2.3.    IT IS STRONGLY RECOMMENDED that each team is also eligible for one more car from each class other than its main class.
5.3.    The Reconnaissance will be an in-game session that will take place daily and will be subdivided into time periods that represent daytime and nighttime. Teams must dedicate themselves to both periods with the same zeal and dedication, also in line with clause 4.2.
5.4.    After the Recognition session, the Selective Test will be opened, following the organization's schedule.

6.    Selective Event
6.1.    The Selective Event will be used to qualify the teams and drivers entered based on the scoring criteria defined in clause 4 and, specifically, in clause 4.4.
6.2.    The teams, after the Recognition phase, must, according to the deadlines defined by the organization, define, choose and communicate to the organization, through the group on the event's website, which class and car they wish to register to participate in the race.
6.2.1.    Class and car change at this stage is strictly prohibited, except for reasons of force majeure or exceptions to be communicated to the organization, which may or may not accept the request.
6.3.    Teams must use this time in a dedicated, responsible, organized and coordinated manner, making sure to record as much time on the track and as little lap time as possible in order to maximize their drivers' points.
6.4.    The Selective Test will be an in-game session that will take place daily and will be subdivided into time periods that represent the daytime and nighttime periods. Teams must dedicate themselves to both periods with the same zeal and dedication, also in line with clause 4.2.
6.5.    After the Selective Test phase, teams must wait for the announcement from the organization and race direction in a topic on the event's website about the race result, ranking and qualified teams.

7.    Free Practice
7.1.    The organization of the event will provide 4 Free Practice sessions after the Selective phase so that the teams seek to complement their training stage.
7.1.1.    In this phase the teams must dedicate themselves to the fine tuning of the cars, pit stop training, driver changes, qualification simulation and race simulation.
7.2.    Free practice will take place alternately between day and night periods, offering conditions for drivers and teams to evaluate all light and temperature scenarios, with a view to preparing teams for the qualifying phase and the main event.
7.2.1.    Free training will take place in the intervals of periods that comprise from 6 am to 12 pm and from 4 pm to 10 pm.
7.3.    After the end of the Free Practice phase, the Test Race will be carried out, following the organization's schedule.

8.    Test Race
8.1.    The Test Race serves the purpose of acclimating the drivers and teams to the procedures that will be carried out during the race, starting procedures, timing of drivers' driving intervals and pit stops, in addition to the procedure after the end, as well as contingency tests, such as event interruption.
8.2.    All drivers and teams must participate in the Test Race, including reserve drivers and engineers.
8.3.    The Test Race will have its parameters published by the organization on the event's website.
8.4.    After the end of the Test Race, the Qualification will be opened, following the organization's schedule.

9.    Qualification
9.1.    The Qualification session will take place in two sessions of 30 minutes each.
9.2.    It will be the free choice of the teams in which session they wish to participate, with no limit of participants for each session.
9.2.1.    The choice of session must respect the deadline given by the organization of the event, communicated on the event's web page and the participants of each session will only be announced after the end of registration.
9.2.2.    Once the session is chosen, the team cannot change it anymore.
9.3.    The date and time of the sessions will be announced by the organization on the event's website.
9.3.1.    Every team is required to attend qualifying with at least one registered driver.
9.3.2.    Teams that do not present themselves for qualification may be disqualified and replaced by teams that are on a waiting list.
9.3.3.    If the team presents itself for qualifying but does not set a time, it will start at the end of the grid and, if there is more than one team in the same situation, the organization criteria will be respected following the order of class from fastest to least and time and time of communication. the inability to participate and, if the time is the same, the score of the first driver who presented for qualification will be used as a criterion, with the best ranked ahead.
9.4.    The driver who has set the best time for the team must be the first driver to race the car, regardless of whether he is a starter or reserve.
9.5.    Drivers may not deliberately use any car in front of them to make use of the “vacuum” (slipstream). If they do, the team will forfeit any set qualifying time and their car will start at the back of the grid.
9.6.    drivers may not use ESCAPE at any time while on the track. It means that drivers will be REQUIRED to be in the pits if they use ESC. If any driver uses ESC, qualifying will be tacitly closed for the car.
9.6.1.    Any and all penalties will be at the discretion of the marshals and may vary from track to track.
9.7.    The use of teleportation will only be allowed during the qualifying phase in cases where the car is not able to return to the pits by its own means or where the damage does not allow a safe return without disturbing the other participants.
9.7.1.    The team that damages its car to the point of not being able to take it to the pits by its own means will have its qualification automatically terminated, as repairs will not be accepted for this type of accident.
9.7.1.1.    If the team has recorded a valid lap time, it will use this time to measure its place in qualifying, otherwise it will start at the end of the grid.
9.7.2.    The team is responsible for informing the race direction if it has an accident and is in conditions that hinder the other participants. In this case, the management can authorize the teleportation or declare a red flag, temporarily suspending the session until the situation is resolved.
9.8.    After the qualifying session there will be a warm-up session to finalize the event.

10.    Warm-up
10.1.    The organization will provide a final pre-race acclimatization stage so that the drivers have an experience with the track on the day of the event.
10.2.    The warm-up session will be a single two (02) hour session starting at dusk and ending at night.
10.3.    All starting and reserve drivers are required to record at least fifteen (15) laps during the Warm Up session.
10.3.1.    IT IS STRONGLY RECOMMENDED that each driver record time in the transition moments from day to night and also in the night, so that they are properly acclimated when they are going to take over the cars.
10.4.    At the end of this stage, the Main event, the Curitiba 12h Race, takes place.

11.    Curitiba 12h Race
11.1.    The main event will last twelve (12) non-stop running hours.
11.2.    The start will take place at 24:00 in the official time zone of Brasília (GMT-3) and the arrival, declared by means of the flag, will take place after the completion of an additional lap inserted after the conclusion of the 12:00h of the race and should occur very close to 12:00 same day.
11.3.    Each driver must have the in-game chat option enabled so that management and teams can use it to communicate with drivers on the race server.
11.4.    It is mandatory for drivers to also use our Discord server. Information on how to access it will be available on the event website once the necessary access has been granted.
11.4.1.    Management will use Discord to announce important information to all teams, such as Code 80, race warnings and penalties, and other information.
11.4.2.    While online, all drivers (and their teammates) must be on their respective input and communication channels.
11.4.3.    Each team must, necessarily, always have at least one teammate present in their channel. The teammate can easily contact the race management via a direct message on Discord if there is a problem before or during the race.
11.5.    The race will be preceded by two (02) formation laps. The goal of the formation lap is to get everyone to calm down before the race and also to ensure everyone's frames per second (FPS) are at a safe level, as well as the tire temperature is optimal. If a driver notices any FPS issues during the formation laps, it is recommended that he safely exit to the side of the track and teleport to the pit and line up at the end of the pitlane waiting for the start and the passage of the cars to be able to start his race. .
11.5.1.    drivers are responsible for their actions during formation laps. In the event of any incident involving damage to other drivers, increased penalties will apply.
11.5.2.    All drivers and teams must be properly connected and with their settings properly made up to 30m before the start so that there is time for the final briefing to pass and the start of the start procedures.
11.5.2.1.    The cars will be walking on the track before the start time so that it is possible to perform the two (02) formation laps.
11.5.3.    The direction will use the following procedures for the start:
11.5.3.1.    The start will be stopped, everyone must line up their car in the correct position on the grid. After everyone is stopped, the direction will call the starting lights which will go off between 1 to 7 seconds.
11.5.4.    drivers are expected to maintain a smooth pace during the formation laps, enough to warm up their tires.
11.5.5.    drivers must always be prepared for the accordion effect, especially when approaching sharp turns.
11.5.6.    drivers must not perform burns and skids to warm up their tires. This can cause accidents and not properly heat the tires.
11.5.7.    drivers should not use the “brake test” (accelerate and brake sharply) to warm up the brakes. To heat the brakes efficiently, depress the accelerator and brake pedals, “dragging the brakes”. This generates a lot of heat and is a sure way to maintain a smooth, consistent and predictable speed.
11.5.8.    Drivers who spin, or otherwise exit their starting position during formation laps, must safely blend into traffic or wait for cars to pass before returning to the track, then carefully turn back and follow directions from the direction to resume their position.
11.6.    Starts are subject to extra supervision, and penalties are increased for incidents occurring at the start of the race, according to the defined Orange Zone (see 11.8 below).
11.7.    In the case of an odd number of cars in a class, the following classes must maintain their grid position, even if it means that the class's pole sitter shares a row with another class.
11.7.1.    Drivers who do not accelerate at the start command (turning off the lights) may be penalized, especially if their actions have directly interfered with another competitor and caused accidents.
11.7.2.    Always check your position on the grid independently of the other participants, using references with the track and your position, as cars in front of you can end up leaving the position or starting from the pits and this will not change the starting position of each one.
11.7.2.1.    Alignment failures will be subject to penalties.
11.8.    The downhill east is defined as “Orange Zone” (right, left and right turns immediately after the end of the pit straight). If a driver causes an incident in the Orange Zone, the penalties are doubled.
11.8.1.    drivers who repeatedly cause incidents in the Orange Zone may be subject to additional penalties, including suspension and/or expulsion. This will be determined by the Race Stewards and is not subject to appeal.
11.8.2.    Overtaking is allowed in the Orange Zone, but all cars will be very close together at this point, so extreme care must be taken.
11.9.    As soon as the Race Director announces “CODE-80 in 10 seconds”, the entire track is under the Orange Zone until the green flag is resumed.
11.10.    In very extreme cases and in case of force majeure, if no pit stop has been made for fueling, if necessary, a restart of the test can be carried out through the server, but only due to its malfunction or instability of the environment.
11.10.1.    If there is any other malfunction of the Server after this period, the race may be suspended and the positions, distances and lap times prior to suspension will be considered. The test will subsequently return in the normal way and will respect the single deadline of 12 consecutive hours for its conclusion.
11.10.2.    Restarts will only be granted in the event of a significant server malfunction affecting a minimum of 20% of the starting grid.
11.11.    Watching is not allowed; drivers can only join the server as a spectator 1 to 3 laps or 5 minutes before they make a driver swap with their teammate.
11.11.1.    Only the race director, the broadcast team and people authorized by the Race Stewards can be on the server as spectators. Anyone else watching will receive a penalty, a driving ban and the car may be disqualified from the race.

12.    Overtaking and on-track behavior
12.1.    It is difficult to define concrete overtaking rules in multiclass events due to differences in dynamics and braking between different car classes. In general, the passing driver is responsible and must be aware of the performance limitations of cars of other classes in order to make a safe overtake at a safe time. However, it is the responsibility of both drivers to ensure that a safe overtake is made. Failure to do so may result in a penalty.
12.1.1.    Cars in faster classes are NOT automatically entitled to overtake a car in a slower class. All classes have the right to race on the track, and each class will be involved in their own battles. Faster cars should overtake when it is safe to do so.
12.1.2.    Cars being passed must give way in up to 4 corners after receiving a blue flag, or risk receiving a penalty.
12.1.3.    Generally speaking, the ideal places (in order of preference) for a faster car to pass are on the straights, exiting a curve or entering the braking zone. Overtaking a car mid-turn is dangerous and should be avoided unless the passing car is confident that the other driver is aware of the passing movement.
12.2.    When entering a turn, the passing driver must, at a minimum, align the front wheels with the rear wheels of the passing car before the entry point, in order to be entitled to a car space. At this point, the driver being overtaken is responsible for leaving a car space for the overtake.
12.2.1.    Cutting the front (chopping) – The overtaking of drivers who go back in front of the overtaken car before completely clearing the space may be penalized.
12.2.2.    Sudden braking (brake test) - The overtaking of drivers who return in front of the overtaken car and brake immediately may be penalized.
12.2.3.    Pushing the car while overtaking - Overtaking is not permitted and may be subject to a penalty unless the offending driver returns the placement, even if it happened accidentally. Overtaking is defined as the passing driver pushing the car forward to make it unstable and then overtaking it while the overtaken driver is regaining control.
12.2.4.    Pushing on the straight (Bump-draft) - Not allowed and subject to penalty. Bump-drafting is defined as the driver pushing the car forward to make the 2 cars go faster. This includes all stages of the track and event.
12.3.    Blocking is not allowed for any reason. Blocking is defined as changing the race line in reaction to another driver in an attempt to avoid an overtake. Blocking will be penalized.
12.4.    Changing the running line (stitching) to prevent a following car from overtaking or using the slipstream is considered blocking and is prohibited.
12.5.    If a driver runs on the track, he must immediately apply the brakes to a complete stop (even if still on the track) and keep the brakes on until he can assess the situation (waiting for a clear opening in the track to resume). When the driver doesn't lock the brakes, the car is prone to spin or roll in a much more unpredictable way and cause yet another incident. A driver involved in an incident while turning on the track and not fully locking the brakes will be held liable for that incident.
12.6.    Drivers who are off-track and cars that have run on the track must resume the race safely. This may mean driving forward and/or reversing to a safe area to first turn into the flow, then safely enter the traffic flow away from the racing line.
12.7.    If, for any reason, a car becomes permanently disabled, whether in the pitlane, on the track or in an escape area, the driver must notify the race management and disconnect. A parked car will cause a yellow flag in that area for the remainder of the race.
12.8.    The yellow flags displayed by the Assetto Corsa and should be observed, slowing down appropriately for the situation. drivers who fail to observe the yellow flag and as a result contribute to the escalation of the existing incident or become involved in an additional incident will be penalized. Claiming "I didn't slow down because no one else slowed down" is not an acceptable argument and will not be accepted, as one mistake does not justify the other. Each driver is responsible for his own actions.
12.8.1.    Due to game code limitations, driving cannot automatically penalize drivers for passing a yellow flag zone. If, during race review and/or through a post-race incident report (IRR), the marshals determine that a driver has overtaken another car in a yellow flag area, that driver may be penalized for passing a yellow flag. Observing the “Gentlemen's Rule” (see rule 12.11) is encouraged if a driver completes an overtake while in a yellow flag zone.
12.9.    drivers who demonstrate unpredictable behavior may be subject to penalties. Some common examples of unpredictability include:
12.9.1.    A driver who suddenly changes lanes 'to get out of the way' when faster cars appear in his mirror or when the blue flag appears. The driver must maintain a predictable line and pace until overtaking is initiated by the fastest car, maintaining his current lane throughout the manoeuvre.
12.9.2.    A driver braking early in a turn when car(s) appear around him, in his/her mirror(s), or when the blue flag appears. Often, the fastest car is planning to follow the same lane and has nowhere to go when a driver ahead brakes early or suddenly.
12.9.3.    Not accelerating at a normal racing pace outside of a turn. When in a throttle zone, lifting the throttle is the same as applying the brakes, but without the benefit of brake lights as a warning. The car behind has nowhere to go.
12.10.    Drivers deemed by Race Stewards to have driven excessively aggressively (whether or not causing an incident) may be penalized.
12.11.    If a driver is involved in an incident that he feels he may be responsible for initiating, the offending driver is encouraged to apply the “Gentleman's Rule” (GR). This is the online racing equivalent of saying “my fault, sorry”. It simply means that you stop safely or drive slower than usual until the car you may have harmed overtakes you again.
12.11.1.    drivers that the stewards clearly observe the application of GR after an incident may receive a reduction in the penalty if it is applied. For example, Penalty reduced to Infraction; Infraction reduced to Warning.
12.11.2.    If one driver causes significant damage to the other vehicle, one GR may not be enough and stewards may impose additional penalties as appropriate.
12.11.3.    If a driver violates 20.3.4 and applies the GR and minimum damage, it will be moved to 20.3.5 or even 20.3.3.
12.12.    Drivers must predictably complete a cool-down lap and return to the pits and press 'Escape' to exit the race. Remember that chatting or leaving the server before the last car crosses the finish line, heading to the pits and coming to a complete stop is against policy.
12.13.    It is not acceptable behavior for a driver to collide with other cars or objects on the side of the track after finishing his race. Drivers must proceed to the pits and come to a complete stop. Any driver found in violation and causing an incident with another driver who is still completing his final lap may be subject to penalties including suspension and disqualification.

13.    Flag Rules
13.1.    Blue flags are displayed to warn that an approaching car will place a driver lap and must be allowed to pass. Drivers receiving the flag must help the fastest driver to make a complete and safe overtake within a maximum of 4 corners.
13.1.1.    On certain tracks, a series of turns in short succession may be designated as a turn for blue flag observation purposes only; this will be at the discretion of the commissioners.
13.1.2.    If a blue flag driver manages to get out of the blue flag condition, he may continue without giving up track placement. However, if the blue flag condition occurs again, it must yield within 4 turns.
13.1.3.    drivers who are getting laps should keep their race line current and predictable. Any incidents that occur due to the unexpected change of your line will be penalized.
13.1.4.    If drivers have not yet entered a turn, when possible it makes sense for the driver receiving the blue flag to take the outside line.
13.2.    While the yellow flag is displayed, drivers can only overtake other cars if those vehicles are moving too slowly, damaged or stopped.
13.2.1.    drivers must be cautious under yellow flags. Be prepared for slow, damaged or stalled cars on the track. Bear in mind that screens and monitors are 2D surfaces and that depth and approach perception is compromised, favoring caution.
13.2.2.    drivers are not allowed to create a yellow flag zone by remaining stationary on the track or creating a dangerous environment for other drivers.
13.3.    Red flags will only be used in rare emergencies and will immediately stop any session where they occur.
13.3.1.    Red flags will only be triggered in case of significant server failure and no chance of server recovery.
13.3.2.    In exceptional cases a red flag may be declared for a car stopped on the track with damage that prevents it from returning to the pits, but only if the situation means damage to the normal conditions of the session.
13.3.3.    Teams may change drivers during the red flag situation, but must restart from the pitlane.
13.4.    The red flag will be triggered by a server crash or crash in a race situation, considering the race is not restarted.
13.4.1.    If the server crashes or crashes before the first refueling pit stop, the event will restart with a new start, but elapsed time will be lost. There will be no cumulative effect on times and laps. The closing time will not change.
13.4.2.    If the server crashes or crashes after the first refueling pit stop, the positions and timing disadvantages of the last lap before the server stop will be considered. The environment will be reset, cars realigned to positions and handicap times added at the end of the event, following the criteria in clause 13.5.
13.4.3.    If the server presents new instabilities, the criterion of clause 13.4.2 will be followed and the disadvantage times will be accumulated and recalculated.
13.5.    The red flag will be triggered by a server crash or crash in a race situation, considering the race restart.
13.5.1.    Server log, replay or other sources will be used to determine the odds and ends positions at the end of the last completed round. Cars will line up for the restart based on that order and times will be noted for recalculation of differences.
13.5.2.    To be able to rejoin the race after a red flag period, your car must not have been DNF rated prior to the server crash/reset point.
13.5.3.    Race restarts after a red flag/server crash are at the discretion of the race direction; factors to consider are the amount of time remaining, time in the real world, and other factors considered important.
13.5.3.1.    The race direction is allowed to close the event if it is found that there are no conditions for it to be held in a stable and adequate way.

14.    Use of Headlights and Horns
14.1.    drivers may flash their headlights – but it must be appropriate. Flashing is not necessary and should not be overused.
14.1.1.    A flash sequence must not last longer than 2 seconds and cannot include more than 4 flashes.
14.1.2.    If the drivers are inadequate with the headlights, the commissioners can penalize these drivers, who go to the suspension of the race, harming the team.
14.2.    The use of the horn is not permitted during any event session.

15.    Pit Entry and Exit 
15.1.    Drivers must exit and enter the pits at a safe speed relative to other cars in or near the pits.
15.2.    drivers entering and exiting the pits must not touch the separation lines.
15.3.    Racers on the track are not allowed to use the pit intersection line with the track as part of the official racing surface.
15.4.    drivers must remain in the pitlane rolling lane until they approach the pit stall. drivers are expected to safely leave the pit lane rolling lane to enter their pit.
15.5.    Drivers should carefully re-enter the pitlane taxiway after exiting their pits and only when it is safe to do so.
15.6.    Drivers are not allowed to pass between cars in pits and garages.
15.6.1.    The only situation that a driver can pass between a car and the garages is when the track requires double rowing of the pits and its pit is inside, between the outside pits and the garages and only if there is an option not to leave the car. The driver must safely return to the pit lane rolling lane.
15.7.    Pit lane drivers must respect pit lane speed limits at all times in all sessions (Reconnaissance, Trials, Practice, Test Race, Qualifying, Warm-up and Race) of the event and whenever they are logged into the server.
15.8.    drivers who cause contact or drive unsafely will be subject to penalties.

16.    Chat
16.1.    Drivers cannot use in-car text chat during qualifying or race sessions for any reason, including “Sorry”, “Pit in” and “Pit out”.
16.1.1.    Race management will notify drivers when they can resume chat functions after Qualifying and after the Race.
16.2.    The proof direction will use ALL CAPS to make posts that must be read. drivers are expected to read these and are subject to any penalties associated with failing to follow any instructions given. I have not seen will not be accepted as an argument.
16.3.    Drivers must refrain from posting chat messages while race management is conducting the pre-race briefing.
16.4.    Drivers can use in-car text chat during the Recon, Selective, Free Practice, Test Race, Warm-up, Post-Qualifying and Post-Race phases.

17.    Track surface and boundaries
17.1.    drivers must keep a minimum of 2 wheels within solid white lines on the race track at all times.
17.2.    We use the in-game hack detection system; warnings will be given when lane boundaries are abused and subsequently penalties will apply. If/when there are exceptions to this, they will be posted in the specific race announcement thread.
17.3.    Drivers are allowed to put more than 2 wheels off the track to avoid an accident or avoid another car. drivers cannot go out to improve their lap time. If drivers receive a warning or penalty for the game, this will not be removed.
17.4.    During Trials and Qualifying, drivers must ensure that they do not take more than 2 wheels off the track on their fastest lap. Otherwise, the fast lap will be invalidated and, in the case of qualifying, the team will have to start from the back of the grid.

18.    driver Responsibility
18.1.    drivers are responsible for following all rules specified in this regulation.
18.2.    Drivers are expected to review all topics in the race regulations and any pertinent rule revisions must be brought in with sufficient time for their review by the race direction. Requests for review the day before or during the sessions will not be accepted.
18.3.    Cheating in any form will not be tolerated in any way.
18.3.1.    Failure to report a bug/glitch/game issue that gives you an unfair advantage may result in disqualification.
18.4.    drivers are expected to participate in an ethical and sporting manner. Teasing, badmouthing, whining and berating other drivers is not tolerated and can lead to immediate expulsion. The 12:00h Curitiba is a high level competition where mutual respect and a positive atmosphere are demanded among all the drivers, team engineer and event staff.
18.4.1.    The above rule applies during any session on a 12h Curitiba Assetto Corsa server, as well as on the event's website, whatsapp groups, social network profiles and includes the chat and Discord channel.
18.5.    Pre-Race Preparation: We expect all drivers to prepare in advance for the race. If the driver participating in the event demonstrates that he is clearly unprepared, the stewards can ask him not to participate. Stewards can use the record of superior lap times to check drivers' practice times. The race direction may choose to place a minimum lap time and/or maximum cuts or crashes for drivers to achieve in the warm-up session as a condition for drivers to participate in the race. This is intended to ensure that a driver who has participated in tryouts or free practice and qualifying in small numbers is effectively fit and aims to ensure that drivers are adequately prepared for the event and that they are not a danger to all teams and drivers who have dedicated significant time in preparation for the race.
18.5.1.    ALL DRIVERS preparing for the event must complete at least 70 individual online practice laps in the class and car they wish to participate in, as well as in the other cars and classes they wish to participate as a second option in case they do not qualify for the event. main event or to meet some contingency of the event, such as, for example, replacing a team.
18.5.2.    It is the driver's obligation to make sure that his laps are being recorded in the Server's STracker and KissMyRank system, for that he must access the online time consultation environment (live-timing) provided by the organization.
18.5.3.    The fastest lap must be within 103% of the class average time.
18.6.    Curitiba 12:00 pm is an event held in Curitiba, Paraná, Brazil, therefore, all times mentioned refer to Brasília Official Time – GMT-3, there is currently no daylight saving time.

19.    Reward
19.1.    The event has a commemorative and celebratory character. Finishing places will be recognized as in any official event.
19.2.    Each class will score participation points, in the following format from first to twentieth: 30-25-21-18-16-15-14-13-12-11-10-9-8-7-6-5-4-3 -2-1.
19.3.    The event's score will serve as selection criteria for future events, so it is expected that drivers will take the race in the most serious, ethical and responsible way possible, as their data will be recorded for future use.
19.4.    The car must travel at least 50% of the distance of the class-winning car course to be eligible for points in the event.
19.5.    The car must start the race in order to get participation points.
19.6.    Drivers must use their real name as submitted by the engineer, it's up to drivers and engineers to make sure their in-game names are correct.
19.6.1.    If there is an error in the entry/transmission list, the team leader must notify the organization of this error by posting the line up change information in the appropriate area of the event website.
19.6.2.    If the mistake is made by the organization, this edit will not count towards 1.4.3.
19.7.    Depending on the fundraising by the organization, it is possible to supply trophies or trophies and prizes in kind.

20.    Penalty Levels and Overview
20.1.    Penalties can be collected in-race by the live marshals, in-race via the game's automated “court lane” system, or post-race in the incident review.
20.1.1.    Penalties received through a post-race incident review will apply prior to the official declaration of the result and the awarding of prizes, if any.
20.1.2.    These penalties will be applied to the scoring and reward system and will be used as criteria for evaluating the driver and team in future events.
20.2.    These are the different types of incidents that can be penalized:
20.2.1.    Aggressive Driving (AD) – determined when the driver is driving excessively aggressively.
20.2.2.    Avoidable Contact (AC) – assessed when a driver makes contact with another driver in a way that is considered avoidable.
20.2.3.    Blocking (BL) – evaluated when drivers change their race line in relation to another driver in an attempt to avoid an overtake or reduce the drafting effect.
20.2.4.    Chat (CH) – evaluated when a driver 'chats' during a “No Chat” session.
20.2.5.    Failure to apply brakes (FLB) – assessed when a driver is involved in an incident and has failed to fully lock the brakes, moving unpredictably on the track or after stopping.
20.2.6.    Ignore Blue Flag (IBF) – assessed when a driver who has completed one lap does not yield to a faster driver after 4 turns.
20.2.7.    Ignore Yellow Flag (IYF) – assessed when a driver does not decelerate properly for a Yellow Flag zone.
20.2.8.    Passing Under Yellow Flag (PUY) – evaluated when a driver completes an overtake when the yellow flag is displayed or is active at the lane position relative to the driver.
20.2.9.    Pit Lane Violation (PLV) – assessed when a driver exceeds the pit lane speed limit, enters or exits the pit lane without safety, enters a closed lane or violates the pit lane separation line.
20.2.10.    Track Cut (TC) – assessed when a driver takes more than 2 wheels off the track, except when involved in an accident, significant error or accident avoidance or other time or position benefits.
20.2.11.    Unsafe Return (UR) – evaluated when a driver does not resume the race safely.
20.2.12.    Unpredictable (UP) – assessed when a driver has demonstrated unpredictable behavior.
20.2.13.    Unsportsmanlike (USA) – evaluated when a driver behaves in a manner considered unsportsmanlike by the 12:00 Curitiba stewards.
20.2.14.    If a driver breaks any rule in section 3.6, driver and team are subject to penalties at the discretion of the stewards, ranging from parole to a black flag and disqualification of the car.
20.3.    Typical incidents will be divided into 5 classes:
20.3.1.    Race incident – typical racing incident, no penalty involved.
20.3.2.    Warning – the driver needs to be warned of an action that caused problems but does not warrant a penalty.
20.3.3.    Infractions – the driver violated a rule and caused a problem on the track, but not enough for a full penalty. (2 infractions = 1 penalty)
20.3.4.    Penalty – the driver has broken a rule and/or caused a problem on the track resulting in a significant loss of time/lost position for another competitor. The penalty is: Pit lane drive-through.
20.3.5.    Penalty – the driver broke a rule and/or caused a problem on the track resulting in significant damage. The penalty is: Pit box stop/hold – 60 seconds.
20.3.6.    If a driver receives two avoidable contact penalties two (02) consecutive times, he will be counted as an infraction.
20.4.    If a driver re-offends the avoidable contact penalty, enforcement after the infraction is converted into a penalty advances to the next major penalty. After the provision in 20.3.5 and if it repeats, it will receive a black flag and disqualification of the car.
20.5.    Lane shortcut (automatically decided by the game): The penalties applied are as follows:
20.5.1.    First, second, third and fourth infractions – warning.
20.5.2.    Fifth and following infractions – Pit lane drive-through.
20.5.3.    If the game considers the cut too excessive, it will override the warning and the penalty imposed will automatically be a Stop-and-Go.
20.6.    Blue Flag Violation Penalty is: Drive-through in Pit Lane.
20.7.    Yellow Flag Violation Penalty is: Drive-through in Pit Lane.
20.8.    Blocking penalty is: Drive-through in Pit Lane.
20.9.    Violation of Pit Lane Penalty is: Pit lane drive-through.
20.10.    Chatting during Qualification or Race (see Section 16): Pit lane drive-through.
20.11.    Qualifying hotlaps can be reviewed for the same penalty scenarios with the same penalty being applied.
20.12.    Parole: Any driver with a history of overt, careless or aggressive driving may be placed on parole by the flight attendants (official notice will be given). A driver on parole may be suspended if another penalty occurs while on parole. If a driver is back on probation and has another penalty, the driver could be suspended for the remainder of the event, harming his team.
20.13.    If a team uses an unregistered driver and does not obtain prior authorization from the race director, that team will be disqualified.

21.    Full Course Caution – CODE-80
21.1.    Instead of a traditional full-course yellow, Curitiba 12pm will use a “CODE-80” procedure to slow down the track environment and neutralize the course if unsafe conditions, such as a damaged car, warrant such action.
21.2.    The procedure begins when the CRO announces “CODE-80 IN 10 SECONDS (NO PASSING)” on Discord or CHAT. Immediately, no overtaking is allowed, regardless of the speed of cars around you.
21.2.1.    It is allowed to overtake the damaged or stopped car(s) on the track.
21.3.    Once the countdown starts, each driver is responsible for finding a clear space on the track to start gradually decelerating so as not to cause incidents with cars ahead or behind.
21.4.    At the end of the ten seconds, the Race Director will announce “CODE-80 – APPLIED”. The cars must have already decelerated and reduced their speed to less than 80 km/h (49.7 mph) and activated the pit speed limiter. No overtaking is allowed, regardless of the speed of cars around you.
21.4.1.    It is allowed to overtake damaged or stopped car(s) on the track.
21.4.2.    Cars must travel in a single file without overlapping. It is the responsibility of the driver behind to give in and follow the line. Non-compliance is subject to penalties.
21.4.3.    Teams that gain an advantage by not actively slowing down immediately after a Code-80 is announced are subject to severe penalties, such as double penalty enforcement.
21.5.    The pits will remain open throughout the CODE-80 procedure.
21.5.1.    Cars in the pit lane travel at the same speed as cars on the track, therefore cars re-entering the track from the pit lane MUST yield to cars already on the track and find a place to queue. Causing a driver on the track to yield to you is subject to a penalty.
21.5.2.    Cars returning from the pitlane should only enter traffic when there is a clear gap of more than one car length.
21.6.    Any driver who exceeds pit lane speed at any point during the CODE-80 procedure is subject to penalties of up to 60 seconds, including a Stop and Go, to ensure that neither team gains an advantage.
21.7.    The stewards will review the sector times after the race to ensure that no car goes faster than the maximum time determined by the average pit lane speed of the track.
21.8.    The exit from a CODE-80 situation will begin with the CRO announcing “10 SECONDS TO GREEN FLAG”. At the end of the countdown, he will announce “GREEN FLAG”. At this point, cars can accelerate and resume overtaking.
21.9.    At the restart, the passing driver is responsible for completing the passage safely, even if the car in front does not accelerate. Accidents that occur at the end of the CODE-80 security periods are subject to review and penalty.
21.10.    The CRO may also announce “CAUTION SECTOR (1, 2 or 3) – SLOW OR DAMAGED CAR OFF PACE“.
21.11.    drivers cannot serve any penalties during the CODE-80 period.

22.    Race Commissioners
22.1.    Curitiba 12:00 pm established a non-biased system called the Curitiba 12:00 pm Test Commissioners Committee. This committee reviews every conduct during the event looking for aggressive, overt driving and drivers who do not comply with Curitiba 12 noon rules and regulations. This committee is responsible for reviewing incidents and determining the driver(s) at fault and will apply penalties accordingly.
22.2.    Stewards may be present at races, but not all incidents will be captured even if there is a live stream.
22.3.    The commissioners will be on Discord. If a violation is taking place, you can contact live proof management by logging into the team channel. You will need to tell management your name, team and car to ask them to join you on a specific channel to discuss the matter further.
22.3.1.    Live stewards may not be available during certain periods as they may be volunteers who are also participating in the race. In this case, ask the management how to proceed.
22.4.    Race Stewards will automatically review the Orange Zone (specified prior to the race) and any potential areas that drivers may cut out on the track.
22.5.    Stewards will not review an entire race. If a driver wants an incident to be reviewed, they must submit an Incident Review Request (IRR). The IRR form can be found on the 12h Curitiba website, searching for the form: Incident Request.
22.5.1.    Drivers should carefully review the official race server replay before submitting an IRR.
22.5.2.    Drivers must submit the following information: server replay time of the incident, cars and drivers involved and a brief description of the event, as well as of course their own identification as drivers, cars and teams.
22.5.3.    Drivers who abuse the IIR process may be subject to penalties.
22.5.4.    The driver submitting the IIR must be part of a team involved in the incident being reported. Failure to comply with these instructions will result in the stewards removing the right of that specific driver and/or that team to submit any IRR for a given time.
22.6.    The deadline for sending the IIR is as follows:
22.6.1.    Up to one (01) hour after the incident.
22.6.2.    No later than thirty (30) minutes after the end of the test.
22.7.    A table with any associated penalty(s) will be posted and the team(s) involved will be notified of the penalty(s).
22.7.1.    All penalties will be fulfilled during the race, or applied at the end before the official announcement of the result of the event.
22.8.    All decisions made by the stewards are final. drivers can notify the organization if a decision violates one of Curitiba's 12 noon rules.
22.8.1.    Appeals made to the organization must be made no later than ten (10) minutes after the decision of the commissioners.
22.8.2.    The decision of the organization will be given during the test or after the end, before the announcement of the final result.
22.8.3.    The decision of the organization is final and unappealable.