Links
Tags
Creators
Details
All versions
2.3.1-1.20.2-forge
Release
Useful Tools 2.3.1 — Minecraft 1.20.2 Forge3 weeks ago 1
Compatibility
Minecraft: Java Edition
1.20.2
Platform
Forge
Supported environments
Client and server
Changes
- Renamed the former Soul Lantern to Ectoplasm Lantern. New content uses
usefultoolsmod:ectoplasm_lantern;usefultoolsmod:soul_lanternremains a deprecated save-compatibility alias. - Replaced the transparent
cube_allEctoplasm Lantern and Mining Charge blocks with bounded, solid-backed models on all modern targets; added state-complete charge orientation and armed-indicator variants. - Made newly placed Mining Charges remain stable when their block-entity data has no saved fuse, and added dedicated unlit, lit, directional, and glass-platform visual evidence.
- Split modern inventory sprites from placed-block geometry and restored bounded selection/collision plus non-occluding rendering, preventing adjacent floors and walls from being culled behind transparent pixels.
- Added the equivalent Forge 1.7.10 repair with opaque generated block faces, bounded legacy blocks, and separate original inventory sprites.
- Repaired the Forge 1.7.10 Wraith spawn egg to use Minecraft's complete two-pass egg texture with Wraith-specific colors instead of requesting a missing overlay texture.
- Added Wraith WTHIT coverage wherever WTHIT is supported, including live Ectoplasm Lantern suppression and ectoplasm-infused weapon eligibility; WTHIT remains optional.
- Decoupled natural Wraith spawning from the Ghost enable switch; Wraith spawning now follows its own enable and chance controls while retaining its distinct hostile behavior.
- Fixed event-driven advancements, including the Wraith encounter advancement, to award their declared remaining criteria instead of assuming every advancement used a criterion named
trigger. - Reduced the paged 1.20.x/1.21.1 config layout to seven entries per page so loader-provided buttons no longer overlap Useful Tools navigation controls.
- Added a 16-target static resolver gate and expanded release-JAR checks for blockstate, model, texture, and item-model completeness.
- Preserved all registry IDs, recipes, configurations, save formats, and published compatibility bounds.
Optional dependencies
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:VFnQ6wSJ:HPRhytR2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VFnQ6wSJ:HPRhytR2"
}


