Links
Tags
Creators
Details
26.1.2-1.0.0
Compatibility
Changes
Endrise v1.0.0 — The Way Home
The covenant closes its circle. After your gear, your drops, and everyone else's graves, it's your turn.
New
- The Homeward Pearl. An ender pearl wrapped in four Void Petals and four enderium ingots. Use it anywhere, in any dimension, and arrive at your own respawn point: bed, anchor, or world spawn if the bed is gone, resolved by vanilla's own rules. Consumed on use (creative keeps it), five-second cooldown, ender chime at both ends. It dismounts you first, it never spends a respawn anchor charge, and it can never roll the credits: that belongs to the portal.
- Enderium is quietly awake. Ore and Blocks of Enderium shed slow reverse-portal motes from any face that meets open air, with a rare resonant hum. A vein glimmers into the cave before you can read its texture.
- The advancement tab is complete. Eight nodes walking the whole arc: Buried Light, Deeper Than Diamonds, Bound, The Tier Above, Nothing Is Lost, There and Back, Someone Was Here, The Way Home.
Fixed
- The advancement tab background rendered as the missing-texture checkerboard on 1.21.1 (a form mismatch that had been there since 0.4). It shows the End now.
- Using the pearl while riding on 1.21.1 would have wasted it; it now dismounts you first, like chorus fruit.
The 1.0 candidate
This build is feature-complete: the arc Endrise set out to tell is told. It ships to the alpha channel for a one-week soak; if nothing breaks, the listing gets promoted to full release with this exact jar. If something does break, say so loudly in the issues: spacing, loot rates, bloom density, draught duration, and the pearl recipe cost are all still open to argument.
Both jars: MC 26.1.2 (NeoForge 26.1.2.87) and MC 1.21.1 (NeoForge 21.1.244).
Thank you for dying in the End with us. Nothing was lost.
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:3Fim3QPm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KrSZ0ev8:3Fim3QPm"
}

