Nova Fuhrmann
- wostramock
- wostramock
- Europe/Stockholm
- Yes
- No
MC-271970
Normal
Dimensional Padding doesn't stop structures from generatebeyond bedrock ceilingDimensional Padding doesn't stop structures from generating beyond bedrock ceiling
How to recreate:
- Load in the Attatched padding_test datapack in a new world
- Go into the nether
- Execute "/locate structure padding_test:padding_test"
- Teleport to the location of the structure
What you expect to happen:
The structure is suposed to stop generating 10 blocks away from the bedrock boundries on the bottom of the nether and top of the netherWhat happens:
Structuregenerates beyondNetherceilingDimensional Padding, as used by trial_chamber, are suposed to stop the structure from generating the valiues amound away from the dimensionals boundries. This does not work for Structures generated by datapacks inside the nether as the bedrock ceiling is at Y128 while dimensional boundry is at Y256
How to recreate:
- Load in the Attatched padding_test datapack in a new world
- Go into the nether
- Execute "/locate structure padding_test:padding_test"
- Teleport to the location of the structure
What you expect to happen:
The structure is suposed to stop generating 10 blocks away from the bedrock boundries on the bottom of the nether and top of the netherWhat happens:
Structure stops 10 blocks from the Nether bottom
Structure generates beyond Nether ceilingDimensional Padding, as used by trial_chamber, are suposed to stop the structure from generating the valiues amound away from the dimensionals boundries. This does not work for Structures generated by datapacks inside the nether as the bedrock ceiling is at Y128 while dimensional boundry is at Y256
Trial Spawner Forget their designated mob when placed by player out of creative mode, asigned by spawn eggs
Trial Spawner Forget their designated mob when placed by player out of creative mode, assigned by spawn eggs
have the same problem with 1.10-pre-1, 1.10-pre-2 and the official 1.10 version.
Curently this issue can be worked around by using commands on the placed block such as "/data modify block ~ ~-1 ~ normal_config.spawn_potentials set value [\{data:{entity:{id:"minecraft:spider"}},weight:1}]". this bug is spawn egg specific