Description:
On snapshot 20w19a, the Nether generation changed once again. That's normal. But I noticed that Fortresses and Bastions generated in worlds created before 20w19a cannot be located when using the /locate command.
(Note: I just discovered that this bug also affect Overworld and End structures, not only Nether ones). (I'm putting the most explained case, the Fortresses & Bastions, but for the other structures they also need a fix).
The seed is: 8825242716498603998. Today, on the new coordinates, there are a big Soul Sand Valley and a big Basalt Deltas, where on old snapshots were Nether Wastes, Crimsom Forest, and a Basalt Deltas.
Also, on Bastions, Piglins don't generate correctly, and even spawn there Zombified Piglins. Extra: On 20w21a this was overlaped with a lowercase error, but on 20w22a now this bug returned exactly as it was before 20w21a.
How to reproduce:
1) Use seed 8825242716498603998 on 20w18a/20w17a (versions for the example).
2) At spawnpoint, create a Nether Portal. There should be a Crimsom Forest with a Fortress.
3) Modify the structure.
4) For the Bastions, just go to the coordinates of the photos. (This also applies for the Fortress).
5) Finally, charge the world on 20w21a/20w20b-a/20w19a.
Note: The same bug applies for every version that changed nether generation. Examples are opening a world of 20w06a on 20w15a or opening a 20w15a world on 20w17a.
PD: If you see some spanish parts, that's because I use spanish, but now I'm reporting a bug. Thanks for hearing. 🙂
Notes: 20w19a trigger the advancements.
20w20a-b trigger the advancements.
20w21a don't trigger the advancements.
20w22a trigger the advancements again.Â
Related issues
relates to
Attachments
Comments
migrated
galaxy_2alex
Please let us know if this issue still occurs in the next snapshot (20w21b or 20w22a).
supeika
I noticed that there is a new bug similar to this, and it's even worse. And yes, they still happen. Now also they don't trigger their advancements.
supeika
Please see it, because with the newest bug with structures (lowercase now is applied on commands) this would be forgotten. Also I say: This is a different bug, originated before 20w21a.
violine1101
Does this also affect nether fortresses generated in 1.15.2 (without opening the world in any snapshots prior to 20w22a)?
supeika
Obviously, every fortress generated before 20w19a is not recognized. Also, this bug persists on 20w22a. I just confirmed it.
supeika
That would be caused by the new generation changes. The nether changed 3 times, 4 if you count old nether.
I can say more information: If you open a 20w06a world on 20w15a or a 20w15a world on 20w17a (examples), this bug also applies for that cases.
supeika
You have fixed MC-184740, but not this bug. And I have to confirm that if that bug is fixed then this bug is a different bug than that bug.
migrated
This DOES affect my world as well (which is why I quit it) where Monument mobs (Guardians) and Wither Skellies dont spawn at all. Only blazes spawn from the spawner. And at the Monument, there were only the Boss Guardians
supeika
On my world, those mobs still spawn. But not correctly, I can confirm that because I've seen Fortress mobs spawned on those fortresses.
supeika
please see it, because we need to fix this problem
supeika
Seriously, at least mark this as confirmed, or at least leave a comment here. We need to prioritize the generation bugs. Those affect gameplay and make it less comfortable.
galaxy_2alex
It's unlikely this will be fixed, as in the final release, no worlds will be affected that weren't generated in the snapshots. Please note that the use of snapshots is not recommended for any persistent world, and can of course cause corruption or issues like this, issues which aren't always fixed in a way that automatically fixes it for previous snapshot worlds.
supeika
Yeah, thanks anyway for hearing.