Fix veins differing between server and clients #57
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.
Fixes https://discord.com/channels/181078474394566657/522098956491030558/1286984717304074354
The changes made to vein caching here caused the id's that veins get assigned to differ between old and newly generated caches.
To prevent any future mishaps we just send the vein name in the prospecting packet instead which can't ever differ between server & client.
Confirmed working https://discord.com/channels/181078474394566657/522098956491030558/1287024258391871518
Closes GTNewHorizons/GT-New-Horizons-Modpack#17412