Skip to content

Use resolved UUID instead of illegal string. #979

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

Merged
merged 1 commit into from
Nov 19, 2018
Merged

Use resolved UUID instead of illegal string. #979

merged 1 commit into from
Nov 19, 2018

Conversation

crashdemons
Copy link
Contributor

@crashdemons crashdemons commented Nov 18, 2018

Reference #977 #978

PR #978 attempted to fix Issue #977 (Completablefuture typename was being used as the UUID string in NBT data), however after the null check, the uuid variable that was resolved is discarded instead of used in the NBT.

This change uses the resolved UUID in the NBT instead of the CompletableFuture type-string as the uuid.

In #977 I list some exceptions that occur when this string is read before adding this PR. After adding this PR, these don't seem to appear.

EDIT: double word

@CLAassistant
Copy link

CLAassistant commented Nov 18, 2018

CLA assistant check
All committers have signed the CLA.

crashdemons added a commit to crashdemons/PlayerHeads that referenced this pull request Nov 18, 2018
@Pr0methean Pr0methean merged commit be40956 into GlowstoneMC:dev Nov 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants