Revision 2, last updated December 8th 2011
If a team is interested in participating in the event, a team manager or representative should make a registration post in the registrations thread, following the directions in the original post.
All teams who register will have a chance to compete. If there are more than 32 registered teams, a pre-qualification session will be used to determine the eligible teams. During pre-qualifying, teams will be allowed to drive an unlimited number of laps. The fastest 16 teams in each class will qualify to participate in the race. If required, pre-qualifying will take place from 19:00 UTC on Monday, January 2, 2012 to 19:00 UTC on Thursday, January 5, 2012.
Cars in each class are balanced using intake restriction, added ballast, or a combination of the two as described below:
The GT1 class consists of the GTR class, with the following ballast and intake restrictions: FZR 1% + 15kg. XRR and FXR are unrestricted.
The GT2 class consists of the GTR class, with the following ballast and intake restrictions: FZR 21% + 10kg, XRR 25%, FXR 23%.
See the tracks & cars page for more information.
Teams should maintain their driver rosters in the Registrations thread. If a team has a car in both classes, each car must be maintained with a separate driver roster.
Using drivers not listed on a team’s official application list will result in an immediate disqualification from the given event.
During the event (including qualifying and race sessions), a minimum of 3 drivers and a maximum of 6 drivers may race for a team.
A driver may not drive for two different teams during the event. Any race laps driven by a driver who has already driven for another team during a given race weekend will be invalidated.
The driver who sets a team's fastest lap in pre-qualifying must drive that car in the race.
Changes to a car's driver roster may be made after the start of the race, if approved by the admins. Any such changes will result in a SG penalty when the newly added driver takes over the car. If multiple drivers are added, multiple SG penalties may be assigned. Admins may deny post-start roster changes at their discretion.
No driver may drive more than 45% of a given race. This number is calculated using the number of laps completed by the team in question. Any fractional amount of laps will be rounded up to a full number of laps. The admins will publish a "45% estimate" in each pre-race briefing, to be used as a planning guideline.
Drivers may use any view that includes a rearview mirror. This includes custom cameras. Follow view is strictly prohibited for the sake of safety, as it does not provide a mirror.
- Name format
Driver names must show the driver’s car class, team number, and real name. Classes are distinguished using specific colors for team numbers. GT1 uses blue and GT2 uses red. The name and the dash between the number and name must be white.
Class Name format GT1: 21 – P. Kempermann GT2: 41 – P. Kempermann
Teams may not attend official qualifying or the race without having produced a car skin and posted it on the forum. If a team has a car in each class, the skins should be distinct in appearance from one another.
Skins must be posted in the race skins thread at least 24 hours prior to the start of qualifying. Skins should be posted at 2048x2048 pixel resolution.
A skinning kit will be provided for each car model in each class in advance of the season start. These kits will include layers for distinct class markings, which must be used.
Skins must include the provided number plate with the correct number (placed on left and right sides of the car as well as the hood/bonnet), class markings, the Masters of Endurance series logo and the 24 hours of Aston Grand Prix logo.
The license plate is regarded as part of your skin and must contain your team's tag. If you have a car in both classes you MUST include the class on your plate as well.
Example: spdo GT1
- Race Weekend
The qualifying sessions will be held on Friday, January 6th, 2012, starting at 19:00 UTC.
Shift-s and shift-p are allowed.
Each car may run an unlimited amount of laps during each qualifying session. Driver changes may be made, but any driver who participates in qualifying must be on the team's driver roster for the race.
Only the active driver for each team should be connected, except for the brief overlap when the new driver connects and the old driver leaves the server.
However, each team may have one “spotter” present on the server to provide information to their driver. This spotter’s name should be formatted in a manner consistent with their team’s active driver’s name. The spotter does not have to be on the race or team roster.
When exiting the pits, drivers must respect cars already on-track, and should not exit into their path. While on an outlap or inlap, drivers must respect cars on hotlaps. Blocking another car during qualifying, if protested, may result in a loss of the fastest lap from qualifying.
The race will be of a duration of 24 hours, and will begin at 16:00 UTC on January 7, 2012.
Each team's starting driver must be present in the server within 10 minutes of the scheduled start time. Drivers who fail to meet this deadline will start from the rear of their class's grid.
The race will begin with a rolling start including one formation lap, behind the Safety Car if there are less than 32 starters. Otherwise, the polesitting car in each class will control the pace, which should be kept at 100kph / 60mph.
The GT2 class should remain stationary on the grid after the green light, until directed by the admins to roll off.
- Formation lap
Drivers will remain in single-file, giving ample room to cars around them, until the final sector of the formation lap. Once they have reached the final sector split, each class will assume a double-file formation.
When each class assumes the double file formation, the class polesitter must maintain a steady 60mph / 100kph, +/- 6mph / 10 kph. The polesitter must not deviate from this target speed until the green flag has been displayed, otherwise a DT penalty will be assessed.
The rows in the double-file formation must maintain a proper gap to the row ahead, and should not overlap cars in that row.
Passing is not allowed before the green flag is displayed. Once the green flag has been displayed, passing is allowed, even before the start/finish line.
A car that loses its grid position during the formation lap because of a spin or any other situation, regardless of the cause, cannot regain its grid position. It must start from the back of its class.
Warming tires during the single-file portion of the formation lap is allowed, provided drivers leave enough space to prevent collisions. Tire warming after going to double-file is prohibited.
Each class will be given a separate green flag, which will be displayed via RCM and chat messages.
Driver swaps may be made at any time. However, a driver should only join the server when the car he wants to swap into is within two laps of its pitstop. The driver leaving the car should leave the server immediately after the driver change.
Drivers should give respect to all other cars around them, even those laps down, and especially to those from a different class. Rough driving will not be tolerated.
Any cases of rough driving observed by the admins, or reported as a protest, will be judged by the marshals on duty, and an appropriate penalty will be assessed if necessary.
Blue flags must be respected in a timely manner. A driver under a blue flag SHOULD NOT behave erratically, or in any way that would confuse the lapping car. A driver under a blue flag SHOULD keep to his line and give way when the lapping car presents an overtaking maneuver. Repeated blocking under blue flag may result in a DT penalty.
In order to be classified, a car must complete at least 70% of the laps of its class leader and cross the start/finish line to begin the final lap. If a car begins the final lap but is unable to complete it (due to lack of fuel, beaching, flipping, or loss of connection, etc.), it will be credited with completing the previous lap and awarded finishing points.
After finishing, drivers should continue around the track on a cool-down lap before returning to the pit lane and parking in a garage stall. The podium finishers in each class should report to the start/finish line for a podium photo as instructed by the admins.
Penalties will be given during the race in form of a drive-through (DT), a stop-go (SG) penalty or a lap penalty.
Penalties given during the race must be served within 10 minutes. If not served within this time frame, the next highest penalty will be given.
Driver changes during a SG penalty are not allowed.
Penalties given after the race will come in the form of time penalties. These penalties will be measured for each track to correspond as closely as possible to the actual DT and SG times for the given pitlane. These penalty times will be published before the start of each race.
Incidents involving gross negligence or misbehavior between car classes may result in more severe punishments, including loss of points, loss of laps, or disqualification, at the admins’ discretion.
Repeated violations of the same rule in a given session may result in an increase in severity of the penalty imposed.
- Name format
Failure to properly format one’s name during a qualifying session will result in loss of that session’s fastest lap. Failure to properly format one’s name in a race will result in a drive-through (DT) penalty.
If a driver mistakenly joins the server with an incorrect name, he may disconnect and fix his name to avoid a penalty. Changing the name on-server is treated as chat and will result as a DT.
Each team must post their skin at least 24 hours prior to the qualifying session (19:00 UTC on January 5, 2012). Failure to conform to this rule will result in exclusion from qualifying.
All drivers must use the appropriate skin during each session (excluding pre-qualifying). Use of an inappropriate skin or on-server absence of a skin will result in a loss of fastest session lap in qualifying, or a DT penalty in the race.
Teams may protest on-track incidents in which they feel they have been wronged by another car. An appropriate protest thread will be available in the Masters of Endurance forum, with a format specified for lodging protests.
Teams may not protest incidents in which they are not directly involved.
Protests lodged more than one hour after the end of the stint of the affected driver will not be accepted.
Protests lodged within the last hour of the event will be ruled upon after the race has been completed.
Admins may request a replay of a protested incident, cut to show the lead-up to and aftermath of the incident.
- Server failure
If the server or master server fails, or a significant number of drivers are unable to join the server, or if the admins judge there to be sufficient reason, the race may be stopped.
Positions will be recorded according to the running order on the last completed lap.
The race will be re-started when the situation has been rectified, or the teams have been instructed to move to a designated backup server.
The race will be re-started according to the rules in section 6.2.2, with the exception that cars will remain in single file. Cars will be divided by class, with the GT2 cars starting behind the GT1 cars.
Gaps at the end of the last completed lap before the race stoppage will not be preserved. The completed laps from the first segment of the race will simply be added to the results from the second segment.
- Chat messages
Drivers must not block messages during qualifying and race sessions, as admins may need to direct them regarding an on-track situation. Accidental blocking will not be penalized as long as the driver quickly unblocks. Repeated blocking/unblocking will be treated as chatting.
Chatting is strictly forbidden during qualifying and race sessions.
Chatting includes intentional messages and accidental use of chat binds.
Teams who chat during a qualifying session will lose their fastest lap of the session. Teams who chat during a race session will receive an immediate DT penalty.
Drivers are strongly encouraged to create a driver profile (LFS > Options > Driver) specifically for MoE. This driver profile should have the proper driver name, number plate, and skin set. All chat binds should be deleted. Doing so will help prevent any unintended errors leading to penalties.
Chat penalties may be assessed due to messages sent by drivers who are not currently in the car, and team members who may not even be on the race roster.
The race marshals will announce when chat is allowed following the completion of a qualifying or race session.
- Driving/conduct standards
All cars should keep at least two wheels on the racing surface (here defined as the paved areas not including raised bump strips) at all times. The act of putting more than two wheels off of the racing surface to gain an advantage may be reported, or may be addressed independently by the admins. If the admins deem that an advantage has been gained in the act of leaving the racing surface, the incident will be punished with a DT penalty.
Suspicious disconnections will be investigated and may result in severe penalties ranging from loss of laps to disqualification and probation.
Excessive honking is not allowed, and a DT penalty may be assessed in extreme cases.
Driving counter to the normal flow of the track is not allowed, except in order to safely rejoin the track. Admins will assess a SG penalty for any such incident, and further penalties may be added for gross negligence.
- Chat messages
- All teams must have a representative present at all times on the Masters of Endurance IRC channel: #moe @ gamesurge. A DT penalty may be issued if no representative is present when required by the admins.
- Common sense is to be used regarding the rules. Teams who discover an unforeseen loophole should bring it up prior to the event, so that the event organizers can make a ruling on it.
- Participants in the series are asked to respect the admins' decisions and accept their rulings.
- Team leaders should ensure that all of the members of their team have read and fully understood the rules.