Structures from old worlds don't regenerate if opened with 1.13 standalone client/server
The bug
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
How to reproduce
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- Teleport to about 5256.0 65.0 -248.0
- Observe guardians frolicking in the autumn mist
- Close 1.12.2
- Open 1.13 and enter the world
- Fly up to Y190 to let the existing hostiles despawn
- Descend to Y60
- Observer no more guardians to spawn
- Confirm the observation typing /kill @e[type=minecraft:guardian]
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
Linked Issues
is duplicated by4
MC-127119Structures misbehaving from previous versions to new versionsDuplicateMC-127376Guardians not spawning.in old world and new world generations. DuplicateMC-127396Guardian's do not spawn in farms. DuplicateMC-129626when switching world from 18w16 to 18w20 guardian farm doessent spawn guardians anymoreDuplicate
![[Mojang] Gnembon](../../../data/avatars/users/93709.png){kind=small}
Created Issue:
Structures from old worlds don't regenerate if opened with 1.13 standalone client/server
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
Steps to reproduce:
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- teleport to about 5256.0 65.0 -248.0
- observe guardians frolicking in the autumn mist
- close 1.12.2
- open 1.13 and enter the world
- fly up to Y190 to let the existing hostiles despawn
- descend to Y60
- observer no more guardians to spawn
- confirm the observation typing /kill @e[type:minecraft:guardian]
- sad panda.
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
PS. Apologies for cutting off their fins and tails - FPS gets 3 times better without them
乁( ⁰͡ Ĺ̯ ⁰͡ ) ㄏEnvironment
Windows Java
Attachments2
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
Steps to reproduce:
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- teleport to about 5256.0 65.0 -248.0
- observe guardians frolicking in the autumn mist
- close 1.12.2
- open 1.13 and enter the world
- fly up to Y190 to let the existing hostiles despawn
- descend to Y60
- observer no more guardians to spawn
- confirm the observation typing /kill @e[type
:minecraft:guardian]- sad panda.
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
PS. Apologies for cutting off their fins and tails - FPS gets 3 times better without them
乁( ⁰͡ Ĺ̯ ⁰͡ ) ㄏInformation about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
Steps to reproduce:
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- teleport to about 5256.0 65.0 -248.0
- observe guardians frolicking in the autumn mist
- close 1.12.2
- open 1.13 and enter the world
- fly up to Y190 to let the existing hostiles despawn
- descend to Y60
- observer no more guardians to spawn
- confirm the observation typing /kill @e[type=minecraft:guardian]
- sad panda.
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
PS. Apologies for cutting off their fins and tails - FPS gets 3 times better without them
乁( ⁰͡ Ĺ̯ ⁰͡ ) ㄏ
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
![[Mod] redstonehelper](../../../data/avatars/users/10122.svg){kind=small}
relates to
relates to
MC-125192
![[Mod] Michael Wobst](../../../data/avatars/users/37868.png){kind=small}
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
Steps to reproduce:
- Run 1.12.2 client, create a new world, seed 2791111690993685248
teleport to about 5256.0 65.0 -248.0observe guardians frolicking in the autumn mistclose 1.12.2open 1.13 and enter the worldfly up to Y190 to let the existing hostiles despawndescend to Y60observer no more guardians to spawnconfirm the observation typing /kill @e[type=minecraft:guardian]- sad panda.
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
PS. Apologies for cutting off their fins and tails - FPS gets 3 times better without them
乁( ⁰͡ Ĺ̯ ⁰͡ ) ㄏThe bug
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
How to reproduce
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- Teleport to about 5256.0 65.0 -248.0
- Observe guardians frolicking in the autumn mist
- Close 1.12.2
- Open 1.13 and enter the world
- Fly up to Y190 to let the existing hostiles despawn
- Descend to Y60
- Observer no more guardians to spawn
- Confirm the observation typing /kill @e[type=minecraft:guardian]
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
Windows Java
The bug
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
How to reproduce
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- Teleport to about 5256.0 65.0 -248.0
- Observe guardians frolicking in the autumn mist
- Close 1.12.2
- Open 1.13 and enter the world
- Fly up to Y190 to let the existing hostiles despawn
- Descend to Y60
- Observer no more guardians to spawn
- Confirm the observation typing
/kill @e[type=minecraft:guardian]The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
The bug
Information about previous structures (generated in the world) saved in data/*.dat files seem not to load when a 1.12.2 and below world is opened with 1.13 (tested on client and server).
How to reproduce
- Run 1.12.2 client, create a new world, seed 2791111690993685248
- Teleport to about 5256.0 65.0 -248.0
- Observe guardians frolicking in the autumn mist
- Close 1.12.2
- Open 1.13 and enter the world
- Fly up to Y190 to let the existing hostiles despawn
- Descend to Y60
- Observer no more guardians to spawn
- Confirm the observation typing /kill @e[type=minecraft:guardian]
The ability to store previously generated structures, even if the newer world generation/format had different opinion about it, allowed for players with stubborn personalities to continue playing in their old and dingy worlds even in the newest and shiniest of Minecraft versions.
is duplicated by
is duplicated by
is duplicated by
![[Mod] Neko](../../../data/avatars/users/92901.png){kind=small}
is duplicated by
is duplicated by
![[Mojang] Nathan Adams](../../../data/assets/gravatar/dinnerbone.png){kind=small}
ProfMobius (Thomas Guimbretiere)![[Mod] Les3awe](../../../data/avatars/users/79847.png){kind=small}
is duplicated by
region refernces 1.PNGrelates to
An interesting note is if you upgrade your world from 1.12 to 18w21a and then 1.13, the structures are fine. The issue is upgrading directly between official releases.
I posted an issue that apparently got linked to this one, and it still exists in 18w30b.
![[Helper] Michał](../../../data/avatars/users/43368.png){kind=small}
Same issue with 18w07c. Loaded 1.12.2 word into snapshot to see new mechanics and how they would affect farms. No guardians spawn in existing guardian farm/temple. Tons of hostile mobs spawning though, so I am assuming the game no longer recognizes this as an ocean monument.
I added screenshots what happens if you create a world with said seed and tp to said location for each version separately (18w07c and 1.12.2). 18w07c didn't create Monument.dat file yet the monument generated when teleported to this place. Did the location of saved structures changed?
Oh. This should be updated with the more recent versions of 1.13 snapshots. My search, https://bugs.mojang.com/browse/MC-126943?jql=affectedVersion%20in%20(%22Minecraft%2018w10c%22%2C%20%22Minecraft%2018w10d%22)%20AND%20text%20~%20%22structure%22 yielded no results and the versions listed here are not selectable currently in the search options. This happens in 18w10c & 18w10d currently.
Added. It is possible to search for older versions, though, but only on the advanced search; see
WEB-929.It's generally better to not assume tickets are up to date, limiting the ticket creation range to the last X weeks usually works for new issues.
To add to this issue, as of 18w15a, witch huts generated in a 1.12.2 world are no longer spawning only witches after conversion (they are spawning other mobs like creepers, skeletons, etc). New witch huts generated by 18w15a's world generation function properly since that was resolved in
MC-125141. It's only the converted ones that are broken.Just loaded my 1.12 world into the latest snapshot, 18w20c and the witch hut I had been just setting up is no longer spawning witches. I used the /locate witch_hut command and it did locate and point to the witch hut so it does see it. However it no longer functions.
It seems like it isn't populating the Swamp_Hut entry in the References folder of the chunk in the region file. It's only populating the Swamp_Hut entries under Starts. We didn't have that entry in the Temple.dat previously. Any chance a dev could help us figure out how that References entry is calculated so we can edit the region files to fix it until this is resolved?
Hey almightyzing. Yep that is the problem, or one of them. Sometimes the "Swamp_Hut" tag is not generated in the "Starts" tag.
The value of the "Swamp_Hut" tag are the chunk coordinates from the witch hut merged into one integer. Click" Hex" in the NBTExplorer then you'll see what I mean.
So 07 00 00 00 00 00 00 00 and 64 00 00 00 00 00 00 00 would give 07 00 00 00 64 00 00 00.
Here is a twitter link where I explain how to convert old witch hut structures to the 1.13 snapshots.
Twitter Thread
Unarybit, mind to attach the pictures here to this ticket ?
Twitter is no bugtracker...
Sorry was only meant for helping out. I can edit my post tomorrow, it's getting late here <3
The structures do not generate completely because when converting from old worlds to the snapshots the value for the reference to the start chunk of the structure is not created. In case of a larger structure such as an ocean monument it applies to all chunks where the structure is included.
Sometimes the "structure tag" is corrupt or do not generate in the start chunk of the structure.