Links
Tags
Creators
Details
26.1.2-0.3.0
Compatibility
Changes
The tier above netherite. The End keeps what's marked, and now the mark is the metal itself.
Downloads: pick the jar matching your Minecraft version
| Minecraft | NeoForge needed | File |
|---|---|---|
| 1.21.1 | 21.1.244 or newer | endrise-1.21.1-0.3.0.jar |
| 26.1.2 | 26.1.2.87 or newer | endrise-26.1.2-0.3.0.jar |
The Enderium Tier
- Nine new items: enderium sword, pickaxe, axe, shovel, hoe, helmet, chestplate, leggings, and boots, with their own teal-and-purple look, in hand, worn, and in the new Endrise creative tab
- Upgrade, don't enchant: netherite gear + Enderium Upgrade Smithing Template + enderium ingot at the smithing table, exactly how diamond became netherite. Enchantments and durability carry over
- Stats sit one honest notch above netherite (a little more durable, faster, sharper, tougher); fire resistance kept
- Soulbound is enderium-exclusive now: the enchant, the anvil, and the death-return only answer to enderium gear
Breaking change from 0.2.x (alpha honesty): gear "infused" or trimmed under the old marker system loses Soulbound eligibility. The items themselves load fine and keep their enchantments; run them through the smithing upgrade to bring them into the tier. The old trim cosmetics still render.
Fixed
- The enderium trim palette shipped value-inverted in 0.2.1 (highlights and shadows swapped); legacy trims now shade correctly
- The upgrade template sprite had 8 stray transparent pixels and an off-style gray plate; repaired and recolored
- Enderium ingot and raw enderium re-drawn on proper vanilla silhouettes (the old ones read undersized/pearl-like)
Install: NeoForge for your version, jar in mods/
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:KrSZ0ev8:IXQwecvz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KrSZ0ev8:IXQwecvz"
}

