Links
Tags
Creators
Details
All versions
0.6.0+mc26.3
Release
0.6.0+mc26.33 days ago 31
Compatibility
Minecraft: Java Edition
26.3
Platform
NeoForge
Supported environments
Client and server
Changes
Changed
- Updated for Minecraft 26.3 (Fabric Loader 0.19.5+ / Fabric API 0.161.0+; NeoForge
26.3.0.7-beta+). Requires Minecraft 26.3.
Fixed
- Ported to the 26.3 APIs: the see-through shape guide now runs on the new
renderpearlrender layer (the OpenGL/Vulkan abstraction introduced in 26.3) and declares its own translucent colour target; keybinds use the SDL key codes that replaced GLFW; the config screen's Open config folder button uses the newBlaze3D.openUri.
Notes
- NeoForge for 26.3 is still in beta; this build targets
26.3.0.7-beta. - Keybinds carry over — the
[/]defaults and any custom bindings are saved by key name, not key code, so nothing needs rebinding after the GLFW → SDL switch. - ModMenu now resolves from the Modrinth maven at build time (no player-facing change).
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:syHecAZ6:hP3eP8bc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:syHecAZ6:hP3eP8bc"
}

