Tags
Creators
Details
All versions
Mixin Startup Crash —
1.0.6
Release
G1ax Crystal Optimizer 1.0.65 days ago 1,200
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Fabric
Legacy Fabric
Supported environments
Client-side
Changes
G1ax Crystal Optimizer Release Notes
Version 1.0.6
Bug Fixes
Mixin Startup Crash — JAVA_25 Compatibility Level (mc-26.2)
- Fixed a fatal startup crash on the mc-26.2 build:
IllegalArgumentException: The requested compatibility level JAVA_25 could not be set. Level is not supported by the active JRE or ASM version. - Root cause: The mixin config for the mc-26.2 version declared
"compatibilityLevel": "JAVA_25", but the ASM version bundled with Fabric Loader (ASM 9.x) does not recognizeJAVA_25as a valid level, causing Mixin initialization to abort before the game loads. - Fix: Downgraded the mixin compatibility level to
JAVA_21. No Java 25-specific bytecode features are used in mixin classes, soJAVA_21is fully sufficient. The mod still compiles and targets Java 25 bytecode for non-mixin classes. - Reported by <@1017102539486928918> — thank you!
Edge Crystal Placement (Both Versions)
- Verified and confirmed the
findAdjacentBaseedge placement fix from v1.0.5 is active in both the root (1.21.11) and mc-26.2 builds. - When your crosshair hits neighboring grass/ground on an edge flick, the optimizer detects adjacent obsidian/bedrock and executes the placement correctly.
Improvements
Better Command Help
/g1axoptimizer(no arguments) now displays a clean, detailed help screen showing:- Mod name and current version (v1.0.6)
- Current active mode
- All available modes with clear descriptions of what each one does
- Discord support link
- Replaces the old single-line usage hint with a properly formatted multi-line help output.
https://github.com/tech-anupam/G1ax-Crystal-Optimizer/compare/v1.0.4...v1.0.6
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:IHiygx2V"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Xqnzyc08:IHiygx2V"
}

