3.1.0-legacy+1.8.9
Compatibility
Changes
AI disclosure: This mod's code and description were written with AI assistance, then built, tested in-game, and reviewed by kln.
!lag legacy 3.1.0 (Minecraft 1.8.9, Forge)
First 1.8.9 Forge build of !lag. In-game it is called !lag legacy. Client-side only, for Forge 11.15.1.2318 (Java 8). It has no extra dependencies.
Features
- FPS HUD: a small box in the top right that updates 4 times a second. It hides with F1 or F3, and its scale is adjustable.
- Entity distance culling (default 64 blocks). Players, the Ender Dragon, the Wither, lightning and anything you ride are never culled.
- Name tag culling for mobs (default 48 blocks). Player name tags are always kept.
- Tile entity culling for chests, signs, skulls, banners and similar blocks (default 64 blocks). Beacons and end portals are exempt.
- Particle distance culling: particles farther than 32 blocks are skipped.
- Menu FPS cap (default 60) and unfocused-window FPS cap (default 30). Set either to 0 to keep vanilla behavior.
- Smooth zoom: hold C, and scroll while zoomed to change the strength. Your strength is remembered.
- Settings screen: press Right Shift, or open Mods β !lag legacy β Config. Settings save when you close the screen.
- Config file: config/notlag-legacy.json
Not included: features that rely on the modern renderer in the 26.3 version, such as adaptive render distance, chunk compile budgets, render caches and shader-compatibility mode.
Tested: The build and 16 unit tests pass. On a real Forge 1.8.9 client (software rendering), the game reached the title screen and loaded a singleplayer world. All mixins applied with no errors. The settings screen, FPS HUD and zoom all work.
Not yet tested: real graphics cards, how much FPS the culling actually saves, OptiFine or other mods, and multiplayer servers. Please report any issues.
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:9nC6qNeD:s3f2SFKT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9nC6qNeD:s3f2SFKT"
}

