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.

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.

undefined

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.

undefined

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.