Tags
Creators
Details
Licensed ARR
Published 2 months ago
Updated 5 days ago
All versions
1.1.537
Release
DMZ Ragnarok 1.1.5375 days ago 267
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
Models
- Ragnarok character models no longer stand with a frozen chest. 86 of the 376 models named their torso differently from the rest of the rig, and the game only ever drives one particular name, so on those models the chest never animated at all while the head, arms and legs did.
- Their upper bodies now turn with them. On the same models the torso was attached above the waist rather than below it, so it sat out every turn the waist made while the head and arms took the full amount. The arms swung around a chest that stayed where it was, which read as the body facing the wrong way. This affects both the Ragnarok NPCs and any race using one of these models.
- Both are corrected as the model is loaded, so nothing needs redownloading.
Titles
- New title: Grand Zeno. It carries the God of Destruction and the Angel movesets at once, rather than making you choose. Its tag shows after your name in magenta.
- The ability key raises and lowers both self buffs together for a Zeno. They draw on the same energy, so holding the pair costs twice what either costs alone and a full bar carries it about ten seconds.
- Fixed for existing titles too: anyone holding more than one role could lose abilities they were entitled to, because the checks asked which energy bar was on screen rather than what the player actually held. The Angel staff and the angelic state were both affected.
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:bLplVEcb:dRSQ6bDD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bLplVEcb:dRSQ6bDD"
}

