Conversation
Protonull
force-pushed
the
uuidv5-offline
branch
from
3739bea to
f32613f
Compare
I figured that, given the recent PRs, it would be rude to make their instances start throwing.
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
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.
This uses UUIDv5 to generate deterministic UUIDs for non Mojang-auth'd players. UUIDv5 takes a "namespace" UUID and a value, so a reimplementation of Java's
UUID.nameUUIDFromBytes()to turn "mapsync:server" into a namespace UUID. Given that Mojang uses UUIDv4 for authenticated players, using UUIDv5 means having a valid UUID without introducing any risk of collision.This will require that people delete (or update) their
uuid_cache.jsonandwhitelist.jsonfiles if they've used unauth mode, otherwise they will fail to parse.