Improved system for saving player settings #3
Conversation
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
…d of a single file
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.
Hello,
I created this version because saving all players in the same file is very heavy when you have many unique players on the server. This causes slowdowns (increased mspt) when loading and saving players, which often happened with the save on logout.
In this version the player information is saved in one file per player. This creates more files but they are smaller and therefore easier to edit when saving.
The player's settings are only saved when he changes one of his settings.
To avoid problems with older versions of the plugin, the version includes an automatic migration system from the old storage system to the new one.
If you have any questions, don't hesitate!