Links
Tags
Creators
Details
26.1.2-1.0.1
Compatibility
Changes
Endrise v1.0.1 — The Covenant, Explained
The 1.0 candidate, now with JEI integration.
New
- JEI support. Every Endrise recipe already appeared in JEI (they're all vanilla types); now the covenant explains itself too. Info pages for the mechanics that aren't recipe-shaped: where Enderium Ore hides and how it glimmers, what the void gives back, how End deaths become Mourning Blooms, what the Draught and the Homeward Pearl actually do, what the Upgrade Template's renewable source is, and everything enderium gear carries (Soulbound, pearl-damage negation, void return). Fully optional: nothing changes without JEI installed.
The soak
This replaces v1.0.0 as the 1.0 release candidate; the one-week alpha soak restarts from today. Same rule as before: if it soaks quiet, this exact jar gets promoted to full release.
Both jars: MC 26.1.2 (NeoForge 26.1.2.87, JEI 29.x) and MC 1.21.1 (NeoForge 21.1.244, JEI 19.x).
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:1msYiMd3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KrSZ0ev8:1msYiMd3"
}

