Tags
Creators
Details
All versions
1.0.4
Release
G1ax Crystal Optimizer 1.0.42 months ago 463
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Fabric
Legacy Fabric
Supported environments
Client-side
Changes
🔮 G1ax Crystal Optimizer Release Notes
🚀 Version 1.0.4-mc26.2 (Minecraft 26.2 Support)
This release adapts the G1ax Crystal Optimizer mod to support Minecraft 26.1.2 & 26.2 running on the latest Fabric loader.
New Features & Optimizations
- Java 25/26 Platform Support: Compiled with compatibility for Java 25 compiler specs and optimized to execute efficiently on modern JDKs.
- Unobfuscated Mojang Mappings: Fully transitioned class references and mixin targets to match Mojang's official unobfuscated mapping environments.
Re-architected Components (Minecraft 26.2 Compatibility)
- Record Packet Adapter: Adapted the outgoing packet interceptor inside the ClientConnection mixin to query the new flat
recordstructure ofServerboundInteractPacket. Evaluates the presence ofhand() == nullto correctly optimize attacks without using the deprecated/removed innerHandlerinterface ordispatch()method visitor patterns. - Refactored GUI & Chat Accessor: Migrated in-game command messages to print system feedback using the new
mc.gui.hud.getChat().addClientSystemMessage(Component)path, aligning with the updated HUD class layout in Minecraft 26.2. - Fabric API Networking Update: Upgraded packet payload registrations in
Main.javato use the modernized Fabric API methods (clientboundPlay(),serverboundPlay(), andclientboundConfiguration()), resolving packet-registry mismatches and preventing client-side launch crashes. - Tooling Compatibility: Upgraded Lombok annotation processor version to
1.18.46in the Gradle build pipeline, resolving compilation daemonExceptionInInitializerErrorcrashes when building under Java 26.
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:Xqnzyc08:zdwc5eFZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Xqnzyc08:zdwc5eFZ"
}

