[Network] Automatically pause server when 0 clients are connected

[jamespetts]

Time can often be critical at certain junctures of multiplayer games: one might go to bed one evening making a good profit, and wake up the next morning bankrupt. There is much to be said, therefore, for a feature that maximises players' use of time: (optionally) automatically pausing the server when no clients are connected. That way, time will only pass when at least somebody is actually playing.

Another worthwhile (and related) option might be to have the option on the server to enforce certain times of day during which the game is paused (but viewable in its paused state by clients logging in), again, to enable the server administrator to make sure that people are not disadvantaged by only being able to play at regular hours.

[prissi]

I though about this too. But then, the progress of time would be very non-linear, depending on joining. This should be definitely couples with acertain uptime (which can be even achieved already using scripted start/stop of severs using the nettool),.

[jamespetts]

Ahh, I didn't realise that the scheduled uptime was possible with nettool. I'll have to look into whether this can be used with Experimental (and, if not, adaptations). Do you think that the pausing when 0 clients are connected could work well with the scheduled uptimes, or do you think that scheduled uptimes on their own are the way to go?

[jonasbb]

Maybe you could include up times like this. Would be a bit complexer to configure but it has the two ideas of you included.
You have three types:

• allways on
• allways off
• on when someone is logged in

This would give you the possibility to have a more or less linear timing because you can be sure that at least 2,5 (or whatever) years have passed since the previous day.

But it would allow players to play longer than this 2.5 years if they like and have the time to do so.

[jamespetts]

That idea could work.

[Ashley]

So long as this is optional, sure