You could dictate that members of your league create a standalone install (and Data Path) for your league. This isn't at all uncommon for leagues to do. Then just have a policy to not upgrade the server until the build is 1 week old and instruct members to not upgrade the install that is dedicated to your league until directed by you. Normally people spot the bugs within a few days so one week should be a safe timeline. You will probably say this is too much to ask, but I have been in several leagues that operate this way with rF1. The reason for doing this in rF1 was to be sure everyone had the right content and didn't trash it up installing other mods unrelated to the league. In rF2 we shouldn't have these problems thanks to the new content management. But with all the bugs it is probably a good idea. I am sure the dev cycle will slow down and new bugs will not get introduced as often. This lag bug is due to a rather significant and complex feature that they are currently working on which is the ability to reconnect to a race session if you get disconnected. Once the feature set is fixed, the builds should be more stable.