mojira.dev
MCPE-97295

Nether Fortresses Not Generating Blaze Spawners

Update from @unknown:
The reproduction of this bug is equivalent to the reproduction of MCPE-141499 and MCPE-23416.

  1. Player comes within render distance + 2 chunks of the structure, but not within simulation distance. This triggers the chunk to generate because it contains tile entities.

  2. Player moves away so that the chunk is no longer within render distance + 2 chunks.

  3. During autosaving, the player comes within simulation distance of the chunk.

I am not 100% sure that step (2) is necessary, but I think it is. My theory is that because the chunk was outside of render distance in step (2), it only loads block data when it comes back into render distance in step (3), and then gets ticked before it can load entity data because the game is busy saving other chunks.

The following more precise steps work in 1.17.32 without the Caves & Cliffs experimental generation. In future versions or with the experimental toggle enabled, you will need to use a different seed and location.

Steps to reproduce

  1. Set render distance to 8 and turn on the autosave icon in video settings.

  2. Create a world with seed 1212557532, simulation distance 6, and coordinates enabled.

  3. After you spawn, /tp 800 ~ ~, make a nether portal, and enter the nether.

  4. In the nether, /tp 95 ~ 216

  5. Fly east to X = 115 and flying around the area, never going to X < 115 until the auto-save icon appears.

  6. When the auto-save icon comes on (showing that autosave is happening), due west (-X), staying near Z = 216, until you get to X = -60.

  7. /tp -60 78 216.

Expected result

There is a blaze spawner.

Observed result

No blaze spawner.


I came across two rooms that should've generated blaze spawners, but they weren't there. That was the closest one to spawn (-80 ~ 192). The second fortress (736 ~ -320) luckily had a single spawner room with a spawner. The coordinates of each of the spawners is in the images, and here's the seed; 1212557532. Also sorry about the poor image quality.

Linked issues

Attachments

Comments 10

GoldenHelmet

I loaded the seed and found blaze spawners at the coordinates. Is there any chance another player had destroyed the spawners in your world?

Auldrick

This report is being closed pending your response. It will reopen automatically when you reply.

migrated

No other players or myself destroyed them as it was a single player survival world and was like that upon discovering it. I don't have the seeds since the worlds have been deleted but this isn't the first world that this has happened in.

Also sorry for the late response.

migrated

Could not reproduce, however, I tested on win10 so this maybe is a platform issue... Is this still reproducing?

migrated

Not that I'm aware of no. I haven't done much testing in newer versions but I'll see if it's still an issue and get back to you.

v-baslod

Did you have any success reproducing this issue?

This ticket will automatically reopen when you reply.

migrated

It still isn't fixed in my world.

GoldenHelmet

Brian Quimby: when you say it isn't fixed in your world, that sounds like you are expecting a missing blaze spawner to generate in an already-generated fortress. That isn't going to happen, even if this bug gets fixed, because Mojang has no way of knowing whether someone intentionally destroyed a spawner or it failed to generate in the first place. A fix to this bug would only mean that newly-generated blaze spawner platforms never fail to generate the spawner.

migrated

This is happening for me too.

Can recreate like this ...

 Create Bedrock Realm with seed...

-1384570475

Go to 468, 77, -62 and spawner is missing.

Create creative single player with same seed and at same location spawner is there.

Hope this helps, I am playing on iOS but obviously it is a realm so I don’t know how much the platform matters.

Mattus

 

 

silentwisperer

this affects 1.18+
Its also affecting regular dungeons in the overworld, and mineshafts. It's likely affecting any structure that has a spawner.

migrated

(Unassigned)

635098

Confirmed

Multiple

10.1.0

1.12.1, 1.16.1, 1.16.20, 1.17.30, 1.17.32, 1.17.41 Hotfix, 1.18.2 Hotfix

1.18.10.27 Beta, 1.18.10

Retrieved