'doFiretick' makes fire to not extinguish. Lighting makes fire all over the place!

Very confusing :/

What exactly do you mean with 'doFireTick' ?

doFireTick is console command in game that make fire to not spread, it write like this: "/gamerule doFiretick", but it makes fire to not extinguish natural. In wiki is said that this command only make fire spread on or off, nothing about keeping fire like on Netherrack.

Actally I really like this "bug" since you can make fire last forever without the need if burning everything alive!

At least Mojang could make separate console like: '/gamerule FireStayAlive' and that would make them to not extinguish naturally. Then I would be satisfied.

This is the intended behaviour of doFireTick.

Really? But after every thunderstorm there are dozens of fires all over the place. I don't believe that is supposed to work this way.

The fire should stay, but the thunder shouldnt create any fire, if the game rule is deactivated. Else after just one thunderstorm there will be tons of fire all around the world, ugly as hell. I have tons of experience in this as I have my own server.

Wouldnt it just be better to remove the fire created by lightning if the rule is deactivated?

I'm not entirely sure how to understand this.
I disabled the FireTick on my server to avoid fire spreading all over the place and burning down everything.
Just like the rest in here it causes fires not to extinguish by rain anymore either, however, lightning strikes still cause fires.
My whole world is covered with random fire spots, on buildings, in fields, in trees. I even lost half of my cows to a fire burning in their cage without me noticing.

You can't be serious when you say it's working as intended

I can only second xelotar here.

The reason I'm using this rule is to disable fire spread, which works perfectly fine. However, a thunderstorm still causes fires which won't go away unless extinguished manually, which can be very annoying.

The option "doFireTick" may work as intended, but as has been suggested, lightnings shouldn't be able to cause fires when the rule is active. I cannot see any drawback from that and the developmental effort should be minimal.

This is tremendously annoying. I like to have doFireTick false on our server to allow players to make better fireplaces, but I can't do this without having lightning causing hundreds of fires in inaccessible locations that need to be manually extinguished! If doFireTick is false, lightning shouldn't make fires at all.

Noticed the same today and it is very annoying. 😞
I hope this can be changed or another rule could be added if lightning should create fires.

BUT the staying lightning fires can be a great gameplay element to have random fireplaces in a PvP Arena for example (without spreading)! So another rule would be great and everyone should be happy. 🙂

i found a fix that will get rid of the thunder. but it will also get rid of rain. open the map in mcedit and cover the highest place possible with block 36(piston movement block). this block is invisible, lets light go trough normally and you can walk in it. but do not block update it or else all the blocks 36 will dissapear.

This should be updated to v1.5.2 and reopened. The "bug", I believe, is not with /gamerule doFiretick false – the bug is with lightning.

Lightning should not be able to create fire at all if the fire spread is off, especially if "extinguish" is wrapped up with spread because of tick updates. It either needs to be able to start fire and the rain instantly extinguish it as normal, regardless of the state of doFiretick, and doFiretick should only stop the actual spreading of fire – OR – there needs to be a separate command to turn off all fire created by lightning, which can either be used in conjunction or separately from doFiretick.

We started a vanilla server about 2 months ago, and the owner decided to set /gamerule doFiretick false. We had never used it prior. Now I've never seen so much fire in game before. Everyone has infinitely burning jungles. Many of them are difficult to reach, and time consuming to manually extinguish. When you're exploring, you can tell that someone lives in the area because of the dozens of fires everywhere. Sometimes when I exit the Nether and return to the Overworld, I think for a moment that I am still in the Nether because everything is still on fire. Seriously, it's that bad – we shouldn't have more fire with fire spread turned off than we ever did with it on.

Whether it's truly a "bug" can be debated but this topic needs a different resolution.

I'd definitely second that – I cannot believe that this is an intended function of gamerule doFireTick false as Dinnerbone said. I feel that earlier commenters might have given the developers the wrong impression, and made them think that they were complaining about fire not spreading, which is NOT the problem.

This gamerule should, based on its description, prevent fire from spreading – but instead, it causes many, many more fires due to the lightning not properly taking doFireTick into account when it strikes. Even worse, when doFireTick is disabled due to its current non-functional behavior, these fires then spread, leading this command to be unusable in its current state.

Furthermore, looking at the sheer number of duplicate tickets created to report this single bug, I have to question the choices made by the Mojang bug reporter staff, specifically with regards to simply closing these massive number of duplicate entries instead of perhaps taking them as a sign that maybe this issue was not correctly resolved. A quick search for "doFireTick" results in a shameful number of entries simply being marked as duplicates and closed, complete with a snarky note indicating users should search before posting their bug reports – advice that the moderators should, perhaps, take themselves.

Agreed. Why has this been resolved? Lighting + doFireTick false + chunk loader = super annoying!

It is resolved since it should be fixed in the latest snapshot.

But your post was yesterday and I'm not entirely sure when C was released.