The online racing simulator
S08-09: Rules
1. Participants

Masters of Endurance is a team racing series with two separate car classes. For the 2008-2009 season, the car classes are GT1 and GT2. The GT1 class consists of LFS’s unrestricted GTR class. The GT2 class utilizes the GTR class with intake restrictions as follows: FZR 20%, FXR 24%, and XRR 25%. Team participation is on an invitation-only basis. If a team is interested in racing in MoE, it needs to send an application to (applications 'at' mastersofendurance.eu), after which an invitation may be issued by the organization. An application must include a list of the drivers the team is planning to employ, the racing history of the drivers, the team name, chosen class, and chosen car. Teams that have not previously raced in MoE need to prove their racing experience in order to receive an invitation. The organizers may ask the teams or single drivers for proof of their racing capabilities before issuing an invitation.

Teams can substitute team members. They can freely substitute team members that are on the official application list. When they want to change this list, they should send an email first, in which they announce this change. This email should be sent to (applications 'at' mastersofendurance.eu).


2. Number of drivers for a team during a race weekend

* During a race weekend a minimum of 3 and a maximum of 4 drivers must race for a team. In the 12h and 24h race, a maximum of 6 drivers can race.
* No driver may race on two different cars during a race weekend, even if both cars belong to the same team. Qualifying sessions are part of a race weekend.
* No driver may drive more than 45% of the race. This number is calculated using the number of laps completed by the winning team. Any fractional amount of laps will be rounded up to a full number of laps. Prior to each event, the admins will provide a 45% estimate to help the teams in their planning. All laps driven by a team’s driver that exceed the 45% or the estimate, whichever is higher, will be deducted from the team's total lap count.
* Driver names should be announced the Friday before the start of the race by 21:00 UTC. Teams who fail to meet this deadline will start at the rear of their respective class grid.


3. Driver Names and Swaps

* Driver names must show the car class and the team number of the driver and must show the real name of the driver. Classes are distinguished by different colors of the team numbers. GT1 uses blue and GT2 uses red. The name must be white, and spaces should be used around the hyphen and between the first initial and family name. Example:

GT1: 10 – P. Kempermann
GT2: 10 – P. Kempermann

* Drivers who connect using an invalid name will receive a drive-through penalty (DT), as a name change is considered to be equivalent to a chat message and will be dealt with similarly.
* A driver who leaves the pits with the wrong name will receive a stop and go penalty (SG). While serving this penalty, the driver must change his name.
* Driver swaps may be made at any time. However, a driver may only join the server when the driver he wants to swap with is on his in-lap. The driver leaving the car must leave the server immediately after the swap.


4. Racing Modus

Qualifying

* GT1 qualifying for each event will take place the Sunday and Friday before the event, at 20:00 UTC.
* GT2 qualifying for each event will take place the Sunday and Friday before the event, at 20:40 UTC.

* Each qualifying session will last for 30 minutes. Teams may run an unlimited amount of laps during these sessions, but may only have one car on the track at all times. Each team’s fastest lap from both sessions determines their starting position.
* No more than 2 members of the same team are allowed to be on the server on the same time. Team is in this case defined as GT team, meaning that 2 members of a GT1 team and 2 members of a GT2 team are allowed on the server. In addition, GT2 drivers may not be present on the server while a GT1 qualifying session is ongoing, and vice versa.

Season 2008/2009 Race Schedule

* Race 1: 12 Hours of Kyoto GP Long: October 4th, 08:00 UTC
* Race 2: 6 Hours of South City Long: November 1st, 11:00 UTC
* Race 3: 6 Hours of Westhill International: November 29th, 11:00 UTC
* Race 4: 24 Hours of Aston GP: January 24th, 15:00 UTC
* Race 5: 6 Hours of Blackwood GP: February 28th, 11:00 UTC
* Race 6: 6 Hours of Kyoto National: March 28th, 11:00 UTC


5. Scoring

* In order to be scored, a team must cross the line after the full time has expired and the leader has finished.
* If a team is disconnected from the server, they may rejoin and start racing again. Their number of completed laps will be recorded by the organizers and kept by the tracker, and their total laps will be added up in the end and scored accordingly. If a disconnect appears to be suspicious, in that it causes the team to gain an advantage, the admins can assess a 1 lap penalty at their discretion.
* If a team is stranded on the track due to running out of fuel, an accident or other reasons, they may use Shift-S and restart the race. In that case, a penalty of 1 lap will be added to their overall time.


