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
Due to a number of reasons, our group is playing every 1-3 weeks in a very irregular basis. I like to have half-hourly backups in general so that if I run into a problem I'm less likely to lose a lot of progress, but I've also already run into two issues that I didn't learn about for days after (2 weeks after in one case)... storing half-hour saves for weeks is a bit much.
Is there a way to have the current configuration automatically mark a certain number of saves per 24-hour period as keep? This way I could set it to 1 and, if I have it set to hourly backups and save 24, it would give me a days worth of hourly back ups and a running single backup ongoing (maybe with it's own limit, so I could set it to something like 60 days, thereby saving 1 per day for 2 months back).
Thanks!
The text was updated successfully, but these errors were encountered:
This isn't something that's possible with the current configuration options, but if you'd like to submit a pull request for this feature, I'm happy to review it.
Due to a number of reasons, our group is playing every 1-3 weeks in a very irregular basis. I like to have half-hourly backups in general so that if I run into a problem I'm less likely to lose a lot of progress, but I've also already run into two issues that I didn't learn about for days after (2 weeks after in one case)... storing half-hour saves for weeks is a bit much.
Is there a way to have the current configuration automatically mark a certain number of saves per 24-hour period as keep? This way I could set it to 1 and, if I have it set to hourly backups and save 24, it would give me a days worth of hourly back ups and a running single backup ongoing (maybe with it's own limit, so I could set it to something like 60 days, thereby saving 1 per day for 2 months back).
Thanks!
The text was updated successfully, but these errors were encountered: