BetterF3 20.0.0 lands on Minecraft 26.3 with a sidebar fix

Key takeaways

BetterF3 has been the default answer to vanilla’s debug screen for years, and the reason is simple – it turns an unordered wall of text into configurable modules you can colour, reorder and switch off. It is one of the few mods that is purely additive to a vanilla system without changing any behaviour, which is also why it quietly breaks every time Mojang moves a class.

Version 20.0.0, published 4 October, is the full 26.3 release build for both Fabric and NeoForge. The major version number is a renumbering rather than a rewrite, but there are three real fixes in it and one of them has been broken since 26.2.

What changed in 20.0.0

The changelog is short, so here it is in full with what each line means in practice.

Added: full Minecraft 26.3 release support for Fabric and NeoForge. The 19.x line was built against the 26.2 release and the 26.3 snapshots. This is the first build the author is calling release-ready on the 26.3 release itself, on both loaders at once rather than Fabric first.

Changed: project version bumped to 20.0.0. BetterF3 uses the major number as a Minecraft version marker rather than a semantic break. There is no API change here that would affect a third-party module, beyond the 19.0.1 fix below.

Changed: the Shader line now lists every applied post effect, matching vanilla 26.3. This is the most useful change. Minecraft 26.3’s own debug output lists the full post-processing chain, and BetterF3 was still showing a single shader name. If you run Iris or a post effect stack, that line is now actually diagnostic rather than decorative.

Fixed: right-side text alignment when Debug GUI Scale differs from GUI scale. The 26.4 cycle’s debug overlay work introduced a separate scale setting for the debug screen, and BetterF3’s right-hand column was aligning to the wrong width when the two scales disagreed. Anyone running a small debug scale on a large GUI scale was seeing text run off the edge.

Fixed: Hide Sidebar works again. The scoreboard sidebar moved to a new class in 26.2, which silently broke the option that hides it. This has been broken for an entire version cycle, and if you play on a server with a persistent scoreboard it is the single most noticeable fix in the release.

Frame time graph visible while flying over Minecraft terrain

The 19.0.1 fix worth noting

Published the same day for 26.2, version 19.0.1 made BaseModule public so that third-party modules outside the BetterF3 package can extend it. That is an addon-developer change rather than a user-facing one, but it explains why 19.0.1 and 20.0.0 arrived together – the author shipped the API fix to the old line and the version bump to the new one in a single pass.

If you maintain anything that adds a custom BetterF3 module, that is the build you want to target.

Why this matters for a 26.3 mod list

BetterF3 sits in the category of mods that are the first thing you install and the last thing you think about. It has no gameplay effect, no server component, and no performance cost worth measuring. The consequence is that people forget it is pinned to an old version until something else in the pack refuses to load.

Three practical notes for anyone assembling a 26.3 list:

That last point is the interesting one. Our coverage of the F3 overlay redesign covers what Mojang is building, and the 26.4 snapshots have added configurable debug profiles, a lightmap visualisation you can toggle from options, and chart displays that used to need a key combination. Vanilla is moving towards the thing BetterF3 was built to provide.

Minecraft scene used for measuring render performance

Where the mod still wins

Even with vanilla improving, three things keep BetterF3 installed.

Module ordering and colour. You can decide which lines appear, in what order, on which side, in what colour. Vanilla’s redesign makes the overlay configurable in terms of what is shown, not how it is laid out.

Information density. BetterF3 strips the lines nobody reads and keeps the ones that matter, which on a 1080p display is the difference between an overlay that covers a quarter of the screen and one that covers an eighth.

The animation. Minor, but the overlay slides in rather than appearing instantly, which makes a tap of F3 to check coordinates less jarring. Small things like this are why the mod has stayed popular.

If you are chasing frames rather than readability, the debug overlay is not where your time goes – our performance mod list and our culling explainer cover what actually moves frame time, and a debug overlay costs almost nothing to draw.

Updating

Drop in the 20.0.0 file for your loader and remove the 19.x one. The config format has not changed between the two, so your module layout carries over. If the right-hand column was running off screen for you before, that will fix itself without touching settings, because the alignment bug was the mod reading the wrong scale value rather than a bad config.

Shader-lit Minecraft vista used for an FPS comparison

Our read

This is a maintenance release with one genuine quality-of-life fix buried in it. The Hide Sidebar regression had been live for a full version cycle, and the fact that it took a major version bump to surface says something about how invisible client-side quality-of-life mods become once they work. If you have been playing on a scoreboard server and wondering why the option did nothing, this is why.

The Shader line change is the one to actually notice. With Vulkan now the default renderer in the 26.4 snapshots and the post effect chain becoming more complex, a debug line that lists the full stack is going to matter more over the next few releases, not less. Our notes on the Vulkan switch cover why.

Images: Photon Shaders project gallery.