Back to mods
Lazyboy's No Fire Spread project artwork

CurseForge · Minecraft mod

Lazyboy's No Fire Spread

Stops fire from spreading in the world.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which Lazyboy's No Fire Spread release should I use?

Updated last month
Latest stable file nofirespread-neoforge-26.1-1.0.1.jar
Game version 26.1, 26.1.1, 26.1.2
Loader NeoForge

Lazyboy's No Fire Spread nofirespread-neoforge-26.1-1.0.1.jar targets 26.1, 26.1.1, 26.1.2 with NeoForge. The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server. No extra mods listed for this file.

Where it goes

Is Lazyboy's No Fire Spread required on the client, server, or both?

The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server.

Client Source doesn’t say
Dedicated server Source doesn’t say
Loader for this release NeoForge
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

The source does not explicitly classify this release as client-only or server-only.

What else does Lazyboy's No Fire Spread nofirespread-neoforge-26.1-1.0.1.jar need?

nofirespread-neoforge-26.1-1.0.1.jar. Change the file and its required mods may change too.

No extra mods listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional mods.

Before you install it

Add Lazyboy's No Fire Spread without breaking your instance.

Built for Lazyboy's No Fire Spread nofirespread-neoforge-26.1-1.0.1.jar. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use nofirespread-neoforge-26.1-1.0.1.jar. It targets 26.1, 26.1.1, 26.1.2 with NeoForge; another release may have different loader, side or dependency requirements.

  2. 02

    Bring the mods it needs

    This file does not list any required mods. Do not add a library just because a different file uses it.

  3. 03

    Put it on the correct side

    The project page does not say whether it belongs on the client. The project page does not say whether it belongs on the dedicated server.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside nofirespread-neoforge-26.1-1.0.1.jar. It opens that exact file at the source.

About this project

What does Lazyboy's No Fire Spread add?

This is a simple mod that sets the no fire tick gamerule to false everytime the game/server loads, which then stops fire from spreading in the world

🔥 How Fire Spread Works

Minecraft’s fire system is governed by a repeating “fire tick” that controls whether fire spreads, burns blocks, or goes out.

The gamerule doFireTick determines whether fire behaves normally.

  • Enabled (true) → fire spreads, burns blocks, and extinguishes naturally
  • Disabled (false) → fire becomes static and does not spread or burn anything

🔥 Why Fire Spread Matters on Servers

1. Fire spread can destroy player builds

On a multiplayer server, one careless torch, lava bucket, or lightning strike can:

  • Burn down entire wooden bases
  • Spread through forests
  • Jump across roofs
  • Trigger chain reactions

On a public or semi‑public server, this becomes a griefing vector, even if unintentional.

2. Fire spread causes lag

Every fire block performs multiple random tick checks:

  • Should the fire go out?
  • Should it spread?
  • Which adjacent blocks are flammable?
  • Should those blocks ignite?

In large forests or big builds, this can mean thousands of checks per second, especially during:

  • Lightning storms
  • Lava near trees
  • Player‑made fires
  • Nether hubs with lots of netherrack

Disabling fire spread reduces server load.

3. Fire can spread across unloaded chunks

This is a subtle one:

  • Fire can start in a loaded chunk
  • Spread to the border
  • Load adjacent chunks
  • Continue spreading

This can cause:

  • Unexpected chunk loads
  • TPS drops
  • Large‑scale forest fires that nobody sees happening

Admins often disable fire spread to avoid these “invisible disasters.”

4. Fire spread interacts badly with mods

On modded servers, fire can:

  • Trigger block updates in modded blocks
  • Cause tile entities to tick more
  • Break machines
  • Spread to modded wood types with high flammability
  • Interact with worldgen structures in unpredictable ways

This is why many modpacks would want to ship with fire spread disabled by default.

5. Server rules and fairness

Many servers want:

  • Decorative fireplaces
  • Campfires
  • Torches
  • Nether portals

…but don’t want fire to behave realistically.

Disabling spread allows fire to exist without risk.

Simply put this in the "mods" folder of you server or modpack. Server-side is fully supported.

Project description from CurseForge.

Pick your setup

Lazyboy's No Fire Spread by Minecraft version and loader

Choose the version and loader you play, then open the matching release.

22 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

Lazyboy's No Fire Spread versions and loaders

13 of 13 releases match

Looking for an older file? The official CurseForge project page is in Resources.