6. Points

* Points will be given as follows for both classes:
40, 34, 29, 25, 22, 19, 16, 14, 12, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1
This means that the 20th car in a class (which is currently not existing), does not receive any points. In the 24h-race the points will be doubled.


7. Skins

* All teams must have a distinct racing livery. If a single racing team enters more than one car in MoE, the racing liveries of these cars must differ significantly. The team’s assigned number must be placed on the sides, and hood of the car. The real names (no nicknames) of the team’s drivers must be listed on the car in a readable way; these names must be accompanied by flags identifying each driver’s nationality.
* MoE can require all teams to fit their cars with number plates, sunstrips and car markings, which are provided by MoE.
* Teams racing with no livery will be given a SG penalty (this includes teams who reconnect after a disconnect).


8. Starting Procedure

* 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.
* MoE races will use a rolling start. A pace car will lead the field during the formation lap at a reduced speed. Drivers are to run in single file until the last sector, when the pace car will slow to 80kph in order to allow drivers to catch up and assume a double-file formation. When the pace car pulls into the pits, the leader continues at 80kph. A race marshal will give the green flag signal, at which point the race has begun. Passing is not allowed before the green flag is given.
* * In all but the last sector teams are expected to leave a gap of approximately 5 cars between their car and the car ahead. In the final sector, single formation will be transferred into dual file formation. In the dual formation teams are expected to allow about half a car length between the car in front, and the car next to him.
* A car that loses its grid position during the formation lap because of a spin, empty tank or any other situation, regardless of the cause, cannot regain its grid position. It must start from the back.
* A car found to be breaking the double file formation may be assessed a DT penalty.


9. Red Flags/Race Restarts

* In the case of a server crash, or of a situation in which a large number of drivers are unable to reconnect to the server, a red flag may be declared by the admins. In this case, a red flag point will be determined, defined as the last completed lap before the server problems manifested themselves.
* Teams will be credited with the laps they have completed at the end of the designated red flag lap.
* If the race server is determined to be unreliable, the admins may move the race to a designated backup server.
* The field will be reset using data gathered from the tracker and replays, and the race will be restarted behind the safety car, in single file.
* The time remaining in the race will be based on the planned race end time, not on the time remaining at the time of the server crash.
* After one lap, the safety car will return to the pits and the race will continue with a green flag. The field will remain in single file until the green flag is waved.
* Each team's completed laps from the first part(s) of the race will be added to the result of the last part of the race, and the total tally will constitute the final standings.


10. Penalties

* Admins may impose special layouts for use during qualifying. These layouts will define restricted areas. Drivers caught violating these restricted areas will have their corresponding laptimes stricken from the qualifying results.
* Penalties will be given during the race in form of drive-through (DT) or stop and go (SG) penalties. Teams who feel they have been wronged during the race must file a protest with the organizers immediately. The race marshals will then analyse the situation and deliver a verdict.
* If a protest is made within the last hour of the race, instead of a DT or SG penalty, the penalty will be 30 or 45s added to the overall race time of the team in question in case there is no time to apply the penalty during the actual race.
* Incidents resulting from gross negligence (including incidents between GT1 and GT2 cars) can be penalized by a deduction of 1–5 laps on top of the penalty normally given, at the marshals’ discretion.
* Should a driver cause another car to lose its grid position during the formation lap, a DT or SG penalty can be given.
* It is mandatory to follow the yellow pit exit lines to ensure a safe reentry the track, those who cut the yellow pit exit lines may be given a DT. For some events restrictions may apply for the pit entry as well, but this will be announced by the admins beforehand.
* Appeals filed later than one hour after the stint of the driver who feels victim of the accident will not be accepted.
* Appeals must be filed via a form provided for it on lfsforum and must include a replay of the scene. Appeals without a replay will not be accepted.
* The admins can rule upon an accident without an appeal being filed.
* Penalties must be served within 10 minutes of the time they are issued.
* Teams may not change drivers while or immediately after serving a stop & go penalty.


11. Miscellaneous

