Links
Tags
Creators
Details
1.2.0+26.2
Compatibility
Changes
changelog
1.2.0 NeoForge (Minecraft 26.2)
Added
-
In-Game Configuration Screen: 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.
-
Customizable Outline Colors: Inspection Mode outlines can now be customized (Gold, Green, Red, Blue, or Disabled) individually for workstations, bells, and beds.
-
Enhanced Inspection Feedback: Added a click sound effect on toggle and a smooth visual HUD indicator that fades out naturally (hidden when F1 is pressed).
-
Lava Cauldron Light: Cauldron filled with lava now emits light level 15, matching vanilla behavior.
Changed
-
Optimized Scanning & Rendering:
-
Rewrote the inspection scan logic to iterate column-by-column, significantly improving scanning performance.
-
Refactored outline rendering to cache and reuse line gizmos instead of rebuilding them every frame.
-
Updated rendering hooks to use NeoForge's
SubmitCustomGeometryEventandRegisterRenderPipelinesEvent.
-
-
Codebase Refactoring:
-
Restructured code into dedicated packages and isolated client-side logic to prevent server-side issues.
-
Streamlined registry structures and block specs.
-
-
Configuration Improvements:
-
Standardized configuration option names to match the in-game screen labels (with automatic migration for existing files).
-
Config files are now saved atomically using temporary files to prevent corruption.
-
-
**Dependencies: Built against NeoForge [26.2.0.06-beta, 26.2.0.93].
Fixed
- Dimension Transfer Fix: Inspection Mode outlines now immediately clear when switching dimensions instead of persisting.
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:M8Sj2xV1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PMg729qN:M8Sj2xV1"
}

