2.1.0
Compatibility
Changes
End Update — v2.1.0
Headline of this release: complete building-block sets for every End wood (and for End Spike Crystal), a proper elytra-style gliding pose for Void Levitation, and a batch of guide-book and creative-menu polish.
Added
Complete building sets
Every End wood now has a full block set, so you can build from foundation to rooftop entirely in End materials:
- End, End Jungle, and Endium each gain: stairs, slabs, fences, fence gates, doors, trapdoors, buttons, and pressure plates.
- End Spike Crystal gains stairs, slabs, and panes.
- Every one has a proper crafting recipe, crafted exactly like its vanilla counterpart (planks → stairs/slabs/etc., 6 crystal → 16 panes, and so on).
Void Glide pose
- While gliding under Void Levitation (falling + holding forward), your character now renders in the elytra-style horizontal flight pose — so gliding finally looks like flying.
- Purely cosmetic: it's applied only for rendering and has no effect on movement or physics. Works for everyone you see gliding, not just yourself (press F5 to watch your own).
Changed & Improved
End Update Compendium (in-game guide)
- Now documents the new building block sets.
- Screenshots fixed — they no longer appear stretched or squished, and fill their frame cleanly with no empty borders.
- Trimmed a few long entry names so they fit neatly in the book without overflowing.
- Title tidied up to "End Update Compendium."
Creative menu ordering
- The End Update creative tab is now laid out in sensible groups — terrain & plants, then each wood set in full, decorative blocks, End Spike Crystal, the Enderite line, the Ambynite line, hammers, and miscellaneous — instead of raw insertion order.
Fixed
- The survival guide-book recipe (Book + Ender Pearl) used an ingredient format that failed to load on 1.21.1 and produced no recipe — now corrected, so it crafts properly.
Requires Minecraft 1.21.1 on NeoForge. The in-game guide still uses the free, optional Patchouli mod — End Update runs fine without it.
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:94HlrSYI:ejZFUOSt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:94HlrSYI:ejZFUOSt"
}

