mojira.dev
MC-279464

Fire placed with /setblock doesn't tick/burn out

Setting a block via setblock or fill to fire (regardless of age) neither spreads or burns out. 

Light a block on fire with flint and steel burns out as normal.

There does not seem to be any difference block states between manually setting a block on fire and setblock ~ ~ ~ fire.

Saving and closing world does not make the setblock'ed fire spread/burn out.

If I dump the region file for the specific chunk with a flint&steel fire and a setblock fire, the setblock fire doesn't have a block_ticks entry, whereas the one placed with flint and steel does;  

"block_ticks": [ { "i": "minecraft:fire", "p": 0, "t": 39, "x": 435, "y": 118, "z": -26 } ],

Comments 3

can't confirm in 25w04a

@B4dAtMC: How did you test? Any fire placed with /setblock or /fill is forever here in the snapshots.

 

/setblock ~ ~ ~2 fire
/tick sprint 1d

fire is still there.

knirch

gnembon

1362211

Community Consensus

Expansion A

Important

Block states, Commands

25w02a, 25w04a, 25w05a

25w06a

Retrieved