I think we should update moderation rules for big drops
If game crashed in menu or before mission - that's ok, timeloss about 20-30 seconds looks minor.
But I had drops in the end of 5-6 minutes mission, late game mission - that's pure restart of run (and restrat every >1 hour run looks bad, worse kind of random).
I thought we can consider to calculate time of drop, add it in run submission and remove this time. E.g. in the last run of Gabriel I have:
49:15-52:06 - drop, 2 minutes, 51 seconds.
First timepoint - load screen of failed mission. Second timepoint - double click of game.exe.
I think we can ignore drops not during mission, it's bad but not so sad. I had drops on 6 minutes missions and on the last life of Belzepuz too, that's a real sadness.
If you agree, we can recalculate time of our runs. If not, I understand.
So if I understand, for example : I start a mission at 42min, and that mission crashes at 45min, we restart the timer at 42min once we click on AvsD.exe ?
I'm not sure about all this livesplit staff, how to restart timer to previous point, but it looks correct. So if you start mission (load screen) e.g. 42:25, game is crashed on the mission 43:34, then you double-click on game icon 43:38, your timer is changed to 42:25 (if no timer - then we just calculate 43:38-42:25=1:13, we'll just cut 73 seconds from final timer. BUT anyway there will be minor crashes when you need to reload game, wait load screen, go to campaing, those 20-25 second will not be cut (because in this case we need to do this 5-6 times per every run, i guess).
Let me game an example: my the latest Gabriel is 1:14:35. Crash 49:15 (start of mission) -52:06 (double click on game), so final updated timer will be 1:14:35 - (52:06-49:15) = 1:14:35 - 2:51 = 1:11:44
If this ruleset is OK for you, you have no better opinion - we could inplement it. I'll make a guide about it and will update category rules.
