Tags
Creators
Details
All versions
1.6.0
Release
FPSFlow 1.6.05 months ago 20
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
[1.6.0]
Fixed
- NPC nameplate flickering — Entities whose nameplate visibility has been set to always-on by the server (
isCustomNameVisible = true, typical for plugin NPC systems) are now exempted from distance culling entirely. Previously the mod fought against the server metadata update on every view-distance change, causing persistent flickering. - Hysteresis reset every 200 ticks removed — The periodic full cache wipe in
NameplateCullingManagerwas resetting the hysteresis dead-band, causing a brief nameplate flicker roughly every 10 seconds for entities near the culling threshold.WeakHashMapgarbage-collects despawned entity entries automatically, so the manual wipe was never needed.
Added
- Background FPS limiter — When the Minecraft window loses focus the frame rate is capped at a configurable limit (default: 60 FPS unfocused, 30 FPS minimised) via a post-frame sleep on the render thread. Inspired by Dynamic FPS. Caps are profile-aware: Quality 30/10, Balanced 60/30, Performance 10/3, Ultra Performance 5/2. Toggle via
backgroundFps.enabledin the config. - Painting back-face culling — Paintings are never visible from behind, so the renderer now skips them entirely when the camera is on the back side. Uses a dot-product normal check against the painting's facing direction. Controlled by
entityCulling.paintingBackfaceCulling(default:true). - Tiered particle density LOD — Instead of a hard allow/block cutoff there are now three distance zones: near (<
midDistance): 100 % of particles; mid (midDistance→maxDistance): ~50 % via a stable position-based hash — no per-tick flickering; far (>maxDistance): 0 %. The newmidDistancevalue is configurable in all four built-in profiles and custom profiles. - FPS-adaptive LOD tightening — When the adaptive renderer detects low FPS (< 30 FPS: 0.7× multiplier, < 15 FPS: 0.5×), entity LOD distance thresholds shrink automatically. At 20 FPS the Balanced thresholds (40/80 blocks) behave like 28/56 blocks without requiring a manual profile switch.
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:ayg7iYUG:EtycviMO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ayg7iYUG:EtycviMO"
}
