Fix Xaeros culling regression - #101
Merged
Merged
Conversation
Algent
added
the
Bug Fix
Caedis
approved these changes
Jul 18, 2026
This file contains hidden or 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
2 participants
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.
Summary
Fixes GTNewHorizons/GT-New-Horizons-Modpack#25941
Regression caused by my PR #89
Change it back so that the culling for journeymap-legacy doesn't apply to Xaeros since it's causing issue.
Cherry picked from my JM6 support branch, quickly making a PR for it since someone ran into the issue and I already had code ready.
Tested full pack on JM5 and Xaeros, doesn't seem to cause additional issues.
Checklist