[MC-195340] Some structures that were generated before 1.16 can't be located using /locate

There is a loss of data when opening a 1.15.2 world in a version at (or past) 1.16.

Steps to Reproduce:

Create a new world in a version before 1.16 with structures enabled
Enter the nether
Locate a fortress structure:
```
/locate structure minecraft:fortress
```
Teleport to it using the command provided
Leave the world, and join in the latest version
Repeat step 3

The command will locate a fortress which is further away, despite the player standing on top of (or near) a fortress.

Linked issues

relates to 1

MC-194300 Structure data of pillager outposts, villages, and bastion remnants get lost when updating a world to 20w28a Resolved

Attachments

Comments 3

j_p_smith 2020-07-18T18:25:57Z

Can confirm, although blazes and wither skeletons are still spawning in previously generated fortresses, and the advancement "A Terrible Fortress" is still granted upon entering, so this may just be an issue with the /locate command.

j_p_smith 2020-07-19T09:45:07Z

This is actually MC-184311, which was closed under the assumption that Nether fortresses generated in 1.15.2 were not affected.

[Mod] Jingy 2024-11-18T01:40:09Z

In snapshot 24w46a, the fortress is still not recognized after upgrading from a world created prior to 1.16.

In my test, the /locate command finds a further away fortress, ignoring the one I am on top of:

[media]