MC-190285"bedrock_roof_position" tag number does not represent height, but height modifier
The "bedrock_roof_position" tag for custom dimensions is calculated improperly.
Issue:
When setting the "bedrock_roof_position" to 30, the bedrock roof moves down 30 blocks from y=127 (moving it to y=97). The bedrock roof can only be moved down because of this. The range is stated to be -20..X, however placing a negative number to move the roof up makes it not generate at all.
Expected Behavior:
Setting "bedrock_roof_position": 27 would set the bedrock height to y=27, OR set it 27 blocks from the top of the world (0 being y=255, 27 being y=228), OR have a range of -127..128 to move it to y=0 and y=255
LowCreated Issue:
Custom dimension bedrock roof position not calculated correctly
The "bedrock_roof_position" tag for custom dimensions is calculated improperly.
Issue:
When setting the "bedrock_roof_position" to 30, the bedrock roof moves down 30 blocks from y=127 (moving it to y=97). The bedrock roof can only be moved down because of this. The range is stated to be -20..X, however placing a negative number to move the roof up makes it not generate at all.Expected Behavior:
Setting "bedrock_roof_position": 27 would set the bedrock height to y=27, OR set it 27 blocks from the top of the world (0 being y=255, 27 being y=228), OR have a range of -127..128 to move it to y=0 and y=255
Roof 27.zip
![[Mod] violine1101](../../../data/avatars/users/92858.png){kind=small}
Custom dimensionbedrockroofpositionnot calculated correctly"bedrock_roof_position" tag number does not represent height, but height modifier
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Mojang] slicedlime](../../../data/assets/gravatar/slicedlime.jpeg){kind=small}
This is actually because you need to modify the "height" value under "generator" > "settings". The roof is calculated based on this height value, not the world build limit. If you leave the height at 128, the roof will calculate its position starting at y=128.
ah, that explains that issue..
This bug still present in 1.16.1?
Rajat explained it's linked to the height tag. If that's intended, than no. If it should be set without anything modifying it, than yes it's still an issue. I'm guessing it's intended though?