Skip to content

Allow anonymous analytics?

Our cookieless analytics show us which features get used and store nothing on your device. We never sell your data or use it for advertising.

Privacy choices

Choose what ModDex may collect. You can change this anytime from Privacy choices in the footer.

Read the full privacy policy

Strictly necessary Required for the site to work: login sessions, security tokens, and abuse prevention. Always on and cannot be disabled. Always on
Analytics Cookieless analytics through PostHog's EU servers, used only to see which features get used. Nothing is stored on your device, and the anonymous visitor ID resets every day. Needs your consent because usage data goes to a third party. Never used for advertising or profiling. Off by default in the EU and UK.

Hitchless

Quick rating

Community listing page, reviews may not be monitored by the author.

How listings work Are you the author?

Hitchless

By pympymg

No reviews yet

Fewer stutters: preloads the code your modpack needs and shows the cause of every hitch.

Mod Loaders
Minecraft
26.3
Shockbyte server hosting: 35% off your first server with code MODDEX35 (opens in a new tab)

About

Description

Hitchless

Fewer stutters in big modpacks, and the cause of every one that is left.

FPS counters show the average. What you feel are the single frames that take 50, 100 or 300 ms: the hitch when you open a screen for the first time, meet a new mob, or the game cleans up its memory. Hitchless goes after exactly those frames.

Warmup: no more "first time" hitches

In a modpack, the first time something happens in a session, the game has to load its code, and every mod gets to change that code first. That happens on the render thread, in the middle of a frame.

Hitchless notes which code your game needs while you play. At the next start, it loads exactly that code on a low-priority background thread, right after the title screen appears. When play needs it, it is already there.

  • Measured in a 168-mod pack: time lost to loading code on the render thread during play dropped from 328 ms to 19–59 ms.
  • Code is only loaded, never run early: nothing behaves differently.
  • Learns by itself. The first session only learns; every session after that benefits.

Stutter Detective: every hitch gets a cause

Press F7 for a small panel with your usual frame time, FPS, the 1% low, a graph of the last frames (hitches in orange and red) and the cause of the last hitch:

Cause What it means
Garbage collector Java paused the game to clean up memory
Loading code Code of the game or a mod was loaded for the first time
Opening a screen Building a menu or inventory screen took long
Compiling a shader A render pipeline was compiled while drawing
New chunks / World rendering The world took longer to draw than usual
Queued work (server data) Handling what the server sent
Game tick / Autosave Game logic, or the singleplayer server saving the world
GPU/driver/system Nothing in the game's own code explains it

When you leave a world, a report is written to the hitchless folder: frame times, hitches per cause, the 15 worst hitches, which mods' code was loaded during play, and where the render thread creates the most garbage. Great for finding the mod that causes your stutters.

Details

  • Client only. Not needed on servers.
  • Uses Java's built-in Flight Recorder for the JVM causes (included in normal Java installs). Without it, the panel still works, without garbage collector and code causes.
  • Costs about 0.015 ms per frame in a 168-mod pack.
  • Settings in config/hitchless.properties: panel, warmup, report, how big a hitch must be.
  • The learned list is config/hitchless/warmup-classes.txt. Delete it to start over.

Requirements

Minecraft 26.3, Fabric Loader 0.19.5 or newer, Fabric API, Java 25.