Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 3 weeks ago
All versions
3.0.1-mc26
Release
inputbooster 3.0.1-mc265 months ago 964
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client-side
Changes
Changelog
3.0.1-mc26 - Minecraft 26.1.x
This update focuses on making InputBooster feel more complete for everyday players while keeping the mod stable during combat and low-FPS gameplay.
Added
- Module system for combat, movement, debug, profiles, anti-idle, and replay features.
- Per-server profile backend so settings can switch automatically for different servers.
- Input replay tools:
Rstarts or stops replay recording.Kplays the recorded replay.
- Advanced CPS limiter modes:
FIXEDHUMANIZEDCOOLDOWNWEAPON_AWARE
- Safe mode that disables active modules after repeated internal errors.
- Keybind conflict detection with event-log reporting.
- Event log backend for recent InputBooster activity.
- Config tools for presets, import, and export.
- Overlay lines for modules, replay status, safe mode, and latest debug event.
Changed
- Updated mod version to
3.0.1-mc26. - Profile saves now include the new CPS mode, replay, safe mode, event log, keybind warning, and per-server profile settings.
- CPS limiter now uses the selected CPS mode instead of only a fixed cap.
Fixed
- Prevented queued mod attacks from firing while InputBooster is inactive or not initialized.
- Prevented stale queued inputs from firing later after the mod is toggled back on.
- Reduced the chance of one physical click causing both a mod entity attack and a vanilla entity attack.
Build
- New jar:
build/libs/inputbooster-3.0.1-mc26.jar
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| inputbooster-3.0.1-mc26-sources.jar | Sources jar | 42.27 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:WGGNOhWY:rIemEoGt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WGGNOhWY:rIemEoGt"
}

