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

fix: origin world can be unknown while knowing location #5793

Closed
wants to merge 1 commit into from

Conversation

Proximyst
Copy link
Contributor

If there is no world anymore (e.g. deleting the world an entity was
spawned in), it will be nulled while the location is still technically
legal.

I'm unsure whether this should rather keep the UUID in memory,
as that would be a very acceptable fix and would even retain the
origin world in these cases. That being said, it would be useless
information.

Fixes #5791.

@Proximyst Proximyst requested review from a team as code owners June 10, 2021 18:35
@kennytv
Copy link
Member

kennytv commented Jun 10, 2021

Plz store the uuid in a field to keep even if the world is poof

We will now store the world ID. It may not be used if the entity is
loaded before the world in question is, but it might be used later on,
should the entity come after the world.

Signed-off-by: Mariell Hoversholm <proximyst@proximyst.com>
@Diezel0468
Copy link

how to solve the problem in the end?

@Proximyst
Copy link
Contributor Author

Update

@electronicboy
Copy link
Member

This was replaced by #5846

@kennytv kennytv deleted the fix-origin-world-npe branch August 21, 2021 15:23
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.

Error Saving entity NBT
4 participants