[FEATURE]: Expanded Restart Schedule

[mtgtnt]

Scope

Web

Feature Description

Please expand the restart schedule to include weekly, bi-weekly, monthly or even a running hour count. For example every 168 hours. I do not need hour or even daily restarts. I can see a weekly or bi-weekly restart though.

Use Case

No response

Proposed Solution

No response

Additional Info

No response

[prosilentgamer2]

At this point you may as well do it yourself as its clear the server is not big

[mtgtnt]

You are right, but I do not have just one server. Didn't think about that, did ya? /sarcasm

Automation in all possible ways is only a plus for server owners.

[prosilentgamer2]

Feel free to edit the code to add this in and make a PR, your the only one ive seen want such a werid request

[yorick2002]

Scope

Web

Feature Description

Please expand the restart schedule to include weekly, bi-weekly, monthly or even a running hour count. For example every 168 hours. I do not need hour or even daily restarts. I can see a weekly or bi-weekly restart though.

Use Case

No response

Proposed Solution

No response

Additional Info

No response

Why would you not need daily restarts? Most server owners restart their server(s) at least once a day to prevent strange issues from happening. It doesnt hurt to restart at a time where your players are not online.

[tabarra]

Thanks for the suggestion, but I don't think this will be implemented anytime soon.
Changing from a 24h-based system to a multi-day system makes the code significantly more complex, specially because it needs to keep track of previous restarts (even across tx reboots) as well as being tricky to have that while also having a 24-hour based restarts, as it could lead to restarts coinciding.

While fxserver has gotten more stable with time, making 2x a day restarts less needed, still not many servers can go by over 1~3 days without a restart, which means that the "effort/risk/reward" calculation for this feature is not really favorable.

That being said, if I continue to receive feedback regarding this need, I will for sure re-visit it.
And because of that, I'll leave this issue open for now to invite more opinions or more arguments.

[tabarra]

On second thought, this wouldn't be that hard to implement.
The input would still be hour, but with an additional field for cadency, where you would be able to select "every day, every X days, ... every week".
And then the scheduler would just need to keep track of when this particular restart time was last executed, and then "skip" it.
This would still pose a challenge for the UI, as this would be too hard to show on the sidebar, so a dedicated page showing upcoming restarts would be required.