Klinbee
- Quidvio
- JIRAUSER702308
- Europe/Stockholm
- Yes
- No
MC-263370
The pack.png for the same data pack no longer works in 1.20.4 when it did in 1.20.2.
I wouldn't be surprised if something is wrong with the image, but that doesn't really explain how it works in 1.20.2 but not in 1.20.4 (it also doesn't work in 1.20.3 and 23w51b)
The pack.png for the same data pack no longer works in 1.20.4 when it did in 1.20.2.
I wouldn't be surprised if something is wrong with the image, but that doesn't really explain how it works in 1.20.2 but not in 1.20.4 (it also doesn't work in 1.20.3 and 23w51b)
image-2024-01-03-21-25-42-601.png
The pack.png for the same data pack no longer works in 1.20.4 when it did in 1.20.2.
I wouldn't be surprised if something is wrong with the image, but that doesn't really explain how it works in 1.20.2 but not in 1.20.4 (it also doesn't work in 1.20.3 and 23w51b)
image-2024-01-03-21-25-42-601.pngThe pack.png for the same data pack no longer works in 1.20.4 when it did in 1.20.2.
I wouldn't be surprised if something is wrong with the image, but that doesn't really explain how it works in 1.20.2 but not in 1.20.4 (it also doesn't work in 1.20.3 and 23w51b)
screenshot-1.png
I recently launched a 21w44a world and also experienced this.
My mistake, but I think this is a duplicated of
MC-239444I will be more careful next time in searching ahead of time... slipped my mind.
Can confirm for 1.20 and 1.20.1 rc1. Unfortunately I made a duplicate post of this because I forgot to check first...
Thanks, I tried searching but could not find any. Didn't match any keywords with that post while searching.
I've found out the reason the issue occurs.
Regular taiga biomes generate at [-1.0,-0.450] temperature values with [0.1,1.0] humidity, but frozen rivers, snowy beaches, frozen oceans, and deep frozen oceans also generate in this range, despite being surrounded by non-snowy taigas.
A solution would be to change the frozen rivers to rivers, snowy beaches to beaches, frozen oceans to cold oceans, and deep frozen oceans to deep cold oceans in the [-1.0,-0.450] temperature and [0.1,1.0] humidity range.
I made a datapack using a useful website to test this.
Before:
After:
Seed: 6375681940372423679
TP: /execute in minecraft:overworld run tp @s 110.99 78.71 1445.22 112.01 16.22
I would attach the datapack, but I don't know if I should or not, so I'm just going to play it safe and not do that. I'm sure Mojang can do it themself if they really want to. If it is requested and allowed though I will attach it to a separate comment.
Also tested in 1.20.1 and two mansions I went to had the room and generated with them.EDIT: It may have been a mod that was fixing it....
Can confirm for 1.20.1. Also important to mention that the reason behind this bug is that the jigsaw in the file says "buidling_entrance" instead of "building_entrance".
It's probably to do with resource pack version 21's png change, which means it is intended and my image is just messed up. (I was told nearly immediately after I posted this even though I've been looking at snapshots for a while... sorry about that.)
Jiingy,
I have checked the code and confirmed that savanna_plateau biomes are the only savanna biomes that spawn wolves. The spawning position for the wolves was in a savanna_plateau biome, but because these biomes border close to each other, when the wolves spawned, they spawned in the savanna biome, and thus took the coat of the savanna biome, which makes them look like normal Pale Wolves instead of spotted wolves.
Stay strong SeaOfPixels, one day they'll give it experience... I've been watching this post for the past 9 months.
Can confirm for 1.20.6
Can confirm in 1.20.6, but this never actually happens in game during natural generation (source: the combined several million hours of the minecraft speedrunning community), only when you use the structure blocks. My guess is the non-rampart section of the stables bastion prevents it from generating in any other orientation.
Can confirm for 1.20.6
Can confirm in 1.20.6, it is due to the `patch_soul_fire` configured_feature file, which specifies it can only be placed on top of soul soil.
{
{ "Name": "minecraft:soul_fire" }"type": "minecraft:random_patch",
"config": {
"tries": 96,
"xz_spread": 7,
"y_spread": 3,
"feature": {
"feature": {
"type": "minecraft:simple_block",
"config": {
"to_place": {
"type": "minecraft:simple_state_provider",
"state":
}
{ "type": "minecraft:matching_blocks", "blocks": "minecraft:air" }}
},
"placement": [
{
"type": "minecraft:block_predicate_filter",
"predicate": {
"type": "minecraft:all_of",
"predicates": [
,
{ "type": "minecraft:matching_blocks", "offset": [ 0, -1, 0 ], "blocks": "minecraft:soul_soil" }]
}
}
]
}
}
}
This seems to be fixed in at least 1.20.6 and could be fixed sooner. I may be misunderstanding this though.
Can confirm in 1.20.6 omg I can't believe you can softlock yourself
Can confirm in 1.20.6
Not in 1.20.6
Can confirm in 1.20.6
In 1.20.6 this still acts like it is successful, but the item no longer has the enchant glint or desc. So it is partially fixed.
Can confirm in 1.20.6. The reason this occurs is because both bastions and delta features are placed on the surface_structures step in world generation. If bastions were directly placed after, then the deltas would not spawn inside of them.
This issue is very important for custom worldgen now that
MC-226687has been resolved. Floating Islands-style custom worldgen packs usually set sea-level to -64 to remove the lava at the bottom of the world. But now, doing this results in a cascade of unintended side-effects, like preventing aquatic mobs from spawning above the bottom of the world.