Tags
Creators
Details
0.0.3-1.21.1
Compatibility
Required content
Changes
What's New
-
Modloader Change The mod has officially been ported to NeoForge, and this is the version it will be updated for going forward.
-
New Ore – Jaspilite A brand new ore has been added: Jaspilite
- Visually similar to Malachite, but with a black and red color scheme
- Positioned between Diamond and Netherite in terms of strength
- Not required for progression-optional tier
-
Creative Tabs Multiple new creative tabs have been added to organize content:
- Tools
- Armor
- Blocks
- And more
-
Config File (Work in Progress) A config file has been introduced. While currently non-functional, all values map directly to in-game systems for future customization.
-
Music Discs Two early-stage music discs are now available
- Both currently use placeholder audio
- Original music will arrive in a future update
Balance & Gameplay Changes
-
Armor & Tool Rebalancing All sets have been rebalanced for a more linear progression from Diamond → Jaspilite → Netherite No more weird exponential stat jumps or misleading tier strengths
-
Sapphire Tools
- Nerfed: No longer have built-in Looting or Fortune
-
Sunstone Armor
- Nerfed: No longer grants Fire Resistance by default
- Reason: Preserves the uniqueness of the Ring of Sunstone
-
Atherium Armor
- Nerfed: No longer grants extra hearts
- Reason: Stacking it with the Ring of Ruby previously resulted in three rows of hearts, breaking balance
-
Sunstone Sword
-
Changed to no longer deal vanilla fire damage
-
Instead, it applies a new custom status effect: True Fire – sets entities ablaze only while the effect is active
- Can still be extinguished with water
-
UI Changes
-
Gem Polishing UI The interface for polishing gems has been visually updated
- Functionality remains unchanged
Known Missing Content
- Custom Villager and Rock Candy Trade Not yet re-implemented in the NeoForge port. Will return in a future update
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:NlqncgtT:yAqotW5u"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NlqncgtT:yAqotW5u"
}

