You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you read the Important information text above
Yes i did
Current behavior
container must be manually restarted (or a system cron job created to restart it) and if players are connected, this risks save file corruption.
Desired behavior
container uses a daily (or other interval) script against (possible options)
RCON to see if players are connected, if no players are connected, it restarts the game server or if players are connected then either skips the scheduled reboot or does a broadcast message to the server that the reboot is pending in XX minutes
if RCON isn't a good option, can the incoming UDP datagrams be monitored and if no UDP traffic in YY interval, declare server is 'idle' and restart game server?
why this is needed: early access games typically have memory leaks that over time lead to poor performance or file corruption. less risk of corrupting saves if restarted with no players connected.
Links to screenshots
No response
To Reproduce
Steps to reproduce the behavior:
new feature request
Software setup
OS: centos
Docker: 25.0
Hardware setup
vCPU: 6
RAM: 16
Disk: 2tb
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hey @GMBridge the new exit-trap-handler should softly exit the game now and not kill it totally. I assume the server saves before but im not sure ... 🤷
Regarding the other stuff, please look at #27 the part about rcon things before stop.
jammsen
changed the title
feature request - daily/scheduled game server restarts if no players connected
[Feature Request] - Daily/scheduled game server restarts if no players connected
Jan 25, 2024
Will look into this for the server restart feature I'm implementing, will discuss it with @jammsen on the best way to do it 😊
Feel free to spark ideas or links for us to be inspired ✨
This is fixed in the release on latest from 5 minutes ago. See Changelogs or Discord message regarding the new release and what to lookout for. We dont cover the idle part, but you can setup restarts via Cron-Expressions, which should help you out.
Im closing this issue as resolved, feel free to reach out again if you need help.
If you like this project, please consider giving this repo and the Docker-Hub-Repo a Star.
Have you read the Important information text above
Current behavior
container must be manually restarted (or a system cron job created to restart it) and if players are connected, this risks save file corruption.
Desired behavior
container uses a daily (or other interval) script against (possible options)
why this is needed: early access games typically have memory leaks that over time lead to poor performance or file corruption. less risk of corrupting saves if restarted with no players connected.
Links to screenshots
No response
To Reproduce
Steps to reproduce the behavior:
Software setup
Hardware setup
Additional context
No response
The text was updated successfully, but these errors were encountered: