[MCPE-11594] Can't put out fire by tap and hold in Survival (but can in Creative) Created: 14/Nov/15  Updated: 23/Oct/16  Resolved: 07/Oct/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.13.0 Beta 1, 0.13.0 Beta 5, 0.13.0, 0.15.1 Beta 1, 0.15.1, 0.15.2, 0.15.3, 0.15.4, 0.15.8, 0.15.90.7, 0.15.9, 0.15.10
Fix Version/s: 0.15.90.8

Type: Bug
Reporter: Crazy Dude
Resolution: Fixed Votes: 22
Labels: None

Issue Links:
Duplicate
is duplicated by MCPE-9627 Fire has no hitbox Resolved
is duplicated by MCPE-11840 Fire Cant be Punched out Resolved
is duplicated by MCPE-12042 I can`t put out the fire without brea... Resolved
is duplicated by MCPE-12050 Fire Resolved
is duplicated by MCPE-14786 Can't extinguish the fire Resolved
is duplicated by MCPE-15489 Cannot put out fire in the nether in ... Resolved
is duplicated by MCPE-15868 can't put out fire Resolved
is duplicated by MCPE-15966 Cannot extinguish fire in the Nether ... Resolved
is duplicated by MCPE-16551 Cant set fire off with hand in survival Resolved
is duplicated by MCPE-17370 Flames don't turn off when "pressed" ... Resolved
Relates
relates to MCPE-15569 Breaking an ice or packed ice block b... Resolved
Game Mode: Survival
Confirmation Status: Confirmed
Platform: Tablet - Android - Samsung Galaxy Tab 3
CHK:

 Description   

Usually, if you press and hold you are able to extinguish fire. But on the 0.13.0 builds, it won't work on survival.

Update:
As of 0.15.2, this bug affects Android users playing single player or as LAN host. Android Clients connected via LAN are not affected.

Update by nighter
This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided).
Please avoid duplicate comments. Post only NEW information regarding this bug.



 Comments   
Comment by Mat Cooke [ 23/Oct/16 ]

Hi Neil,

Yes takes about 0.5 seconds hold on the block!

Comment by Neil Gooding [ 23/Oct/16 ]

Sorry, my mistake, it is fixed, it just feels different to use somehow... longer press perhaps? Cheers.

Comment by Neil Gooding [ 22/Oct/16 ]

Still not fixed in v 16.0.5, update from Google Play - what gives?

Comment by rplatham [ 08/Oct/16 ]

Basically, anyone who is not a beta tester in android will have to wait for an update to include this fix. It has been fixed, but hasn't rolled out to all versions yet.

Comment by [Mojang] Mega_Spud (Jay Wells) [ 08/Oct/16 ]

lotharmat - This issue is fixed in the latest 0.16 beta update (build number 0.15.90.8, available on android to beta testers).

Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki

Comment by Mat Cooke [ 08/Oct/16 ]

With respect Rodriguez,

It is not fixed in 0.15.10.

Please mark as unresolved. It is still broken.

Comment by Rodrigo [ 07/Oct/16 ]

Fixed in 0.15.90.8

Comment by [Mojang] Adrian Östergård [ 07/Oct/16 ]

Please note that this is not a discussion forum. Post only NEW information regarding this bug. This bug has been reported to our internal bug tracker for further testing and a fix. It is scheduled to be fixed in one of the future updates (no specific date can be provided). .

Comment by Mat Cooke [ 04/Oct/16 ]

Please add 0.15.10 and please, please, please can you give us an estimate of when this hyper-annoying bug (sorry.. Regression) will be fixed.

Comment by Mat Cooke [ 22/Sep/16 ]

Please add 0.15.9 to the Affected versions....

Comment by Mat Cooke [ 16/Sep/16 ]

Please add 0.15.8 to the Affected versions.

Is anyone actually working on this regression of functionality? 8 sub-versions later and still broken.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 16/Sep/16 ]

Yes, it is reported. Please post only bug relevant comments in this bug tracker.

Comment by Neil Gooding [ 16/Sep/16 ]

@[Mojang] MissMarzenia (Aleksandra Zajac)

I'm sorry, but I think you're mistaken.

You DID comment it was reported for testing - in V13

In v14 it was subsequently fixed.

In v15 the fault reappeared and this bug was re-opened.

Since then, you have not told us you have reported this for testing in V15.

Has this been reported for testing in V15?

Thanks in anticipation.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 04/Aug/16 ]

As mentioned before multiple times, we do not assign bugs as we do not use JIRA as our internal tracker. It is counter productive, wastes our time and slows down process of bug fixing in general. I am not here to argue with anyone and my comment is purely informative. Please do not attempt to get into management related conversations on this bug tracker. Thanks!

Comment by Icode [ 03/Aug/16 ]

@[Mojang] MissMarzenia (Aleksandra Zajac)

No one expects hard dates. But Majong's kanban/agile hybrid flavor of sprint management which is non-standard to the rest of world tends to frustrate both your tech and non-tech savvy user base. You should consider at least assigning bugs and making your current sprint items visible to the public. Your stories are all cluttered with user comments similar to what @Mat Cooke just asked.

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 03/Aug/16 ]

lotharmat We rarely report progress of fixes. I commented it was reported for test and fix. Sorry, we are not able to provide dates for implementation of fixes.

Comment by Mat Cooke [ 28/Jul/16 ]

Any progress on this?

Comment by R. Brown [ 26/Jul/16 ]

I used to be able to simply tap on burning netherrack and it would go out, no matter what I was holding. I never had to tap and hold.

Starting in 0.15, the only way to put out fire in the nether is to place a block on it.

Comment by internetuser1bill [ 21/Jul/16 ]

Plz, someone get this to the attention of the devs, it's an extremely frustrating bug

Comment by Mat Cooke [ 21/Jul/16 ]

When will this be resolved??

Still an issue in 0.15.3..

Comment by [Mojang] Mega_Spud (Jay Wells) [ 14/Jul/16 ]

My mistake - it doesn't affect android Clients when joined to a Win 10 PC Host over LAN.

If playing on Android as Single Player or as host then you cannot extinguish the fire in survival.

Comment by Mat Cooke [ 14/Jul/16 ]

Yup - Still having the issue here - Nexus 7 Android 6.0.1 MCPE 0.15.2

I have uninstalled MCPE and reinstalled it to no avail.

Cannot put out fire in survival in new or existing worlds. - In creative you can!

Comment by [Mojang] Mega_Spud (Jay Wells) [ 14/Jul/16 ]

I cannot reproduce this in 0.15.2:

On Windows 10 PC, a quick tap extinguishes the fire in creative and Survival.

On Android, a tap and hold is needed to extinguish the fire in Survival and Creative. Granted, this takes correct timing to not break the block when in creative, but at least the fire can be extinguished.

Is anyone still having an issue putting out the fire?

Comment by Mat Cooke [ 10/Jul/16 ]

@Liam. In 14.x you only needed to tap on the fire.

In 15.x (creative) you have to tap and hold (almost half way between a tap and full on block destroy) to extinguish.

In 15.x survival, it is like the fire extinguish function jut isn't being called and the block starts to be mined.

Is it possible to revert back to the 14.x method of just tapping on the block to extinguish the fire?

Comment by internetuser1bill [ 10/Jul/16 ]

affects 0.15.2 as well Sony Xperia Z3

Comment by gatharian [ 09/Jul/16 ]

Seams like when you try to extinguish the fire, the game ignores that it's there, so you end up breaking the block below it instead.

Comment by Mat Cooke [ 08/Jul/16 ]

Still a bug in 0.15.2

Comment by Mat Cooke [ 28/Jun/16 ]

Just downloaded 0.15.1 still a bug.

Please re-open

Comment by internetuser1bill [ 28/Jun/16 ]

It was released yesterday but the MOD marked it as fixed today so I think in future version, this bug will be fixed

Comment by internetuser1bill [ 25/Jun/16 ]

Affecting 0.15.1 Build 1, Sony Xperia Z3 D6003

Comment by Mat Cooke [ 16/Jun/16 ]

I was able to extinguish fire in 0.14.3 but not after the upgrade to 0.15.0

Comment by [Mojang] Mega_Spud (Jay Wells) [ 15/Jun/16 ]

Reopening as still occurs in 0.15.1 b1

To Reproduce:

  • Enter nether in survival
  • Light netherack
  • Try to extinguish the fire by punching
Comment by gatharian [ 28/Jan/16 ]

I'm not experiencing this issue in any builds for 0.14.0 - Tested in Survival

Comment by [Mojang] MissMarzenia (Aleksandra Zajac) [ 08/Dec/15 ]

I have reported this issue for testing, thanks for reporting.

Comment by Zhuowei Zhang [ 27/Nov/15 ]

Looks like GameMode::startDestroyBlock isn't being called; that function is responsible for calling Level::extinguishFire to put out the fire when you punch a block in Survival.

Comment by rplatham [ 16/Nov/15 ]

Confirmed on Samsung Galaxy S4 Active Android 5.0.1 MCPE 0.13 build 5 in survival single player.

I started some fires and, with no item in hand, I tapped and held on the fire. I expected this action to put the fire out. Instead, the player mined the block under/behind the fire. Same results when I had an item in hand.

When I tried this in creative mode, the tap and hold on the fire put the flames out as expected.

Comment by Crazy Dude [ 14/Nov/15 ]

Exactly, PlantSeed.

Comment by ItsPlantseed [ 14/Nov/15 ]

I think you mean extinguish fire with hand in survival?

Comment by Crazy Dude [ 14/Nov/15 ]

Not just a punch, but actually you tap and hold on fire.

Generated at Sat Jan 11 14:52:44 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.