1.1.0
Compatibility
Changes

This update introduces the strongest tier ever added, a fully structured End-game progression, and a boosted exploration loop that finally makes the End feel dangerous again.
1.1 officially elevates the mod from "extra items" to true progression expansion.
πͺ βοΈ New Ore: Enderite
- Generates only in the End dimension, embedded inside end stone.
- Significantly rarer than Netherite β players must explore smartly, not randomly (it may appear in surface mostly).
- Designed as the final material for late-game builds.
Why Enderite?
Because the End needed a real reason for players to return β something dangerous, rewarding, and worth the grind.
π£ π‘οΈ New Gear Tier: Enderite Equipment
Enderite Sword
- Higher base damage than Netherite.
- Designed for players who want reliable late-game melee.
Enderite Pickaxe
- Faster mining speed than Netherite.
- Massive durability pool for long expeditions.
- Optimized for future mod blocks and custom materials.
Enderite Axe
- More damage and swing power than Netherite.
- Combines combat strength with insane chopping efficiency.
- Perfect hybrid tool for aggressive playstyles.
πͺ π§ New: Enderite Upgrade Template
- Required to upgrade Netherite β Enderite using a Smithing Table.
- Craftable :
- Encourages proper progression instead of speed-running top tier gear.
π Template Duplication
To stay consistent with vanilla rules and keep upgrades meaningful:

β Balanced. Expensive. And fully aligned with vanilla's "final-tier" logic.
βοΈ Balancing Notes
- Enderite gear is powerful but not busted no god-mode nonsense.
- Durability, mining speed and damage have all been tuned for fairness.
- Enderite is intentionally scarce to avoid rushing to max tier.
- Template rarity ensures players must earn their upgrades.
π§© Final Comment
Update 1.1 brings Eagleβs Expansion into true full release quality.
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:mpR4KmrO:YINbZacG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mpR4KmrO:YINbZacG"
}


