Respect autoSaveInterval values less than 1#111
Open
brickmonster wants to merge 1 commit intoTuinity:mc/1.21.5from
Open
Respect autoSaveInterval values less than 1#111brickmonster wants to merge 1 commit intoTuinity:mc/1.21.5from
brickmonster wants to merge 1 commit intoTuinity:mc/1.21.5from
Conversation
brickmonster
force-pushed
the
fix/autosave-interval
branch
from
cc348d2 to
45be393
Compare
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
1 participant
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.
chunks.auto-save-interval uses 0 to indicate "do not auto save".
When it's negative or default it instead delegates to ticks-per.autosave which uses values less than 1 (docs are incorrrect) to indicate "do not auto save"