Add option to create N backups when there are no players#68
Merged
Conversation
There was a problem hiding this comment.
✅ All localization files have been checked and are complete! ✅
Waiting for approval by @MelanX
There was a problem hiding this comment.
✅ All localization files have been checked and are complete! ✅
Waiting for approval by @MelanX
MelanX
added a commit
that referenced
this pull request
Jan 12, 2026
* Add option to create `N` backups when there are no players closes #59 * Fix backup logic when no players are online
MelanX
added a commit
that referenced
this pull request
Jan 12, 2026
* Add option to create `N` backups when there are no players closes #59 * Fix backup logic when no players are online
MelanX
added a commit
that referenced
this pull request
Jan 12, 2026
* Add option to create `N` backups when there are no players closes #59 * Fix backup logic when no players are online
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces the feature to set an amount of backups that should be created after the last player left the world -
noPlayerBackupCount. It defaults to1which was the default behavior before. That means, that the next backup will still be created. After this, no backups are made unless a player joined.The other config option I added -
noPlayerBackupTimer- introduces a new timer. That timer will be used if there's no player in a world. Setting it to0would just use the default timertimer. If you havetimerset to120, every 2 hours a backup will be created. If you setnoPlayerBackupTimerto180, it'll take 3 hours until the next backup will be created. Once a player joins between 120 and 180 minutes in this example, the backup triggers instantly.By joining a world, the
noPlayerBackupCountwill be reset internally. So, even joining for 1s would result in starting over with a new "countdown".closes #59