Make block hashes more dynamic to avoid registry collisions #918
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
# Conflicts: # server/block/hash.go
# Conflicts: # server/world/block_state.go
# Conflicts: # server/block/hash.go
# Conflicts: # server/block/hash.go
DaPigGuy
reviewed
Sep 3, 2024
DaPigGuy
approved these changes
Sep 3, 2024
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.
Currently the number of bits given to each block is fixed from
cmd/blockhash, which limits the number of custom blocks that can be registered before there are hash collisions. This pull request makes it so the number of bits is dynamically allocated at runtime to account for every block that has been registered before the server starts to avoid collisions completely.