Tags
Creators
Details
All versions
5.3.0
Alpha
tetra 5.3.03 years ago 270
Compatibility
Minecraft: Java Edition
1.19.1–1.19.2
Platform
Forge
Supported environments
Client and server
Changes
New features:
- The holosphere can now be placed on the ground
- placed with shift+rmb
- can be right clicked to open holosphere UI
- enabled holosphere lookup when near a workbench
- added percussion scanner module for the holosphere
- allow scan mode to be toggled for placed holospheres
- right clicking a holosphere in scan mode with a hammer scans nearby chunks for ruins
- chunks with ruins are indicated with a red/orange beam
- apprentice cartographers can now sell maps to the ancient ruins
Changes:
- tweaked keybind UI elements
- changed notification sounds when items settle and when honing becomes available
Fixes:
- diamond sockets now also improve hammer efficiency
- fixed "Thermal Transfer" advancement not triggering
- fixed shield model console warnings
- fixed sweeper not working on some resolution/fov combinations
- holosphere improvement schematics no longer show when the holosphere already has the improvement
- fixed Long Gone, Restored Machinery, Combustion Power-up and Magmatic Press Channel advancements not triggering
- fixed multiblock schematic creative logspam
- fixed good quality modifier making items able to perform actions they shouldn't
- fixed missing and faulty decoration in ruin worldgen
- fixed ruined schematics sometimes working without repairs
- fixed banners not rendering on heater shields
- fixed stonecutter accepting unapplicable improvements
Technical changes:
- added data merging functionality for module variants
- added per-model render layering sorting
- added secondary interaction system
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:YP9DjOvN:db6bS0KD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YP9DjOvN:db6bS0KD"
}

