Entity/Block Persistence + Entity Despawnable #7564
+249
−0
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
Efnilite
requested changes
Feb 1, 2025
ShaneBeee
suggested changes
Feb 1, 2025
sovdeeth
added
the
enhancement
sovdeeth
requested changes
Feb 2, 2025
sovdeeth
requested changes
Feb 5, 2025
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.
Description
This PR aims to add the ability of changing the persistence of entities and blocks (leaves) and change if an entity should despawn when far away.
No test for
EntityUnloadbecause it requires a tick.Yes, I did try the JUnit thing, but was not viable as sometimes it succeeded and other times failed.
Granted if I did it correctly, look at the
Initial CommitTarget Minecraft Versions: any
Requirements: none
Related Issues: #7154