UpdateSuppressor

Update Suppressor 1.0.1

Fixed

• Fixed a crash when a suppression was triggered during a world tick. For example, a hopper feeding a comparator that reads a shulker box with a mismatched block entity crashed the game a few seconds after entering the world.
• An item falling on such a hopper no longer cuts the tick of the other entities in the world.

Improved

• The update suppression crash fix now also handles the wrapped error that Minecraft throws in this case.
• Block entities (hoppers, furnaces, etc.) and entities are now protected one by one, so a single failing one no longer cuts the rest of the world tick.
• A block entity or entity that triggers a suppression now waits before trying again, which greatly reduces lag.
• Crash-fix messages in the log are limited to one every 10 seconds. The first time a suppression is caught, its full stack trace is logged once to help with debugging.

Added

• New option crashFixCooldownMs in config/updatesuppression.properties to choose how long (in milliseconds) a block entity or entity waits after triggering a suppression. The default is 1000, the minimum is 0 (no wait) and the maximum is 600000 (10 minutes). Values outside that range are adjusted to the nearest limit, and invalid values fall back to the default.

Notes

• If a machine triggers a suppression every tick, the error is caught and logged, but the machine keeps failing (and may still cause some lag) until it is taken apart.
• Because of the wait after a suppression (one second by default), a machine that depends on a suppression firing every tick will run slower. Set crashFixCooldownMs=0 to remove it, at the cost of more lag.
• Items being moved by a hopper at the moment a suppression fires can be lost or duplicated, because the suppression interrupts the transfer halfway.
• Requirements are unchanged: Minecraft 26.3, Fabric Loader 0.19.0 or newer, Java 25. Fabric API is not required.