Tags
Creators
Details
All versions
6.0.0
Beta
6.0.03 years ago 1,166
Compatibility
Minecraft: Java Edition
1.20.1
Platforms
Forge
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Changes:
- updated to 1.20.1
- move most mod compat into a separate mod
- pristine sockets can now be repaired using regular gems (with increased xp cost)
- tweaked hardness for most fibre materials
- most modules that cost experience to craft now cost experience to repair (in addition to possible magic instability costs)
- bleeding now bypasses armor and iframes
- added source display in the schematic gui
- tweaked creative tabs
Fixes:
- added missing localization for rod materials
- fixed incorrect armor pen for tempered heavy blades
- fixed several issues relating to the holosphere sorting button
- tweaked serrate tooltip
- fixed modules settling not updating integrity until cache reset
- fixed crafted toolbelt having the wrong strap variant
- the tooltip for replacing the next module in the repair cycle no longer shows when the item has full durability (matches the underlying behavior)
- fixed rack advancement not working
- added missing localization for the holosphere block
- fixed tops of shafts and rooms in ancient ruins ending abruptly
Technical changes:
- cheesed in module dependent tags
- improved logging for faulty replacement data
- added datadriven block predicates for determining unlocks
- module textures now need to be placed within textures/item/[modules] (rather than textures/items/[modules])
- expect significant technical changes moving forward, if you make modpacks or addons and want to be kept in the loop please send me a DM
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:zJtERv77"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YP9DjOvN:zJtERv77"
}

