0.2.0
Compatibility
Changes
With 0.2.0 you still cannot enter Mystic Origin without getting the mystic stone from creative however all ores from 0.6.0OG are added in with Mystic Jade (previously Core Jade) now having an unpolished version that needs to be stone cut into the polished version, the Mystic Combiner is somewhat implemented with its recipie and gui working however the actual functionality is not implimented. Fire quartz is now known as Blazing Quartz. Implementing a "Mystic Stone Blend" that can be made from overworld stones right now that can be smelted to make mystic stone (for automation and for actual legit survival entry) is my current prority along with getting the Mystic combiner working so that the 2 versions of jadium (jade-ium) can be made, thats all that i want to say other than that CORE PLATNUM ARMOR IS BACK AND IS FINALLY BALLANCED!
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:BJSbUPK6:SAknaIMG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BJSbUPK6:SAknaIMG"
}

