Can't put out fire by tap and hold in Survival (but can in Creative)
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 [Mojang] Adrian Östergård
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.
Linked Issues
is duplicated by10
Created Issue:
Can't punch fire in Survival
Usually, if you punch fire, you put it out. But on the 0.13.0 builds, it won't work on survival.
Can't punchfirein SurvivalCan't put out fire by tap and hold in Survival (but can in Creative)
is duplicated by
is duplicated by
is duplicated by
is duplicated by
is duplicated by
duplicates
is duplicated by
duplicates
relates to
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.
is duplicated by
is duplicated by
is duplicated by
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 [Mojang] Adrian Östergård
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.
Duplicate of MCPE-11594 – If you have not, please use the search function in the future, to see if your bug has already been submitted, as currently over 47% of tickets are being closed as duplicate.
Thank you for your report! This issue was, however, submitted at an earlier time as MCPE-11594. You may add any information you find relevant in the comment section there.
Marking this as Duplicate MCPE-11594.
You can add a vote and any helpful comments related to the bug there if you wish.
As bug MCPE-11594 has been closed as fixed in 0.15.1 I thought I should raise this one as the bug has not been fixed.
If I enter the nether in Survival, I cannot extinguish any fires whereas in 0.14.x I was.
This bug is not a duplicate of any 'open' issue
Thank you for your report!
However, this issue has been closed as a Duplicate of MCPE-11594.
It has been linked to this report. If you have additional information, please add it to that report.
Please search before reporting, as it's likely that one exists already.
Quick Links:
📓 Issue Guidelines – 💬 Community Support – 📧 Feedback – 📖 Game Wiki
Not just a punch, but actually you tap and hold on fire.
I think you mean extinguish fire with hand in survival?
Exactly, PlantSeed.
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.
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.
I have reported this issue for testing, thanks for reporting.
I'm not experiencing this issue in any builds for 0.14.0 - Tested in Survival
Reopening as still occurs in 0.15.1 b1
To Reproduce:
I was able to extinguish fire in 0.14.3 but not after the upgrade to 0.15.0
Affecting 0.15.1 Build 1, Sony Xperia Z3 D6003
It was released yesterday but the MOD marked it as fixed today so I think in future version, this bug will be fixed
Just downloaded 0.15.1 still a bug.
Please re-open
Still a bug in 0.15.2
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.
affects 0.15.2 as well Sony Xperia Z3
@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?
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?
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!
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.
When will this be resolved??
Still an issue in 0.15.3..
Plz, someone get this to the attention of the devs, it's an extremely frustrating bug
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.
Any progress on this?
Mat Cooke 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.
@[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.
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!
@[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.
Yes, it is reported. Please post only bug relevant comments in this bug tracker.
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.
Please add 0.15.9 to the Affected versions....
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.
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). .
Fixed in 0.15.90.8
With respect Rodriguez,
It is not fixed in 0.15.10.
Please mark as unresolved. It is still broken.
Mat Cooke - 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
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.
Still not fixed in v 16.0.5, update from Google Play - what gives?
Sorry, my mistake, it is fixed, it just feels different to use somehow... longer press perhaps? Cheers.
Hi Neil,
Yes takes about 0.5 seconds hold on the block!