All versions
1.3.1+26.2
Release
Laminar 1.3.1+26.2last month 649
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Server-side
Required content
Changes
Laminar Engine - Version 1.3.1 Changelog
Architectural Unification & Compatibility
- The Universal Edition (Dynamic Runtime Downloader): Discontinued the split between "Standard" and "Server" editions. Laminar is now distributed as a single, ultra-lightweight universal JAR. To achieve this without causing classpath pollution on clients, a pre-launch bootstrapper has been engineered. When deployed on a headless dedicated server, the engine automatically detects missing hardware bindings and dynamically fetches/injects the precise native compute libraries (LWJGL OpenCL) directly into the server's memory at runtime. This guarantees zero conflict with client rendering mods (e.g., Sodium) while maintaining full asynchronous co-processing on dedicated servers.
- Diagnostic Overlay (F3) Pipeline Fix: Resolved an issue on Minecraft 26.2 where monolithic UI render passes caused the diagnostic text entries to endlessly duplicate and accumulate on the screen. The overlay now utilizes a localized purge-and-reinject routine, ensuring real-time telemetry updates (active sound slots, AI grids) remain clean and static.
- Third-Party HUD Compatibility: Implemented a hardware-level compatibility guard for UI-altering modifications. The native Laminar diagnostic overlay will now gracefully disable itself upon detecting
BetterF3or similar structural HUD mods, preventing visual overlapping and maintaining a clean user interface.
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:XiNdHn2z:Ka7FOnmE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XiNdHn2z:Ka7FOnmE"
}

