Using Fire Spread Tweaks Safely with Other Fire-Related Mods and Datapacks

Why conflicts happen

Fire Spread Tweaks works by forcing doFireTick to false on world load and replacing vanilla fire lifetime with its own timer. Any other mod, datapack, or command that sets doFireTick back to true, or that spawns its own fire entities, can override or bypass the mod's behavior. You'll notice this as fire that spreads normally or never goes out on ordinary blocks.

Diagnosing and fixing conflicts

1. Load your world and run /gamerule doFireTick to see the current value. If it's true, something re-enabled it after the mod applied its setting.

2. Check for datapacks in your world's datapacks folder that touch fire, gamerules, or world tick behavior. Remove or disable suspicious ones and reload.

3. If another mod adds its own fire blocks or ignition mechanics, test them in isolation. Fire from those sources may not respect the burn timer.

4. Re-apply /gamerule doFireTick false manually after loading if a conflicting mod keeps flipping it. You can also bind it to a command block or startup function.

5. Keep netherrack, magma, and soul sand features separated from anything that spawns vanilla-style fire, since those blocks intentionally burn forever and can look like a bug when mixed with other mods.

Once doFireTick stays false and only the mod's timer is running, fire behavior becomes predictable again.