The results for the 24h of Aston have been provisional for quite a long time now. The root cause for this has been the advent of longer car damage repair times and the fact that engine damage cannot be repaired under the last patch.
While most teams welcomed this change for the improved realism it brought, it unfortunately gave rise to a certain type of behaviour which we cannot tolerate. It turned out that a few teams used a loophole in the rules to gain an advantage by intentionally disconnecting from the server at favourable spots of the track. The intentional disconnect allowed for the teams to have a second driver reconnect in a very short time which thus saved the team the time of the pit stop, and more importantly gave them a repaired car with no engine damage and no lost lap.
While this activity was not clearly forbidden by the rules, it was nevertheless contrary to the spirit of sportsmanlike behaviour that the MoE organisation has always held up as the main principle of this series. The past seasons' and even the recent 24h race's success were due in large part to the fact that the participating teams bought into this sense of sportsmanship by being fiercely competitive but also friendly and respectful towards their opposition. Even the current issues have not changed this and we are keen to keep it that way.
Therefore, we decided we needed to act upon using this loophole despite it not being in the rules. After lengthy discussions we came up with the following solution:
1. Any disconnect and/or shift-s/-p that a team gains a distinctive advantage from, such as repaired engine damage or the discounted time of the pitstop, will be penalized by deducting one lap from the team's total.
2. If we deem the disconnect/shift-p/shift-s to have been intentional, we additionally deduct 33% of the points the team gained in the race.
For the last race, we will modify this penalty a tad bit: teams who responded to our request for confessions and admitted to their intentional use of the loophole are only charged with 25% of the points gained.
Therefore, the results and standings for the 24h of Aston will be modified as follows:
Team #02: -2L and -33% pts
Team #03: -1L and -33% pts
Team #10: -1L
Team #20: -1L and -33% pts
Team #26: -2L and -33% pts
Team #31: -1L and -25% pts
Team #33: -1L and -25% pts
With the exception of team #10, Pedal to the Metal, the reasons for the investigated disconnects given by the respective teams did not convince the admin team. Team #02, SK-Gaming, admitted one disco which was the one at the end of the race. However, the explanation given for the other one was not convincing which is why the 33% points deduction is applied and not the 25%.
In the future, the 25% points deduction will not exist. We will still investigate suspicious disconnects. We will have to do this manually, so results will be provisional for a couple of days after the race. Since the remaining races of the season are much shorter, we expect the delays to also be much shorter.
Philip Kempermann on behalf of the Admin Team of Masters of Endurance
edit: Additionally, My3id will be given 1 lap back, as their shift-p was due to a LFS bug and not of their own doing.
While most teams welcomed this change for the improved realism it brought, it unfortunately gave rise to a certain type of behaviour which we cannot tolerate. It turned out that a few teams used a loophole in the rules to gain an advantage by intentionally disconnecting from the server at favourable spots of the track. The intentional disconnect allowed for the teams to have a second driver reconnect in a very short time which thus saved the team the time of the pit stop, and more importantly gave them a repaired car with no engine damage and no lost lap.
While this activity was not clearly forbidden by the rules, it was nevertheless contrary to the spirit of sportsmanlike behaviour that the MoE organisation has always held up as the main principle of this series. The past seasons' and even the recent 24h race's success were due in large part to the fact that the participating teams bought into this sense of sportsmanship by being fiercely competitive but also friendly and respectful towards their opposition. Even the current issues have not changed this and we are keen to keep it that way.
Therefore, we decided we needed to act upon using this loophole despite it not being in the rules. After lengthy discussions we came up with the following solution:
1. Any disconnect and/or shift-s/-p that a team gains a distinctive advantage from, such as repaired engine damage or the discounted time of the pitstop, will be penalized by deducting one lap from the team's total.
2. If we deem the disconnect/shift-p/shift-s to have been intentional, we additionally deduct 33% of the points the team gained in the race.
For the last race, we will modify this penalty a tad bit: teams who responded to our request for confessions and admitted to their intentional use of the loophole are only charged with 25% of the points gained.
Therefore, the results and standings for the 24h of Aston will be modified as follows:
Team #02: -2L and -33% pts
Team #03: -1L and -33% pts
Team #10: -1L
Team #20: -1L and -33% pts
Team #26: -2L and -33% pts
Team #31: -1L and -25% pts
Team #33: -1L and -25% pts
With the exception of team #10, Pedal to the Metal, the reasons for the investigated disconnects given by the respective teams did not convince the admin team. Team #02, SK-Gaming, admitted one disco which was the one at the end of the race. However, the explanation given for the other one was not convincing which is why the 33% points deduction is applied and not the 25%.
In the future, the 25% points deduction will not exist. We will still investigate suspicious disconnects. We will have to do this manually, so results will be provisional for a couple of days after the race. Since the remaining races of the season are much shorter, we expect the delays to also be much shorter.
Philip Kempermann on behalf of the Admin Team of Masters of Endurance
edit: Additionally, My3id will be given 1 lap back, as their shift-p was due to a LFS bug and not of their own doing.