* No chatting during the race. If a driver chats, a drive through penalty will be assessed by the race marshals. Messages must not be blocked, a driver who does block messages will be assessed a DT, since this will be considered a chat message.
* No excessive honking. If excessive honking is used, a drive through penalty will be assessed by the race marshals.
* When the race is finished, it is prohibited to drive another lap. After you have crossed the line and gotten the “FINISHED” notification at the top of your screen, gently slow down and come to a standstill after T1. The top three drivers (for both GT1 and GT2) should turn around and return to the start/finish line for a podium photo, only once the entire field has finished.
* In case a new patch is released by LFS during a running season:
o In case this occurs within 1 week of the event, the previous patch will be used to complete that even t.
o If a patch includes physics changes, car choice options and balancing values will be announced after the new patch is released.

* For ease of communication, each team must have at least one representative in the Masters of Endurance IRC channel (#moe @ Gamesurge) during each race. If/when this representative is driving, a secondary representative must be present. If a team fails to produce a representative during a race, or if the active representative is continually unresponsive to queries by the admins, the team will forfeit its fastest lap in the following round's qualifications.
o During each race, team representatives on the MoE IRC channel must use nicknames formatted as "Teamname|Nickname"
must the driver names have double or single digit numbers? i.e. 05 - B. Crooks or 5 - B.Crooks
Double, please.
rather than just updating the initial thread, can you guys at least highlight the changes to the rules when they're made, so you've got original rule and the new/changed rule, even if its just rewording something insignificant, cos going through a list of boring rules trying to guess whats changed is pretty lame, were not mind readers and if we were properly told whats changed then you'd have a far greater chance of us actually following the rule. All we'd have to do is look at the amendments and know whats different rather than guessing and possibly missing the change.
Whether it's boring or not, these "boring" rules are a guideline, it wouldn't hurt to read the in total from time to time. As for you request regarding a highlight of the rules, we'll post what we've changed in a new post in this thread, while also updating the rules provided in the OP.
Occasion: Rule added
Where: 4.Racing modus - Qualifying
What:
Quote :* No more than 2 members of the same team are allowed to be on the server on the same time. Team is in this case defined as GT team, meaning that 2 members of a GT1 team and 2 members of a GT2 team are allowed on the server. In addition, GT2 drivers may not be present on the server while a GT1 qualifying session is ongoing, and vice versa.

Reasoning:
a) Too many connections may cause unnecessary stress on the server, which may lead to an increased chance of disconnects.
b) Teams who have to qualify cannot connect due to other teams spectating.
c) Teams should only join the server when it is their class specific time to qualify.
Outcome: Admins will reduce a team's server presence to 2 drivers by kicking inactive (spectating) drivers. If a driver reconnects and as a result brings his team's server presence to more than 2 drivers, that team will lose its fastest lap for that session. If a team's drivers repeatedly connect during the wrong class's qualifying session, that team will have +1s added to their fastest lap for their session.


Spectating can be done by LFS remote & LFS world.
thumbs up for the added rule

But I already see GT1 drivers asking to stay on server to watch
Quote from AppiePils :Whether it's boring or not, these "boring" rules are a guideline, it wouldn't hurt to read the in total from time to time. As for you request regarding a highlight of the rules, we'll post what we've changed in a new post in this thread, while also updating the rules provided in the OP.

You know what im getting at though, you could read through the rules and not spot something because your reading every other word because you've already read this once, and when it comes to the 4th time the rules are updated 'it wouldn't hurt to read the in total from time to time' isnt really the case is it, and if this time they dont read and they dont know a rule... well its hardly ideal either. The most important thing in the rules is that people know them and follow them. Its that simple, the hard bit is making sure people know them and IMO helping to clarify whats changed makes it much easier for everyone involved and should ensure everyone is on the same rulebook, and those who arent are only incorrect by there own doing, not because something was tweaked or added which went unnoticed whether they tried to find it or not. Provided people have read the rules once, and read the updates (which are now easily accessable) theres not really any excuse, and you've done everything within reason to make it clear, whereas before we had to kinda hunt the change.

Anyway, the change is much better and nicely layed out, cant see how people would miss them now, especially as the thread is updated when the rule change is added as opposed to just an editted OP. thx
Occasion: Rule clarification
Where: 2. Numbers of drivers during a race weekend.
What:
Quote :* During a race weekend a minimum of 3 and a maximum of 4 drivers must race for a team. In the 12hr and 24h race, a maximum of 6 drivers can race.

