Save and load all modified chunks #331
Merged
Conversation
This file contains 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
Ralith
reviewed
Dec 18, 2023
patowen
force-pushed
the
loading-voxels
branch
2 times, most recently
from
add052c to
d53b969
Compare
Ralith
requested changes
Jan 9, 2024
patowen
force-pushed
the
loading-voxels
branch
from
d53b969 to
f8a02ac
Compare
Ralith
approved these changes
Jan 11, 2024
|
Thanks for reviewing/merging! |
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.
Whenever a block is updated, ensure that an updated version of the relevant node is written to the save file. When a world is initialized on the server-side, all modified chunks are loaded from the save file and stored in memory, to be retrieved whenever the relevant node is to be added to the graph.
This is a temporary implementation, as it does not properly scale for larger worlds, where we may not want to store all modified chunks in RAM.
Note that while this implements loading save data, it only loads voxels. Entity locations, such as the player's location, are ignored.