mojira.dev
MC-187358

Worlds generated in 1.16-pre1 do not have their world generation settings saved correctly, causing chunk errors

When rejoining a world created in this pre-release, loading new chunks cuts off pre-existing chunks.

Linked issues

Attachments

Comments 6

It may only affect worlds created in 1.16 pre1, more testing required.

It seems to only be worlds created in this pre-release, as loading up a 1.15.2 world or a 20w22a world in this pre-release causes the world to generate chunks normally. I rejoined both the 1.15.2 and 20w22a worlds multiple times and no chunks seemed to be cut off.

It's just that previous minecraft terrain engines and the current one don't go well, and start to override each other I think.

I found that whenever you reload a world (exit the world and join back) the new chunks are completely different from the previous ones. I had a little fun and kept reloading my world.

I have just experimented with this bug and found that it is in fact just the worlds being generated by the 1.16-pre1 snapshot that has this issue. It appears that the chunk generation settings are different every time loading the world is loaded again

world generated in 2022a snapshot

[media]

world generated in pre1 snapshot

[media]

 

It appears that maybe the settings aren't being properly saved and garbage memory is being used for those seed values after loading in the world again and could explain why the seed is different for each new instance of the world loading, but the chunks generate consistently within the same instance of the world being loaded.

Chris M

(Unassigned)

Confirmed

Very Important

World generation

1.16 Pre-release 1

1.16 Pre-release 2

Retrieved