Thanks for all the answers.
Definitely worth checking into. However, I believe only one race does this in one series? It's really up to the devs if they want to put the time in... But I'll mention it.
As for 3-wide starts it's not just about being 3-wide. In Indy 500 safety car pulls far away before leader starts picking up the pace. In rF leader would get EOLL penalty for not keeping up with safety car.
Another example - NASCAR forbids crossing lanes during double-file restarts. Even leader can be black-flagged if he crosses lanes before finish line, as it happened during this year's Daytona 500.
Last year in IndyCar about 4 drivers wasted their "push to pass" on race start, because cars were not properly lined-up and there was no green flag.
Paul Tracy nearly won Indy 500 once - he passed the leader but like 2 seconds later there was a FCY. Indy 500 rules stated that track order will revert to end of previous lap.
In NASCAR there can be a "competition yellow" on say, lap 50, and no refuelling is allowed before that lap.
And so on... Implementing all this would be insane and rules keep changing.
That's why I suggested a plugin interface for this on RSC forums, and here, on this forum:
LINK
People would be able to write their own server-side plugins that ask rFactor for things like: "is that guy in pitlane?", "is safety car in pitlane?", "are these guys side by side?", "did that guy serve S&G?", "is that car out of control?", "is that car on track?". And the same plugin would tell rFactor: "Let safety car go on track now.", "let safety car accelerate to 130 mph now", "give that guy a DT penalty", "tell that guy to stay behind that guy" and so on.
So more less something like spotter interface, but server-side and related to race control.
Simply put - implementing various race rules would cost you time. You could stick to just basic race rules ("road", "road with rolling start" and "oval") and invest saved time on implementing such plugin interface. Not necessarily in initial release of rF 2
