Adds 'getEntityData' to WorldReader #240
Merged
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
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.
This commit adds (if I haven't messed anything up) the ability to also pull entity files using the WorldReader. This re-uses the overwhelming bulk of the code from the region files, so I have merged the functionality into a publically exposed function to read
.mcafiles calledgetMCAData.I have not added a EntityDataFrame (EntityRegionDataFrame?) much like there is a RegionDataFrame - I'm not super familiar with the entitiy data structure so I didn't want to get this wrong.
I considered making the
getMCADatafunction private, but I considered if they add any future.mcafiles having this public would allow a way for people to read it while the repo gets updated.