Reasoning:
To be more clear about what we consider a race weekend: a race weekend includes both the qualifications and the actual race. People who qualify for a team are part of that team's group of racers that is performing for that particular weekend for that particular team. We also upgraded the number of racers for a race weekend for the 12h race to a maximum of 6 racers. Do take into consideration that the 45% rule for the actual race still applies (ergo a minimum of 3 racers for the actual race is required).
Outcome: Having more than the maximum amount of drivers race during a race weekend, will lead to the removal of drivers till the allowed amount of participating drivers is reached. Any laps driven by this driver (/these drivers) will be removed from the teams total driven laps.
Occasion: Added Rule
Where: 9. Penalties.
What:
Quote :* It is mandatory to follow the yellow pit exit lines to ensure a safe reentry the track, those who cut the yellow pit exit lines may be given a DT. For some events restrictions may apply for the pit entry as well, but this will be announced by the admins beforehand.

Reasoning:
To ensure a safe reentry on the track it is mandatory to follow the yellow pit exit lines. Restrictions regarding the pit entrance will be announced by the admins before the start of an event.
Outcome: Failure to do so can be protested against, and if declared valid, is subject to receive a DT.
Can you clarify how much excessive cutting will be in the race at the chicane? ty
If we see or are alerted to a car repeatedly cutting the chicane (i.e., hitting poles without appearing to try to avoid them), we will assign a marshal to follow that car. If we see the car subsequently hitting the poles lap after lap, that car may be subject to a DT penalty.

In short, hitting the poles is never a good idea. Making it your normal driving line is a terrible idea, and you WILL get penalized for it.
Rules changes in advance of Round 2:

Occasion: Added Rule Section
Where: 9. Red Flags/Race Restarts
What:
Quote :* In the case of a server crash, or of a situation in which a large number of drivers are unable to reconnect to the server, a red flag may be declared by the admins. In this case, a red flag point will be determined, defined as the last completed lap before the server problems manifested themselves.
* Teams will be credited with the laps they have completed at the end of the designated red flag lap.
* If the race server is determined to be unreliable, the admins may move the race to a designated backup server.
* The field will be reset using data gathered from the tracker and replays, and the race will be restarted behind the safety car, in single file.
* The time remaining in the race will be based on the planned race end time, not on the time remaining at the time of the server crash.
* After one lap, the safety car will return to the pits and the race will continue with a green flag. The field will remain in single file until the green flag is waved.
* Each team's completed laps from the first part(s) of the race will be added to the result of the last part of the race, and the total tally will constitute the final standings.

************************

