Back to mods
Long-Standing Bug Fixes project artwork

CurseForge · Minecraft mod

Long-Standing Bug Fixes

Fixes confirmed bugs that have stayed open for years: campfires and comparators, golem poppies, burning skeleton arrows, wind charges and items.

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

Quick answer

Which Long-Standing Bug Fixes release should I use?

Updated today
Latest stable file long_standing_fixes-1.4.0+26.3-neoforge
Game version 26.3
Loader NeoForge

Long-Standing Bug Fixes long_standing_fixes-1.4.0+26.3-neoforge targets 26.3 with NeoForge. The project page does not say whether this file belongs on the client, dedicated server, or both. No extra mods listed for this file.

Where it goes

Is Long-Standing Bug Fixes required on the client, server, or both?

The project page does not say whether this file belongs on the client, dedicated server, or both.

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 Long-Standing Bug Fixes long_standing_fixes-1.4.0+26.3-neoforge need?

long_standing_fixes-1.4.0+26.3-neoforge. 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 Long-Standing Bug Fixes without breaking your instance.

Built for Long-Standing Bug Fixes long_standing_fixes-1.4.0+26.3-neoforge. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use long_standing_fixes-1.4.0+26.3-neoforge. It targets 26.3 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 this file belongs on the client, dedicated server, or both.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside long_standing_fixes-1.4.0+26.3-neoforge. It opens that exact file at the source.

About this project

What does Long-Standing Bug Fixes add?

Some bugs on Mojang's tracker have been confirmed for years and are still open. This mod fixes a handful of them. Every fix is small, does exactly what the bug report asks for, and can be turned off on its own.

Please report bugs here.

The fixes

MC-166272: comparators can't read campfires. Every other block that holds items gives a comparator signal, but campfires don't. Now they do, the same way a container would: 4 for one item, 8 for two, 11 for three, 15 for four. You can use that to tell when food is done or when a slot is free.

MC-159069: baby villagers ignore the iron golem's poppy. Up to 1.13, a baby villager would walk over to an iron golem holding out a poppy and take it. Since the villager AI was rewritten in 1.14 they ignore it. Now the nearest baby villager comes over again and takes the flower.

MC-217397: burning skeletons don't shoot burning arrows. Up to 1.10, a skeleton that was on fire shot burning arrows, more often the higher the local difficulty. That stopped when wither skeletons were split off. It works again, with the same rule as back then.

MC-280273: wind charges don't move dropped items (1.21.5 and newer). Since 1.21.5, dropped items ignore wind charges completely. Now a wind charge blows them away again. It still never destroys them, and other explosions are left alone.

MC-219854: spectators take void damage. Spectators were made immune to the void once, and then started taking void damage again. Staff watching from below an End island die. Now spectators ignore void damage, and nothing else changes.

MC-168976: a broken spawner floods the log (1.21.1). A spawner whose entity data has a broken custom name logs a warning with a full stack trace on every spawn attempt. Each broken name is now logged once.

MC-186909: a lit creeper eats your flint and steel. Once a creeper is lit, every further click on it with flint and steel still costs durability, and every click with a fire charge still uses one up. Now clicking a creeper that's already lit does nothing.

MC-261789: falling blocks break below Y=0. Sand or gravel that lands fast below Y=0 can stop a tiny fraction of a block too low, and then it breaks into an item instead of turning into a block. Contraptions that drop sand from high up lose blocks that way. Now it lands as a block.

MC-269636: "Lighten Up" for taking the wax off. The advancement is for scraping a lit copper bulb so it shines brighter, but taking the wax off a waxed bulb gave it too. Now only scraping counts. "Wax Off" works the same as before.

MC-210491: sculk sensors ignore batted fireballs. Hitting any entity makes a vibration, except batting a fireball back. Now that counts too, so a sculk sensor can tell a ghast fight is going on.

MC-265635: a cat on one chest blocks the chest below it too. Stack two chests and let a cat sit on the top one, and neither opens. The game looks for cats in the space above a chest, and a cat sitting on the chest above reaches down into it. Now a cat only keeps the chest it's sitting on shut.

MC-135198: dispensers can't light big portals. A dispenser with flint and steel only lights a nether portal if the spot in front of it touches the frame. Aim it at the middle of a 5x5 portal and nothing happens. Now any empty spot inside a finished frame works.

Config

config/long_standing_fixes.properties has one line per fix, named after its bug number. Set one to false to get the vanilla behaviour back.

FAQ

Client or server? The server needs it (or your game, in singleplayer). Players don't need it to join.

Does it need anything else? No.

How is it tested? Every fix has two game tests. One checks the fix works. The other runs the same setup without the fix and checks that the bug is still there in vanilla, so we notice when Mojang fixes one. They run on 1.21.1, 1.21.11, 26.2 and 26.3, on both NeoForge and Fabric.

Can I use it in my modpack? Yes, go ahead, no need to ask.

MIT. Developed with AI assistance. Source: https://github.com/traelmyx/long-standing-bug-fixes

Project description from CurseForge.

Pick your setup

Long-Standing Bug Fixes by Minecraft version and loader

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

8 available setups

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

Recent files

Long-Standing Bug Fixes versions and loaders

40 of 40 releases match

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