mojira.dev
MC-188086

Decorations and amethyst geodes get cut off on full chunk boundaries upon relog

Decorations such as trees, huge mushrooms, huge crimson/warped fungi, and amethyst geodes will generate cut off on chunk boundaries upon exiting the game.

To reproduce:

  1. Set render distance to 12.

  2. Enter the seed 5878760421836343227.

  3. Go into "Game Rules" and set "Respawn Location Radius" to 0 (to prevent chunks from generating differently).

  4. Create the world with the above render distance, seed, and gamerule changes.

  5. When spawning into the world, don't move. Exit the world and reenter.

  6. Use the following command to see decorations getting cut off by a chunk boundary:

    /tp @p -96.0 80 -105 -180 0

If it somehow doesn't work, look around, and there should be broken decorations no more than 32 blocks from where you teleported.

Related issues

Attachments

Comments

migrated
[media][media][media][media]
numeritos

Affects 1.16 pre3

migrated

Can confirm this for 20w51a.

gaspoweredpick

This can also happen with amethyst geodes. I know that the conditions required to cut off a geode are the same as other decorations because above the geode, there were trees that got cut off at the exact same chunk border.

migrated

This affects all worldgen features, including ores and stone blobs. It happens because they are placed once, and they can't affect unloaded chunks.

migrated

Chunks appear to be generated+decorated twice on exit/reload, leading to cut off resources, have been able to confirm via debugging, see: https://github.com/MinecraftForge/MinecraftForge/issues/7766#issuecomment-841545896.

MC-224729 seems like the likely culprit and has more detail.

Brevort

I found this bug in a world generating in 1.17-pre3.

migrated

Also in 21w39a

ampolive

Can confirm in 21w40a.

ampolive

Can confirm in 21w41a.

gaspoweredpick

I've tested it many times in 1.18.2 Release Candidate 1 and 1.18.2, and I was unable to reproduce for those versions. Can anybody else confirm? Note that the current steps to reproduce are outdated, so my method was to exit the game near a jungle, relog, and search for the issue at newly loaded chunks.

clamlol

I likewise wasn't able to reproduce this in 1.18.2.

gaspoweredpick

(Unassigned)

Confirmed

Normal

World generation

1.15.2, 1.16 Pre-release 2, 1.16 Pre-release 5, 1.16 Pre-release 8, 1.16 Release Candidate 1, ..., 21w43a, 21w44a, 1.18, 1.18.1, 1.18.2 Pre-release 1

1.18.2 Release Candidate 1

Retrieved