The tick is too slow.
Your input isn't.
InputBooster samples keyboard and mouse state faster than Minecraft ticks. A short tap that starts and ends between two ticks becomes the action vanilla would have run — without replacing vanilla's handlers and without inventing a single benchmark number.
- Loaders
- Fabric / NeoForge
- Minecraft
- 26.2 / 26.3
- Java
- 25
- License
- MIT
- 01Platform key stateRaw keyboard and mouse sampling, 60–1000 Hz
- 02Edge state machineOne action per physical press or release
- 03Bounded queue128 stamped actions, ordered, never unbounded
- 04Client tickVanilla calls, guarded per action
Static architecture diagram, not live telemetry
A recovery path, not a gameplay advantage.
The mod makes sure Minecraft sees input you actually produced. It does not generate input, alter reach, or hide anything from the server.
Pressed and released edges are captured even when both happen inside one 50 ms tick window.
Observing mixins run at HEAD and cancel nothing. Another mod's key is never remapped.
The poller and the event hooks write through one state machine, so the same press cannot fire twice.
There is no FPS or latency improvement figure on this site because the mod has not been benchmarked in a client.
Built for players and for maintainers.
Tune the input path
Install the right jar, understand the seven settings sections, and know which features help at low FPS — and which are cosmetic.
Open the gamer guideRead the internals
Follow an input from the platform poller to the drainer, audit the mixin contract, and build all three supported jars from source.
Open developer docsWhat InputBooster is, what it needs, and how to get a first session running.
Loader-specific install steps, version matching and safe rollback.
The settings window, input recovery, combat and movement tools, overlay, profiles and replay.
Every key in inputbooster.properties, its range, its default and what actually reads it.
Architecture, the input pipeline, feature managers, the settings UI, builds and tests.
Action semantics, queue rules, mixin inventory, schema tables and known limits.
Read the log, diagnose the common failures, and report a useful bug.
How to propose a change, match the code conventions and keep the mixin rules intact.
Version history, supported jar matrix and the status of the archived API.
4.1.2-alpha is an alpha. The input engine and settings screen are new code and have not been tested in a running client. 4.0.3-stable remains the last stable build. Read the limitations page before relying on a setting.