What Debugify works with.
| Platform | Java Edition |
|---|---|
| Loaders | Fabric, Forge, Quilt |
| Minecraft versions | 1.18.2, 1.19.1, 1.20.1, 1.20.6, 1.21.1, 1.21.8, 26.1.2, 26.2 |
| Environment | Client, Server |
Debugify patches more than 70 long-standing Minecraft bugs taken directly from Mojang's public bug tracker, without adding any new items, blocks, or mechanics. It runs on Fabric, Forge, and Quilt, though only the Fabric build has kept pace with current Minecraft versions, and both the client and server side are marked optional so a single side can run it alone.
Long-standing Minecraft bugs this mod fixes
Debugify's patch list is pulled from Mojang's own bug tracker rather than a community wishlist, so every fix corresponds to a real, numbered report. A handful of examples show the kind of decade-old rough edges it targets.
- MC-577: mouse buttons other than the default set are blocked from working as inventory controls.
- MC-121772: players on macOS cannot scroll while holding Shift.
- MC-237493: the in-game telemetry toggle does not actually disable telemetry.
- MC-162253: crossing certain chunk borders causes a lag spike.
- MC-2025 (server side): mobs wander out of fenced areas or suffocate inside blocks while chunks are loading.
- MC-30391 (server side): chickens, blazes, and the wither still throw off fall particles even while falling slowly.
The mod also folds in fixes that used to need separate single-purpose mods, covering shield rendering, shift-scroll behavior, chunk saving, item tooltips, and title screen quirks, so a modpack can drop several small fix mods for one.
Installing Debugify and picking which fixes run
- 1.Download the Fabric, Forge, or Quilt build that matches your Minecraft version and loader from the Modrinth page.
- 2.Drop the jar file into your mods folder like any other mod.
- 3.Launch the game. Every fix is on by default and needs no setup.
- 4.Open Fabric's Mod Menu in-game, or edit .minecraft/config/debugify.json directly, to turn individual fixes off.
Debugify's Modrinth listing declares no required dependencies, so Fabric API is not needed just to run the jar. If you already have Fabric API installed for other mods, that is fine too. Fabric is worth installing through a Fabric Loader setup before adding Debugify, since the jar itself does not install the loader.
Loader and version support
Support across the three loaders is uneven. Fabric is the actively maintained build and reaches current Minecraft 26.2. Forge's last release only targets Minecraft 1.19.1, and Quilt's last release only targets 1.20.6, both years behind. Anyone on a recent Minecraft version who runs Forge or Quilt instead of Fabric will not get a compatible Debugify build.
Questions about Debugify.
5 questions
What does Debugify actually change in Minecraft?
Nothing new. Debugify only corrects existing engine and gameplay bugs already logged on Mojang's bug tracker, such as broken mouse controls, incorrect particle effects, and lag from chunk loading. It adds no new items, blocks, or mechanics, and every fix works automatically once the mod is installed.
How do I install Debugify?
Download the build for your loader and Minecraft version from Debugify's Modrinth page, then place the jar file in your mods folder alongside your other mods. No extra setup is required. The fixes apply automatically the next time the game launches.
Does Debugify need Fabric API?
No. Debugify's Modrinth listing declares no required dependencies, so the jar runs on a bare Fabric, Forge, or Quilt install. Many players already have Fabric API for other mods, but it is not required just for Debugify to work.
Which Minecraft version does Debugify support?
It depends on the loader. The Fabric build is current through Minecraft 26.2. The Forge build stops at Minecraft 1.19.1 and the Quilt build stops at 1.20.6, since neither has been updated since those releases. Check the Modrinth version list before installing on an older loader.
Can I turn off individual bug fixes?
Yes. Fabric users can manage every fix through Fabric's Mod Menu, which gives Debugify a full configuration screen. Anyone without Mod Menu can edit the plain JSON config file at .minecraft/config/debugify.json instead. New fixes are added off by default so a modpack can review them before turning them on.
