Repository navigation
Fix vanilla height limits - #160
Merged
RecursivePineapple merged 8 commits intoOct 31, 2026
Merged
Conversation
RecursivePineapple
approved these changes
Oct 31, 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
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 several vanilla mechanics that still assumed the world ends at Y0 and Y255
/spawnpointand/setworldspawn: accept an explicit Y anywhere in the world's height range/spreadplayers: where the target's terrain is loaded, it finds the surface at any height and rejects lava,fire and blocked spots, with a bounded search from the column's top through loaded cubes only. Where the column,
its surface or the space above it is not loaded, the vanilla search runs as before:
it still lands on unexplored terrain like now (Y 2-257), and there it does not reject lava or fire, as now.
of them like vanilla does above Y 0.
Checklist