The purpose of this guide is to help you understand the procedures and flow of the World Championship. Please read each section completely to ensure that you have a good understanding of what is expected of you and how to properly participate.

F1RST3 League Administrators and the F1RST3 Marshals assume full authority over the rulings and decisions regarding this Championship. League Administrator decisions are final without recourse. League Administrators will always consult this championship guide as reference.

F1RST3 Administration and F1RST3 Marshals take no responsibility for any ability or lack thereof to spectate a race that is scheduled after Friday Evening. If your race was scheduled past Friday evening, and you are approaching the Administrator/Marshals on Saturday or Sunday, you may find yourself without recourse. The Administrators and Marshals reserve the right refuse to spectate any race held on the race weekend.

Please review and familiarize yourselves with the following guide and rules to avoid any disputes that may arise from not understanding proper protocol and procedure. We ask that you use common sense, and treat others as you would expect to be treated.

All Marshals can be identified trough the F1RST3 Contacts Webpage (http://www.f1rst3.com/guides/contacts.php). They’re duties include, helping drivers understand their rules, ensure that all drivers follow proper protocol and procedure, and to resolve disputes before they occur, or provide advice on proper steps to be taken in matters of procedure.

1. The final text of these Sporting Regulations shall be the English version which will be used should any dispute arise as to their interpretation. Headings in this document are for ease of reference only and do not form part of these Sporting Regulations.

2.1 To participate in the F1RST3 World Championship, all participants must be properly registered at this community through the F1RST3 Client software. For administrative identification purposes, an identical nickname in your F1RST3 registration profile as well in your in-game profile is required.

2.2 We strongly suggest you input proper information in your registration details to ensure proper placement in the Championship. Placing improper details will only make participation more difficult for the participant in the long term.

2.3 Competitors must make sure they have a valid email address showing in their profile. This is used for Championship correspondence and notifications.

Disclaimer: We do not share your email address with any 3rd parties whatsoever, and do everything in our power to ensure that it is not available to spam-bots. We do not send you unsolicited emails or otherwise attempt to contact you unless you have specified that we do so, or that it directly concerns your participation and organization in the World Championship.

2.4 The F1RST3 World Championship is split into 2 player skill levels, Amateur (AMA) and Expert (EXP). Each skill level allows and/or restricts certain in-game aids. The aids that you are allowed to use are dependant upon these Level Restrictions.

2.5 Each skill level is designed to place participant’s skills against each other to ensure a pleasurable experience. For this reason, choosing the appropriate level that matches your ability is extremely important in your enjoyment level, as well as others. We suggest that each participant wishing to enter the F1RST3 Championship reviews the aids allowed, and pick their level wisely based on realistic ability levels.

2.6 The following table outlines the available Aids Settings in the Game:

2.7 Participants can change level freely before the 3rd round of a championship. 2.7 After 3rd round a switch is only allowed ONCE. So no switching back! IF allowed at all by League Admin.

2.8 If users change levels, these level changes will only be in effect for the next qualifying session. Changing levels after you qualify for a race (and before you run that race) will not place you in that desired level until the next open qualifying session for the next track.

2.9 Changes to your level can be performed in the F1RST3 Client Profile.

2.10 Users are only allowed to compete in one level per league. For instance you cannot race both AMA and EXP in the same league and using different user-names to do so is also prohibited. Only one username entry is allowed per person. Players found using 2 or more usernames will be penalized 20 points for Unsportsmanlike Conduct and stripped of all overlapping points for all past/present races where the two usernames have submitted a time.

2.11 Anyone caught impersonating another driver, using another drivers log-in to compete in a league will be severely dealt with.

2.12 Your level can be set in your F1RST3 Client Profile.

2.13 The Championship splits the world into 3 time zone blocks. The Time Zone Block you belong to depends on your geographic location specified during registration.

2.14 We split everyone into time zone blocks for 2 reasons:

• To ensure that the other users you are competing against are close in geographic location. This promotes better connection speeds and stability

• To ensure that all participants are given an opportunity to compete at a reasonable time of day. This promotes better organization of dates/times.

2.15 The Time Zone Block is automatically assigned based on the Country Flag in your Client Profile.

2.16 For the above reasons stated, it is extremely important that you specify your Current Geographic Location as opposed to your Nationality in your Country field of your Client profile. Placing an incorrect country will only make it more difficult on yourself and others when it comes time to compete and organize.

2.17 By changing the country field in your user profile, you will change time zones. It is not advised that you change time zones unless it is absolutely necessary. Those who participate outside of their geographic location forfeit all claims to a vote on organization of Heats/Groups, and must rely on the undirected consideration of the geographic time zone participants for organization.

2.18 To edit your profile to change countries/time zones, simply change the country flag in the F1RST3 Client Profile.

2.19 Users may select to use whatever car they choose to race with. Your selection in your profile will govern which car you are required to use in your qualifying and race.

2.20 Failure to use the car currently selected in your profile, will render your submissions invalid.

2.21 You may change car selection at anytime, and as many times as you like during the course of the Championship.

3.1 If a participant wishes to join an existing team, they will need to get in contact with the manager of that team. You may use e-mail and/or F1RST3 forums for this. Upon agreement of the team manager he will add you to that team.

3.2 Before you do a request to join a team please make sure your status is "independent", meaning that you are not related to any other team. Your new team manager can not add you to his team if you still are related to your old team Also keep in mind that all points you gained during championship races will remain to the old team.

3.3 The first consideration in creating a new team is to ensure that your desired Team Name is not already registered by someone else. The registration process will inform you if you have attempted to create a team that is already registered. Make sure your team registration information is correct, as you wont be able to change it in the future!

3.4 After you registered a new team you will be automatically assigned as the Manager for that Team. From there you can add / remove drivers to your team.

4.1 F1RST3 does not support ANY non-retail game versions in part or in whole. Users are required to own and operate the Retail Version of the Game as found on the CD and/or Official Patches.

4.2 F1RST3 will not troubleshoot or otherwise support Warez, No-CD, or any other Version of the Game in any way. F1RST3 does not guarantee results of any files/mod's uploaded to this community. If in doubt, do not install it.

4.3 F1RST3 assumes no responsibility for the maintenance of your computer and/or its peripherals. You are solely responsible for ensuring a healthy computing environment. Computer failure and/or peripheral failure is not considered a valid excuse for missing a Championship Session that you qualified for, or a reason to rerun your Championship Session.

4.4 If your computer/peripheral fails, you will be end as DNF [Did Not Finish].

5.1 The F1RST3 World Championship is performed 100% online. It is required that you actively maintain an Internet Connection. The quicker and more stable the connection; the more fun you will have. If you intend to take this Championship as serious, then we suggest your Internet Connection reflect this level of dedication and perceived importance on your life. Please keep in mind that your upload speed is the most important factor in online gaming. Do not blame us for poor Internet Connections and its affect on the F1RST3 Software or the game's playability online, we have no control over that.

5.2 All Championship activities are performed using the F1RST3 Client software. Users are required to download the F1RST3 Client software from the F1RST3 software download section. Users must then install the F1RST3 Software and then perform their Championship Sessions online through the F1RST3 Client Software. Any attempts to tamper with the F1RST3 Software package in anyway will result in your immediate removal from the Championship and/or the F1RST3 Network. Reporting tools are built into the software to prevent tampering, with multiple delivery methods employed. We highly suggest not testing our resolve or security in this regard.

5.3 The F1RST3 World Championship Driver's title will be awarded to the driver who has scored the highest number of points in each skill level, taking into consideration all the results obtained during the Events which have actually taken place.

5.4 The title of F1RST3 World Champion Team will be awarded to the Championship Team which has scored the highest number of points, results from all cars being taken into account.

6.1 Each driver is allocated points for their worldwide finish position. Each driver will race in Heats with other drivers from the same geographic time zone block, level, and similar pace. The race will be timed, and the finish time will be submitted to be compared against other drivers from the same level around the world in other time zone blocks. Your finish position, and points allocated, are governed by the comparison against the rest in the world in the same level.

6.2 To get your result in the rankings, you must at least have completed 75% of the race distance. If you fail to do so and your result uploads, it will be changed to DNF by the League Admin(s). In the future this '75% rule' will be automated in the client.

6.3 The higher levels have more points and finish positions available to them by virtue of a more competitive and difficult accomplishment. The points available slowly decline as you move down levels. This is done to ensure that Expert Drivers score the maximum amount of points for their teams and country, and Amateurs division is given a proper representation.

6.4 Drivers in different levels are never compared to each other for the purpose(s) of the Individual Driver's Championship(s). Each level has its own separate Drivers Championship. The only time drivers from different levels are factored together is in Team and Nation standings/scoring, where applicable.

6.5 Points for both titles will be awarded at each Event according to the following scale...

6.6 After the last round of a given championship trophies will be awarded in the format of Gold, Silver and Bronze cups for 1st, 2nd and 3rd places in both Amateur and Expert leagues. These will then appear next to a drivers name within the client until the next season of that particular league is complete, when the cup will be transferred to the new top 3.

6.7 For any Expert or Amateur league to have "Championship Status" (i.e. trophies or client cups awarded), 10 people must compete in at least 50% of RACES. For Championships that have an odd number of rounds, the number will be rounded up. If this happens, all 3 cups will be awarded in that class.

6.8 If not then the top 3 will be noted as winners of the league but cups will not be presented due to the lack of competition.

6.9 The F1RST3 Team Championship is based on the top 5 scorers from a Team overall. For instance if a team has 3 drivers in AMA and 4 in EXP then only the 5 drivers with the most points in total, not per race (no matter which class) can contribute to their team points.

6.10 Points are assigned upon achievement and remain the points of the person and the Team as they were originally assigned. Upon the resignation/termination of a Driver from a Team, the Team will retain all Team Championship Points achieved by that driver over the course of membership, and the driver will take only his Individual Driver Championship Points with him.

6.11 The F1RST3 Country Championship is based on the top 5 scores from each country, per race. For instance if a country has 7 drivers in EXP and AMA in total, it’s the top 5 points scorers that contribute to their Nations score.

7.1 Safety cars during practice races are STRICTLY forbidden. The race should be continued at all times, without having to slow down on request of someone else. Drivers who find it necessary to call a "safety car" period in the room chat, obligating other drivers to slow down and be an obstacle for them, will be banned from the practice servers, without further discussion.

7.2 It's not allowed to hit anyone off, nugde other drivers to overtake, slowing down on the race line becoming an obstacle for other drivers or swaying over the track becoming an obstacle for other drivers.

7.3 Respect other drivers who are still in the practice race. Do NOT overflow the chat, annoy drivers who are still racing or call endless votes for race restarts, kicks or bans of drivers!

7.4 You have no right to obligate your own rules or idea's on other drivers. Only the F1RST3 rules apply on the practice servers and all it's drivers.

7.5 At all times we expect fair racing. Anyone who does not respect these rules are banned from the practice server, without further discussion. To get removed from the ban-list, you will have to contact an overall admin and explain what happened including a request to be removed from the ban-list, we will not automatically do this for you! The overall admin will review your request, and if needed discuss with other overall admins, to conclude the final decision on removing you from the ban-list, or keeping you listed on the ban-list.

8.1 Qualifying is how you notify the F1RST3 Championship System that you are participating in the upcoming race.

8.2 However, if you qualify it is a must you race otherwise you will get –10 for DNS (Did Not Start). Should you not be able to race for whatever reason, contact your League Administrator in plenty of time and post in your Heat Organisation Forum. This will let all other competitors know and therefore, they don’t have to wait for you. If you have done the above in time, you will get DNF instead of DNS.

8.3 The F1RST3 software has the ability to check for corner cutting when you are out on the track.

8.4 Corner cutting is determined by DAT files. Those DAT files will render your lap invalid if you try to 'cut' any corner during an official qualifying session. The F1RST3 software will refuse to upload your qualification result if any corner cutting is detected. The DAT files are available for download (http://dats.f1rst3.com), if you feel the need to investigate those files. We strongly recommend to use our DAT-files and test with them before you Qualify, so you know what the DAT accepts.

8.5 Your qualification lap legality solely relies on the accuracy of the Dat files. You do not need to install those DAT files separately; they are integrated in the F1RST3 software. In the case there are no accurate DAT files available for a specific track; your lap legality will be judged by the Marshals and League Admins, based on the current F1RST3 rules.

8.6 The first consideration is to determine the current track open for qualifying, or at least the next track that will be available after a pending race. To do so you need to consult the Championship Schedule. The Schedule will display the current track open for qualifying, and the submission deadline to participate in the Race. You need only make sure you submit an Official Qualifying Time before the deadline passes.

8.7 Deadline Countdowns and Current/Forecasted Weather Information is available in the right column on the Front News Page, and any other Championship Section Page. Note: a correct weather indication is ONLY on the Championship Page for the specific mod!

8.8 You will only be allowed a certain number of Official Qualifying Sessions, depending on the racing category (i.e.: F1, PCC etc). For this reason, we suggest you practice the current track offline, or online in “pick-up” races. This will then ensure that your setup and your pace are equalled to what your setup and pace will be in the race a week later.

8.9 After you are satisfied with your pace and feel that you are ready to qualify for the race, you should then proceed to your Official Qualifying Session. Make sure you submit an Official Qualifying Time before the deadline, or your submission will not be accepted.

8.10 If this qualifying time is to be considered important to you, we advise that you take every opportunity before the qualifying session to reboot your computer, close any unused programs running in the background, calibrate your controllers, or any other preventative precautions you can take to ensure that your equipment will be in perfect running order for the Scored Championship Qualifying Session. Your system stability is entirely your responsibility. F1RST3 and your co-participants take no level of responsibility for this stability and will not allow re-qualifying/etc. in the event that a system crash occurs. System Crashes are treated as an in-game failure and scored accordingly.

8.11 The Create Session Dialog is integrated to the F1RST3 Championship, and will automatically set the correct settings for your race and/or qualifying, in accordance to the real-time happenings of the Championship. Meaning further; you simply select League from the Race Type drop down menu. The Dialog will then gray out all other settings, and preset them with the appropriate settings. All you need to do is select Championship and launch. F1RST3 will do the rest for you automatically, and will preset your game to the appropriate settings.

8.12 The fastest lap is submitted by the game. If that one contains a cut, detected by the DAT-file, the lap will show as 16.39.999 considered invalid. Even when another less fast lap is correct! Always check right after Qualify if your result and VCR are submitted to the rankings-page. If not, immediately mail the League Admin and attach your LOG and VCR from your session.

8.13 After you launched the game, proceed to the session lobby. Then select the appropriate setup for your laps. The game will start in warm up session, switch to race to start the official qualifying session in game. You will get a 3 lap race; 1 outlap, and 2 fast laps! Your outlap may not be the fastest one or the game will not submit it!

8.14 When you are finished your official qualifying session, you simply exit the game and your results will be automatically uploaded to the F1RST3 database, after you leaved the game you will be placed back into the F1RST3 Race room and should see a "submission successfully" text in your room.

8.15 If a drivers vcr is incomplete, whether it be via auto submission or manual submission, the time the driver’s time will be 16.39.999. This will usually be when a driver hits the escape key too soon after the finish line. A way to overcome this is to leave the car do half a lap of the track and then exit.

8.16 If the lap, for any reason, doesn’t submit to the F1RST3 database, users are asked to send their VCR and log/xml file to the League Administrator. They can check it and add it manually to the database. Make sure you have set your firewall correct or better even disable it! Firewalls not set in the correct way, can block the uploading process.

8.17 All track legality checking will be based on automatic comparison with the correct track Dat file.

8.18 Each track has a specified Qualifying deadline when all participants must submit a qualifying time before. After the deadline has passed, the Race Grids are created instantly, and we progress to Race Week organization.

8.19 All participants should visit the community web site to determine their opponents, and to begin organization immediately in our Heat Organisation Forum. The driver from a heat visiting the Forum first, should create a thread in the following way: "Subject: TZA/TZB/TZC (Depending on your time zone) EXP/AMA (depending on your current Championship Level) Heat x (Depending on which heat you have been placed in) with all drivers mentioned in the subject.

8.20 For rFactor Leagues - we don't use DAT-checking. Each driver has to make sure he runs all legal laps, like those described in Chapter 15. For checking reasons, each driver MUST save his original VCR for AT LEAST 48 hours, as that is the time a dispute can be filed within.

8.21 For rFactor Leagues – If a drivers lap is disputed, the driver must:

• Either send his VCR as requested to the Admin of the League

• Or do a Qualify-run under supervision of a Marshal/Admin and the fastest LEGAL lap MUST be within 0.250 seconds of his Qualify time in rankings. If he succeeds, his time will remain. If he fails, he gets 16.39.999 as it is considered as a cut lap.

9.1 The length of each race will be determined by the League Administrator before each season. In the case of the F1RST3 F1 World Championship, Expert races last 100% of the actual race distance and Amateur races last 50% of the actual race distance.

9.2 Race Heats are employed to place competitors of similar ability and geographic proximity against each other. The result is smaller group portioning increasing both connection speed, connection quality, and worthy opponents. Drivers will only be placed in Heats that contain the closest competition found in each level and time zone. At the moment, these are a maximum of 6 in F1 Challenge and 10 in rFactor.

9.3 To determine which Race Heat you have been placed, the competitor will need to consult the Race Heat Listings after the Qualifying Deadline has passed. At the top of the Race Heats Listings is a search box that should be populated with the F1RST3 Username you are currently logged into this community as. Selecting the FIND button will retrieve the position of that username in the listings, and auto-scroll to its location on the screen.

9.4 Once you have determined your Race Heat and the co-participants identified; it is your responsibility to contact those other participants and engage in actively organizing a race date and time that all participants can be available to race together. It is at the organized time that the Championship Race will commence and be scored. This may ONLY be done in our Heat Organisation Forums!

9.5 The participants have 7 full days to organize and run the race with other participants that are in your time zone region. Given the time zone factor, it should not be difficult to organize a time that suits all parties. We suggest you actively pursue the participants and compromise on the start time if you wish to avoid a DNS for lack of appropriate scheduling. We also suggest that you ensure a proper and frequently checked email addresses in your profile to allow other users to contact you. Contesters should react in the Heat Organisation Forum as soon as possible, but at the most within 48 hours of the deadline. If reacting later, they will have to accept the date and timne others already agreed on.

9.6 The Championship Administration requires that all discussions regarding Heat Date/Start Times be conducted in the Heat Organization Forum, at the Topic Thread that you or a co-participant needs to generate for your Heat.

9.7 Users are not permitted to 'Share' a connection to enter a Heat, for the purposes of strict identification of drivers only 1 user per I.P. address is allowed.

9.8 Failure to reply to a heat organization thread within 48hrs of Qualification ending could, at the League Administrators discretion, result in you being completely removed from the Heat and given a DNS. Failure to respond should be reported to the League's Admin/Marshals as soon as possible after 48hrs has expired. Unless otherwise told by the League Admin, the race will take place, when those who have replied to the thread, agree upon.

9.9 In the event you are the sole Heat Member, please contact the League Admin immediately to arrange for alternative accommodation. Please ensure you are able to, start or respond to, a Heat Organization Thread, before you qualify.

9.10 The Heat Members are responsible for ensuring that one Heat Member, at least, can host their Heat. It is in the Heat Members interest to do this as soon as possible before the race.

9.11 In certain cases, drivers who are left alone can apply to evoke the following procedure, in order to prevent the time handicap being added:

9.12 The driver concerned can ask another heat, and their members, to if they can race with them.

9.13 The driver must get the approval of ALL of the heat members. Each driver must post their approval within the Heat Organisation forum.

9.14 The League Administrator concerned, must be notified by email at least 24 hours before the race. This is so they can set the grid. However, all decisions remain with the League Administrator. A hadicap time will be added for racing alone. This is to compensate the advantage of not having to fight other contesters on track. For F1 this is 60 seconds for EXP and 30 for AMA. Each League Administrator can set the specific handicap for his League, at the start of each season.

9.15 The only real requirement after organizing a Race date/time is to show up and allocate a couple hours to actually complete the race. We encourage active pursuits of compromise in regards to start times to ensure that everyone has an opportunity to race, regardless of schedule. For this reason, it is requested that you arrive no less than an hour prior to race time, to perform tests and properly setup your equipment.

9.16 Pre-Race Trials are encouraged before the Championship Race to ensure that Network Conditions are suitable with particular attention paid to the Session Host. Allow each prospective host the opportunity to host a session, selecting the most stable and trouble free connection as the host.

9.17 If this race is to be considered important to you, we advise that you take every opportunity before the race to reboot your computer, close any unused programs running in the background, calibrate your controllers, or any other preventative precautions you can take to ensure that your equipment will be in perfect running order for the Scored Championship Race. Your system stability is entirely your responsibility. F1RST3 and your co-participants take no level of responsibility for this stability and will not allow re-races/etc. in the event that a system crash occurs. System Crashes are treated as an in-game failure and scored accordingly.

9.18 In the event that a participant is not available to race at the allocated time/date. The user will be given a 30 min. grace period to arrive. If the tardy participant(s) do not arrive within the 30 minute grace period, the existing participants will be allowed to continue with the Championship Heat without the absent participant.

9.19 The winner of the heat is responsible for contacting the Championship Administrator informing F1RST3 of any absent participant. Failure for the Heat Winner to contact the Championship Administrator is punishable by Disqualification from the Race with associated penalties.

9.20 Participants who do not arrive and race at the agreed upon time are considered DNS (Did Not Start) and disqualified from participation with a 10 point penalty applied. If you are unsure of your ability to organize and/or participate in an upcoming race, do not qualify for it... simple.

9.21 The host needs to set the grids. In the warm-up session prior to the race, the host will have an extra option available to edit the grid positions.

9.22 If after pre-race testing it is determined that you are the most attractive host for the Championship Race, it is your responsibility to create a formal League Session for the rest to join. Only formal League Sessions will submit valid race times to the Championship System.

9.23 Creating a Championship Session in the F1RST3 Client is very simple. Select the Room Type Tab in the Dialog. Inside that Tab Section, you should select League from the Race Type Field. Once you select that you need only press OK to create the session. All joining restrictions, naming conventions, aids settings, etc. will all be preset for you. Only users who reside in your Race Heat, will be able to join. Once you have created the Session, and everyone who arrived to race has joined, it is time to launch the game.

9.24 Contrary to an apparent, vast majority of opinion; races are NOT traditionally won on the first corner. As a result, it is useless to try to and squeeze everyone through the same corner at exactly the same time. Use your patience and good judgment when entering the first corner to ensure that you will leave enough room for others to manoeuvre. We are not asking you to give up your line per-se, but we expect you to conduct yourselves in a professional manner and with consideration for your fellow drivers at all times.

9.25 If you find yourself in the rare instance of leaving the track due to an error, etc. and you must re-enter the track. We insist that you re-enter the track Off the Racing Line and ask that you remain off the racing line until such time as a proper and competitive pace can be achieved. You MUST give the other drivers the right-of-way until you can hold your line competitively.

9.26 Purposeful blocking, crashing, or any other failure to relinquish the right-of-way under these circumstances will be considered an act of poor sportsmanship and will be penalized accordingly, complete with a suspension of license, removal of all points achieved at that track, and a deduction of additional points dependant on the severity of infraction, as deemed appropriate by the Championship Administrator. We DO NOT tolerate unsportsmanlike driving!

9.27 Upon finishing the race when the list of ALL drivers who have finished is shown, press F12 to save a screenshot of the results in case it is required for validation. All drivers must save a screenshot using this method to ensure that validation can be confirmed by more than 1 party.

9.28 Upon exiting the game, your F1RST3 room will appear displaying your race time and/or status. At this stage all users should save the room log.

9.29 Users are capable of submitting proof of race results with the above screenshot & room log as many times as they wish (in the event of a failed submission). However, a driver will only be given 1 opportunity for the duration of the season to submit an in-game screenshot that is not accompanied by a room log.

9.30 After all screenshots / logs are taken and you discover a failed submission, submit your screenshots to the Championship’s League Administrator within 48 hours of the Race Deadline. Any submission changes sent in after 48 hours past the race deadline will be ignored.

10.1 If in testing prior to the race in the Heat, a driver is found to be lagging (this will be visible and confirmed by other heat members) then the lagging driver is allowed to leave the session but ONLY with the approval of all heat members. The remaining drivers then continue to race the Heat as normal. Then a Split Heat for the lagging driver is allowed. See point 10.2, below, on how to set-up a Split Heat.

10.2 If a driver suffers a problem just before the race, and can't fix it in time, that driver will be allowed a Split-Heat; the remaining drivers then continue to race the Heat as normal. See point 10.1, below, on how to set-up a Split Heat.

10.3 If a driver suffers an equipment failure after the Race has started, he cannot Re-Race.

10.4 If a driver is unable to race because the other Heat Members have started the race without waiting for the 30 minutes grace time following the agreed Heat start time, the driver left behind will be allowed a Split Heat. See point 10.6, below, on how to set-up a Split Heat. The host of this heat, who started the race without waiting, will be punished with a Time Penalty of 60 seconds for EXP class and 30 Seconds for AMA; the other Heat Members will get a warning.

10.5 If you find you are in a Heat with no other drivers, you are not allowed to race alone unless you follow the procedures in Point 10.6

10.6 The driver(s) with the problem should, if possible, contact a Marshal or a League Administrator to allow his heat to be split. A Marshal or League Administrator should then be present during the running of the split heat. If a Marshal or League Administrator cannot physically be present for the running of the split heat, then the driver of that heat is allowed to race alone in a normal (not League) race. As mentioned only after consulting a Marshal or Admin for permission to do so.

10.7 This race will be in the form of a normal Race with the correct settings to match the original race criteria. As such, they can be raced after the deadline has expired, but as soon as possible to allow the League Administrator time to manually submit results.

10.8 A hadicap time will be added for racing alone. This is to compensate the advantage of not having to fight other contesters on track. For F1 this is 60 seconds for EXP and 30 for AMA. Each League Administrator can set the specific handicap for his League, at the start of each season.

10.9 After completing the Heat you have to mail both the LOG and VCR of the race to the League Admin.

10.10 Under no other circumstances will a split heats be allowed.

10.11 If either the host, or another heat member, is disconnected before the actual race has commenced. All drivers including the host are allowed to restart the race.

10.12 If the host disconnects after the race has started, the host will not be allowed to Re-Race, only those heat members who were still running (i.e.: not retired) when the host crashed, will be allowed to Re-Race. If possible, after contacting a Marshal or an Admin. If a Marshal or an Admin are not available, they ARE permitted to race alone in a normal (not league) race with the correct settings to match the original race criteria and the new host should mail the Admin the LOG as well as the VCR, explaining the situation.

11.1 Marshals may at their discretion, and without notice, spectate a race to ensure that fair play and proper race etiquette is maintained. To best prepare for a Marshal spectated race, expect that every race will be spectated. Marshals may at their discretion impose penalties and/or suspensions as they see fit for Unsportsmanlike Behaviour.

11.2 Specific Marshals are not permitted to spectate a race in the event that it involves directly, or indirectly, a Marshal's Team Member or any other reasonably established bias towards a particular heat member, or that may be construed as reasonable for that Marshal to consider a particular outcome of that Heat as advantageous.

12.1 Points are awarded for race positions, and as such this may encourage people to achieve times based on known game faults in corner cutting. As such, any submission may be disputed by another participant of that track.

12.2 (rFactor leagues only) A dispute for the qualifying must be sent within 12 hours after the deadline of the qualification, together with proof (screenshot). Disputes without proof will be ignored! Disputed ones will receive an e-mail about the dispute and must send a good qualify lap (F1RST3 VCR) by mail to both cash@f1rst3.com and tygernoot@f1rst3.com. The new lap must be send before Saturday 23.59 CE(S)T. If the disputed fails to do so, his lap will be put in as 16.39.999 resulting in a random position at the bottom of the rankings.

12.3 Only users of the F1RST3 League participating in the race in question are capable of filing a Dispute against another driver's race conduct, and only if the race deadline has NOT passed more than 48 hours previously and has a valid VCR file from the race. If disputes are filed without proof they will be ignored!

12.4 A driver may dispute qualifying results as many times as he likes, as long as it is a VALID dispute. Should a driver do an INvalid dispute, the dispuTER will get a 30 second penalty the first race he finishes.

12.5 If all criteria is met for a dispute to be filed, the Submitter needs to only contact the Championship Administrator directly via email, outlining the following information:

• Username of the disputed submission,

• Your Username (Submitter),

• Level of the Disputed Submission,

• Track in question,

• Reason for Dispute,

• VCR (Replay) and approximate race time of incident.

12.6 Drivers, who are disputed against and found guilty, will receive a time penalty which will depend upon Administrator/Marshal's decision.

12.7 Driver identities are kept confidential in matters of disputes. The Disputed driver will know only that a dispute was filed, and must take action to overcome the dispute using methods set forth in this section.

12.8 To actively avoid a dispute against your fastest race times, we highly suggest you understand the proper protocol regarding lap legality.

12.9 Dispute filings and notifications are performed through your email listed in your Game Profile. We highly suggest ensuring that the email listed in your profile is accurate, and that you check it often. You alone are responsible for ensuring expedient contact avenues for the Championship Administrators to use.

12.10 Administrators and/or Marshals are not permitted to hand out penalties individually; at least 3 votes of other Marshals and/or Administrators are required to penalize a driver.

12.11 Administrators and/or Marshals are permitted to hand out penalties for ANY reason they seems fit.

12.12 Administrators and/or Marshals will debate their decisions in a closed forum.

12.13 Purposeful blocking, crashing, corner cutting or any other failure to relinquish the right-of-way under these circumstances will be considered an act of poor sportsmanship and will be penalized accordingly, complete with a suspension of license, removal of all points achieved at that track, and a deduction of additional points dependant on the severity of infraction, as deemed appropriate by the Championship Administrator. We DO NOT tolerate unsportsmanlike driving.

13.1 Yellow Flag: Danger-Reduce Speed - Maintain position until the situation, accident etc that caused the yellow flag to be given is passed. Failure to slow to a safe speed for a yellow flag will be considered a serious breach of these rules.

13.2 Blue Flag: One or more competitors are about to lap you. You must hold your course and allow him or her to pass unimpeded.

13.3 Black Flag: Should it become necessary for any reason to stop a driver, the black flag shall be displayed to the driver concerned. Such signal indicates that once a competitor receives the black flag they are to cease racing immediately and return to the pits next time he or she reaches it without impeding another competitor.

13.4 Black and White Chequered: The display of the black and white chequered flag will determine the end of the race. The race finishing order will be as cars crossed the finishing line on the lap when the black and white chequered flag was displayed. This flag shall also signify the end of practice or timed session.

14.1 Car Direction: During an event and/or practice, it is expressly forbidden to a drive at any time in a direction opposite to that in which the event and/or practice is being run. Infringement of this rule means immediate exclusion (DSQ) and possible further penalty.

14.2 Stop On Course: If for any reason a driver is forced to stop his car on or near the course, it will be his duty to place it in such a manner as to cause the least danger or obstruction to other competitors.

14.3 Lapping Competitor: When a driver is preparing to lap another competitor the driver of the car to be overtaken must hold his course and allow the lapping car to pass unimpeded.

14.4 Contact Of Cars:

a. A driver who causes a car to make contact with another car may be penalized.

b. A driver who drives or acts in a manner that could endanger themselves or any other driver may be penalized.

14.5 During a Race:

a. A car alone on the track may use the full width of the track. However, as soon as it is caught up on a straight line by a car which is either temporarily or constantly faster, the driver shall maintain his or her line.

b. Curves, as well as the approaches and exit zones thereof, maybe negotiated by drivers any way they wish within the limits of the track. Overtaking may be done either on the right or left. However, maneuvers liable to hinder other drivers, such as premature direction changers, deliberate crowding of cars towards the inside or outside of the curve or any other abnormal braking or change of direction, are strictly forbidden and shall be penalized according to the importance and repetition of the offence.

c. Racing Room: …..A misconception in racing is: I have the inside so its my corner!!!!!!! .........This is totally wrong. {If the driver on the outside wishes to stay there, the inside driver must give him room and vice versa. Basic racing room.}

14.6 Chatting During a Race: Chatting once a race has commenced is strictly forbidden and can be penalised. At all other times please keep to a minimum.

15.1 For F1 Challenge, All decisions of lap legality in qualifying will be controlled by automatic comparison of a drivers replay with the latest track.dat file. For rFactor laps can be disputed manually by any participant, through sending in a dispute e-mail incl. proof to the league admin.

15.2 For F1 Challenge, If the comparison shows a clean lap, then it will be automatically submitted. If a cut(s) is detected the lap will not be submitted, please note that the number of cuts displayed as detected does not reflect the number of corners cut.

15.3 For F1 Challenge, Disputes will not be accepted in qualification. The DAT file is final. For rFactor laps can be disputed manually by any participant, through sending in a dispute e-mail incl. proof to the league admin.

15.4 For F1 Challenge, The DAT's will be designed to try and fit the examples given below as much as possible, they will be under constant review for improvement but please note that once qualification has begun nothing can be changed till after race completion.

15.5 For F1 Challenge, The Dat's are available for driver inspection.

15.6 The examples below also cover what is considered as legal in race circumstances, in the event of a dispute, those investigating it will manually use the replay for comparison to the track Dat.

15.7 At least 1 whole wheel must always be 100% on the track at all times throughout each corner to be considered valid. If there is less than 1 whole wheel completely on the track pavement (INCLUDING the white line next to the curb) in a corner, the lap is considered illegal!

15.8 On the exit of a corner, drivers are allowed to take the exit of a corner wide, while remaining as a legal lap. Only during the corner exit you may fully attack the curbs and their marked outrun areas as long as the corner exit is not part of the next corner entry. During a wide corner exit, at least 1 whole wheel should be 100% in contact with the curbs.

15.9 Users who choose to bypass corners entirely are considered illegal and will be removed with submission suspensions for Unsportsmanlike Behaviour.

15.10 Rail Riding is not permitted. Contact with the walls will render the lap illegal, and will be subsequently removed upon receiving an official dispute.

15.11 The track is considered the GREY tarmac, including the white lines seperating it from other materials.Track Pavement does not include the track curbs. At least 1 whole wheel on the track pavement at all times during a corner is strictly enforced. You can attack the curbs; just make sure 1 whole wheel is touching the track pavement

15.12 Examples of what is a cut and what is not a cut can be found in Appendix 1