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

[FEATURE] Use player data to save a non-object specific backup of the database #110

Open
Happyrobot33 opened this issue Oct 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@Happyrobot33
Copy link
Collaborator

The basic idea is that since we store the database in a player object, if the player object completely delinks its network ID, all persistence info related to it is lost. The general idea behind this feature would be this

On world join, copy the database into the playerdata if it is valid (we only do this on world join to avoid the large possible network write costs that can happen since all player data is synched at once. This does mean data loss is still possible if changes are made, although maybe a button can be added to do this possibly larger cost sync). We can then have a way to restore from this backup if everything is lost

Related branch persistence

@Happyrobot33 Happyrobot33 added the enhancement New feature or request label Oct 11, 2024
@Happyrobot33 Happyrobot33 self-assigned this Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

1 participant