Occasion: Added Rule
Where: 11. Miscellaneous
What:
Quote :* For ease of communication, each team must have at least one representative in the Masters of Endurance IRC channel (#moe @ Gamesurge) during each race. If/when this representative is driving, a secondary representative must be present.
* During each race, team representatives on the MoE IRC channel must use nicknames formatted as "Teamname|Nickname"

Reasoning: IRC is used as a quick and central means of communication, and the presence of all active teams will not only speed up the communication process between the admins and the teams, but also between teams themselves.
Outcome: If a team fails to produce a representative during a race, or if the active representative is continually unresponsive to queries by the admins, the team will forfeit its fastest lap in the following round's qualifications.

************************

Occasion: Added Rule
Where: 10. Penalties
What:
Quote :* Penalties must be served within 10 minutes of the time they are issued.

Reasoning: Teams must serve penalties in a timely fashion.
Outcome: Teams failing to serve penalties within the allotted time will find their penalty increased to the next level of severity.

************************

Occasion: Added Rule
Where: 10. Penalties
What:
Quote :* Teams may not change drivers while or immediately after serving a stop & go penalty.

Reasoning: Penalties must not be used for constructive means.
Outcome: A team who completes a driver change while serving a penalty will receive a second stop & go penalty.

************************

Occasion: Added Rule
Where: 8. Starting Procedure
What:
Quote :* Each team's starting driver must be present in the server within 10 minutes of the scheduled start time.

Reasoning: To ensure that the races are started on schedule.
Outcome: Drivers who fail to meet this deadline will start from the rear of their class's grid.
Good updates. One question:
Quote from DeadWolfBones :************************

Occasion: Added Rule
Where: 10. Penalties
What:

Reasoning: Teams must serve penalties in a timely fashion.
Outcome: Teams failing to serve penalties within the allotted time will find their penalty increased to the next level of severity.

************************

How do we go about when a penalty is incurred with less than 10 minutes to go in the race?
Quote from traxxion :Good updates. One question:

How do we go about when a penalty is incurred with less than 10 minutes to go in the race?

per rules:
Quote :* If a protest is made within the last hour of the race, instead of a DT or SG penalty, the penalty will be 30 or 45s added to the overall race time of the team in question in case there is no time to apply the penalty during the actual race.

Quote from AppiePils :per rules:

Ah, I thought that, but this rule makes me think it that only applies to protests. Maybe a clarification of the fact that it's for penalties in general would be in place?
Forgot to put this here when we changed it on Sunday:

Occasion:
Edited Rule
Where: 4. Racing Modus
What:

Quote :Qualifying

* GT1 qualifying for each event will take place the Sunday and Friday before the event, at 20:00 UTC.
* GT2 qualifying for each event will take place the Sunday and Friday before the event, at 20:40 UTC.

Reasoning: This provides a larger window between the GT1 and GT2 sessions, and will hopefully prevent GT2 teams from joining the server while the GT1 session is ongoing.
About my name... it is not possible to put space between the first initial and family name because of length. i.e. I can't set:

09 – D. Marjanović

but I could use:

09 – D.Marjanović

Please, advice needed on this. Thanks.

Quote from DeadWolfBones :3. Driver Names and Swaps...The name must be white, and spaces should be used around the hyphen and between the first initial and family name. Example:

GT1: 10 – P. Kempermann
...

Quote from marecare :About my name... it is not possible to put space between the first initial and family name because of length. i.e. I can't set:

09 – D. Marjanović

but I could use:

09 – D.Marjanović

Please, advice needed on this. Thanks.

This is acceptable, if required by space limitations.

Thanks for asking!
Occasion: Added Rule
Where: 8. Starting Procedure
What:
Quote :* During the formation lap it is not allowed to swerve from left to right, or overly accelerate/brake (so called tire heating). During single file teams are expected to follow the normal race line and during the dual file formation. Teams are expected to allow about half a car length between the car in front, and the car next to him.

Reasoning:
Sudden, unexpected, movements make it hard for teams to follow the single file formation procedure. Half a car length difference between the car in front and next to should allow a safer starting procedure.
Outcome: Drivers who fail to follow the above guidelines can be protested and are subject to be penalized.The type of penalty depends on the severity and impact of the offense.
There is something wrong with the scoring system me thinks: if you get 40pts per victory in a standard 6 hours race and double points in the 24 hours one, shouldnt you get 40*1.5 points for winning in the 12 hours?

This isnt a suggestion since we've already past the 12 hours, but something to consider for future seasons.
So, basically, Tyre heating during the formation lap is no longer allowed?
That's balls to be honest, I'd bet my house on it being far more dangerouse having 30 cars bombing into t1 with cold tyres at south city than having accidents in the warm up lap.

Btw, these problems only came around because of a few specific idiots, and the safety cars pace dropping by quite alot on the back straight of south city.
Quote from Bawbag :That's balls to be honest, I'd bet my house on it being far more dangerouse having 30 cars bombing into t1 with cold tyres at south city than having accidents in the warm up lap.

Btw, these problems only came around because of a few specific idiots, and the safety cars pace dropping by quite alot on the back straight of south city.

total agreement.

Having 60°C on the tyres is much more dangerous than weaving in the warmup lap
Quote from Commander :So, basically, Tyre heating during the formation lap is no longer allowed?

Quote from Bawbag :That's balls to be honest, I'd bet my house on it being far more dangerouse having 30 cars bombing into t1 with cold tyres at south city than having accidents in the warm up lap.

Btw, these problems only came around because of a few specific idiots, and the safety cars pace dropping by quite alot on the back straight of south city.

Tire heating is strongly limited to small, predictable movements, within that half a car frame. We will also increase the speed of the safety car on the straights to increase the tire temperature under braking.

FGED GREDG RDFGDR GSFDG