mojira.dev

Jennifer Sorensen

Assigned

No issues.

Reported

No issues.

Comments

I wish I could +1 Ezer'Arch's comment, and I really hope this is not intended. Gravel for the ocean and deep ocean floors does not make any sense at all – not in a "realistic" sense, or in a gameplay sense. It's not accurate, it's not attractive, and it's not useful. Replacing two highly desirable blocks, sand and clay, that you have to go out and explore to get, with a block that nobody sets out to get beyond a few peices of flint early game – makes no sense. Improving respiration enchant and creating the water breathing potion just to nerf the usefulness of what's already called the most barren and empty biome – makes no sense.

Please say that this is a bug, or even a trial for the snapshot that will be reverted.

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.