No idea which language it is in. All I know is that Wolle who did all the backend stuff for www.lfs-tracker.de has further plans to simplify matters but simply has no time to realize them at the moment.
It can, if you give us the manpower to do it. The problem is, compared to two years ago, that we all are working nowadays. That lessens the time available to invest into coding stuff.
The penalty for a chat is a drive through, if a penalty has to be given in the last hour of a race (or after the race), it is either 30s for a drive through or 45s for a stop and go, as it says in the rules. That is the way LFS handles it (last 3 laps) and the FIA handles it. Therefore, we handle it that way as well. Besides, the actual drive through the pit lane may be shorter, the time you lose entering and exiting the pits however should make up for it (at least seen on an average for all tracks in MoE).
Claiming he was not part of your line up may be true in a very narrow point of view. He is still part of your team, though. Therefore it is up to your team's responsibility to keep your drivers' discipline up high enough in order not to get penalized.
Besides, what individual penalty is there to give? MoE is NOT an individual scoring racing series, it's a team series. Therefore, a team has to stand up for the wrong doings by one of their members, no matter whether in the driver line up or not. It is up to the team to take individual discipline matters.
The results need some work on the tracker first, which cannot be done before tomorrow night. We will have all penalties and stuff sorted by then, so we can get them final asap.
About the videos/replays: at times it can be better to have a replay available. Most of the times the incidents are pretty clear cut, so it is enough to have a vid, as long as it covers enough and is of the heli cam. Covering enough means a couple (~10-15s) before and after the actual contact.
Keep the replay, though, we might ask for it after all.
We have had a few notifications about changed drivers / misspelled drivers: These things can only be corrected after the race. That also means, the laps done by i.e. SK's new third driver can only be added after the race. Sorry for the inconvenience, but we have currently no access to the output side of the tracker.
Their laps will be recorded, just not shown right now.
Reset-Penalties (Shift-S, Shift-P) will be added AFTER the race finishes since our tracker-guru is not at home currently. Just be aware of that in possible lapping situations.
#1: Core Racing (#29): +2s on quali time for chatting
#2: spdo Racing (#16): Quali time disallowed for trying to abuse the possibility to reset the car on the server twice. Will start from the back of the grid.
In race:
#3: F1RST Racing GT1 (#06): DT for avoidable contact with Triple Seven Racing GT2 (#23)
#4: Bandelnet Racing Team GT1 (#18): DT for avoidable contact with CoRe Racing GT2 (#29)
Post race:
#5: mb-racing.org GT1 (#08): Unsafe re-entry into track following accident, resulting in serious secondary accident with Team XFR GT2 (#24). Penalty is a deduction of 2 laps for gross negligence. Normally, a Stop & Go would have been given during the race on top of it that got overlooked.
#6: clownPaint Racing (#11): +30s for chatting (normally a Drive Through, but race was finished).
#7: SK Gaming (#02): +30s for avoidable contact with Mercury Racing GT2 (#22). Normally, this would have been a Drive Through, but the penalty couldn't be given until after the race. The protest was deemed in time even though it was filed more than an hour after the initial end of the stint of the respective driver. However, since the very same driver had to jump back into the car almost immediately due to technical problems for his teammate, the stint of the respective driver is deemed to have ended with the race at approximately 18:15 CET. The protest was filed at 19:04 CET (board time) which means it was within an hour of the end of the stint.
A warning is issued to everyone to obey Yellow Flags. The accident between #8 and #24 was purely #8's fault, #24 could have lessened the impact by actually doing what Yellow Flag's mean: slow down, prepare to stop. The brakes weren't touch one second in this incident. Should such a situation occur again, we are considering giving penalties.
Sorry, not changing that now anymore, as long as the LFSWorld nicks were correct the data will be accounted for by the tracker. I've sent the list to our tracker guru already, so changes now only if they are an absolute emergency.
I just finished the list. Anyone who hasnt posted their drivers is in the list currently with their SO4 lineup. So if you have changes or not participated in SO4, hurry.
As it looks right now, we will be able to finish. Upon this post we have had a few people coming up offering their help. We would still gladly have more, so don't think just because it is not as urgent anymore, we will not look for more help. The situation is just not quite as serious anymore.