Links
Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 6 days ago
All versions
1.2-r2
Release
AccurateFPS+ v1.2-r22 weeks ago 56
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client-side
Changes
- Added separate NeoForge release jars for Minecraft 1.21.1 and 1.21.11, while retaining the existing Fabric jars and the
1.2-r2version. - Ported the HUD, all seven telemetry metrics, settings, presets, keybinds, F3 behavior, precise FPS slider, and optional Sodium slider integration to NeoForge.
- Added a NeoForge Mods-list settings button with a built-in configuration screen when neither optional UI library is installed; Cloth Config and YACL screens remain supported when available.
- Added an unbound-by-default keybind to cycle through the Minimal, Competitive, and Detailed HUD presets in-game; preset changes are saved immediately.
- Enabled Hide with F3 by default for new installations while preserving existing saved preferences.
- Preserved saved FPS limits above the vanilla slider cap by installing the extended range before Minecraft loads its options.
- Pinned NeoForge 1.21.1 to 21.1.259 and 1.21.11 to 21.11.45; defer optional-mod discovery until the loader has initialized its mod list.
- Split loader initialization from shared HUD/configuration behavior and made the FPS slider and Sodium integrations use loader-specific mod/config services.
- Verified player-facing feature parity across all four Minecraft-version/loader jars; only loader- and game-API adapters differ.
- Added release-jar checks for shared feature classes, metadata, and loader-specific entrypoints; CI now publishes only the four runtime jars.
- Updated the Gradle wrapper to 9.8.1 and Fabric Loom to 1.18.3 for both supported Minecraft targets.
- Updated the JUnit BOM to 6.1.3 for both target builds.
Optional dependencies
Any compatible version
Any compatible version
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:AQGahqU5:6yu2giDR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AQGahqU5:6yu2giDR"
}

