Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not save chunks when auto saving is disabled #1280

Closed
wants to merge 1 commit into from

Conversation

PetteriM1
Copy link
Member

This fixes #272

Currently Nukkit saves the chunks when the level is unloaded even if auto saving is disabled. This pr makes chunks to be never saved automatically if the auto saving is disabled (and if none of your plugins does the saving or you don't use the save-all command). The question is: Should disabling auto save only disable the auto save task or also the saving Nukkit does when levels are unloaded? Not saving chunks at all when the auto saving is disabled may be usefull on minigame servers where the worlds will be reseted after a match anyways.

@SupremeMortal
Copy link
Member

I don't think this is correct. Auto-save is the task of saving the world regularly whilst it's running so in the event of a crash, the server does not lose as much data. The proposed change turns auto-save into a property more like read-only or non-persistent world which should be a separate configuration field.

@Guillaume351
Copy link

Creating a separate setting for this could be good, it’a much easier to reset mini game maps when you can just unload and reload them

@PetteriM1 PetteriM1 marked this pull request as draft July 8, 2023 18:32
@PetteriM1
Copy link
Member Author

Proper API included in #2175

@PetteriM1 PetteriM1 closed this Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

disabling auto-save doesen't work
3 participants