Fire does not directly ignite or spread to burn flammable objects. The attached image shows an attempt to burn leaves, vines, oak planks, scaffolding, a peeled oak log, a bamboo tree, and an oak sign with flames applied directly to objects or placed on adjacent blocks. I ran this test for 15 minutes IRL, and there was no effect to any of the objects.
After reviewing the bug database, I note that this issue has been patched for the Java edition, but I found no mention of a patch for the Bedrock Edition.
Note: I was forced to enter this bug as impacting the 1.16.0.60 Beta, but my system has not yet loaded that software, so I am still using the 1.16.0.59 version.
Attachments
Comments 11
migrated
Could not reproduce in 1.16.0.59, cannot currently reproduce in 1.16.0.60. Are you 100% sure that "Fire Spreads" and doFireTick were enabled?
Could not reproduce in 1.16.0.59, cannot currently reproduce in 1.16.0.60. Are you 100% sure that "Fire Spreads" and doFireTick were enabled?
"Fire Spreads" is definitely on. I am playing without cheats enabled, so I cannot access "doFireTick".
"Fire Spreads" is definitely on. I am playing without cheats enabled, so I cannot access "doFireTick".
Using a throwaway world, I set doFireTick = true, and fire spreads as it should. My question remains, however: why does this not work in the Vanilla no-cheats Survival mode. Is doFireTick set to false by default, and if so, why?
Are you able to upload a copy of the world?
If too big to attach to this site you can upload to something like OneDrive or Google Drive and share an open link.
Are you able to upload a copy of the world?
If too big to attach to this site you can upload to something like OneDrive or Google Drive and share an open link.
Apparently doFireTick globally sets the environment across worlds, because fire now spreads and burns properly in all of my worlds. I still don't know why it didn't work right originally, and I believe that is "bug-like" behavior - users should not have to change otherwise hidden environment variables to enable standard game functions. However, I appreciate your quick review of this issue. Thank you.
Apparently doFireTick globally sets the environment across worlds, because fire now spreads and burns properly in all of my worlds. I still don't know why it didn't work right originally, and I believe that is "bug-like" behavior - users should not have to change otherwise hidden environment variables to enable standard game functions. However, I appreciate your quick review of this issue. Thank you.