mojira.dev
MC-210943

Fire caused by lava can appear out of nowhere by placing a non-flammable block on above the lava

The bug

If you place any non-flammable block above the lava by 1 block, and if there is a block flammable by lava very close to the lava, fire will still appear, nevertheless.

Misc (Not related to the bug itself.)

  • I name this bug "The Flamethrower Block", due to the fact that it causes a fire if you place something flammable by lava very close to it.

What I excepted to happen

By placing an non-flammable block above the lava by 1 block, and if there is a block flammable by lava very close to the lava, no fire will appear.

What really happens

By doing the same procedure, fire still appears. This happens if the block touches the non-flammable block, or is 1 block away from the non-flammable block.

How to reproduce (In Steps)

  1. Get a lava bucket, and a non-flammable block.

  2. Dig 1 block, and place the lava here.

  3. Place 2 blocks. The first block must be broken. The second block should be directly be above the lava.

    • First, place a block. Second, fill the hole with lava. Third, Place the second block. This must be directly above the lava by exactly 1 block. Last, Break the first block and go to step 4

  4. Place an block flammable by lava, near to the non-flammable block
    ❌  The flammable block will catch fire, with the fire no-clipping through the non-flammable block. Changing the Mipmap Level will have no effect on the bug. However, if it rains, the process of burning will take longer.

Linked issues

Attachments

Comments 3

Corrections

  1. Making the flammable block catch fire takes a long time (gamerule randomTickSpeed)

  1. Has a different procedure for a block increase.

    1. Dig out 2 blocks horizontally, to the non-air block.

    2. Fill in the other end of the hole with lava

    3. Place the block, closing the tunnel.

  2.  If you don't want to wait, set gamerule randomTickSpeed to 1000.

❌  Has the same effect and speed of the original procedure.

As stated above, this report appears to be a duplicate of MC-144371, which was later resolved as, "Works As Intended". The "issue" that you are experiencing works how the developers intended it to. Please see the parent ticket for further details.

5183609

(Unassigned)

Unconfirmed

20w51a

Retrieved