Steps to reproduce
Create a new world.
Make a nether portal and go in it.
Find a naturally generated fire in the nether.
Place wooden planks or leaves all around the fire.
Expected result
The planks and leaves catch fire.
Observed result
The planks and leaves do not catch fire.
Fires spawned in during world generation in the Nether do not spread fires.
Putting random tick on 100, go to the Nether Wastes biome and find a patch of fire.
Place a flammable block next to it.
Compare to a player-started fire.
It's a very minor issue, but it creates odd interactions
Linked issues
relates to 2
Attachments
Comments 2
Possibly the same underlying cause as MCPE-140396 and MCPE-101371: fire blocks seem to only update based on scheduling updates at they moment they are first created, and they do not actually receive random ticks or block updates from surrounding blocks.
Surprisingly, fire placed with the /setblock command spreads as expected. And blocks placed near fires after they are lit do catch fire, if the fires were lit by the player after world generation. So it seems fire has an attribute to spread or not that it acquires at the time it is created.
Is this still an issue in the latest version (1.17.10)? If so, can you please add it to the affected versions (or mention it if you are not the reporter).
This ticket will automatically reopen when you reply.