Links
Tags
Creators
Details
1.2.0+26.3
Compatibility
Changes
changelog
Ported to Minecraft 26.3 1.2.0 (NeoForge).
Added
-
In-Game Configuration: Built-in config screen accessible directly from NeoForge's Mods menu via the Config button (no extra mod dependencies required). Easily tweak options with instant application. Fully localized in English, French, German, Spanish, and Brazilian Portuguese.
-
Inspection Mode Outline Colors: Custom outline colors (Gold, Green, Red, or Blue) or option to disable them per block family (workstations, bells, and beds).
-
Toggle Feedback:
-
Added a UI click sound when toggling Inspection Mode.
-
Added a HUD indicator showing on/off status that smoothly fades out and respects the F1 key overlay toggle.
-
-
Lava Cauldron Light: Cauldron lava stage now emits light level 15, matching vanilla lava cauldrons.
Changed
-
Minecraft 26.3 Port: Updated to target Minecraft 26.3 (NeoForge
26.3.0.11-betaor newer), leveraging new GPU rendering pipelines, matrix handling, custom geometry events, and 26.3 loot table syntax. -
Performance Optimizations:
-
Optimized the Inspection Mode scanning algorithm to traverse spheres column-by-column.
-
Refactored outline rendering to cache and reuse line gizmos instead of rebuilding them every frame.
-
-
Codebase & Architecture: Reorganized into dedicated packages with complete decoupling of client-only logic and NeoForge event registrations.
-
Configuration Cleanup: Renamed config options to match the in-game UI labels (with automatic migration for existing configuration files) and implemented atomic file writes to prevent file corruption.
-
Dependencies: Requires Minecraft
26.3.0to26.4.0and NeoForge26.3.0.11-betaor newer.
Fixed
- Fixed an issue where Inspection Mode outlines persisted across level or dimension changes.
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:PMg729qN:kJHRK8J1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PMg729qN:kJHRK8J1"
}

