All versions
0.23.0
Release
0.23.0 — The dragon comes alive (+ Minecraft 26.3)4 days ago 14
Compatibility
Minecraft: Java Edition
26.1.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
0.23.0 — the dragon comes alive, and Minecraft 26.3
Now on Minecraft 26.3 (alongside 26.1.2 and 26.2). Each file targets one Minecraft version — this one is for Minecraft 26.1.2.
🐉 Dragon form
- Its own animation rig with real keyframe animations: idle, walk, run, sit, lie down, take-off, flight, glide and landing — toes spread on each step, the tail sways on its own.
- Wings and legs actually move now. Most of the dragon's animation tracks were in a shorthand the game silently ignored, so it never flapped or walked. Fixed, and locked by a test.
- Wings on their own track — they stay folded while the dragon roars, gets hurt or bites on the ground. Eyes that blink.
- Lie down: Sit cycles stand → sit → lie down → stand (menu, hotkey or right-click).
- Hover: release jump in the air and the dragon holds its altitude instead of sinking.
- You sit on it: the rider sits in the saddle, stays on the back while banking or diving, and the neck dips while ridden so the head doesn't block your view.
- A body its size: 1.9 × 1.9 collision box that grows with level — no more one-block doors.
- Safer dismount: a plain right-click with a saddle no longer drops you mid-air — use Sneak.
🔧 Technical
- The 26.2 file now declares
>=26.2 <26.3; on 26.3 use the 26.3 file. - 26.3: loot tables, advancements and world-gen data rewritten for the new data format; the 26.3 build was verified on a dedicated server (world loads, all 20 loot tables, wild bushes generate).
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:s9yDUMze:UNjp4b6x"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:s9yDUMze:UNjp4b6x"
}

