When a game/battle ends the next battle/game is starting at the exact same time and weather conditions the old battle/game ended. This creates an issue if that time is in the middle of the night as the server just dies as players jump out rather than deal with nighttime play on a vanilla (no NVG and super dark) server.

I could be wrong, but I'm 80% sure this didn't used to be the case. That's because in the past all players were all kicked and the server and it was restarted. When the server came back it was set to what felt like a random time of day and weather (or so it seemed random).

The lack of a restart means the time is now the same as the end of the game.

Suggestion;

** Regardless of if it was random or not or if night was a valid start time, going forward, I suggest that there is an option to set the server config JSON along the lines of a "Mission Start Time." The value specified should bound the random start time. For now I can see two useful. One for servers that don't have NVGs/legacy (we can call it Default). The second is Any for any time of day:

Default: (as early as shortly before dawn where there is some light to mid-day giving players 4-5 hours to get situated before the first night)
Any: Any time of day.

Feel free to add more configs but as noted this coves it.

Example of use:
1) Server owner specifies a valid config value or leaves it alone (invalid or missing defaults to "default")
2) Server knows the geoloc of the map for the lat/lon data in the map file. From there it can build the "physical time bound" based on the date and create a random time.

In the future it might be nice to specify a start date (not so much a time but a date) like in DayZ. Can't wait to see winter battles in vanilla Reforger...