Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 months ago
Updated 4 days ago
All versions
1.1.534
Release
DMZ Ragnarok 1.1.534last month 95
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
A startup crash on servers running Lootr, and everything from 1.1.532.
Startup crash
- The server no longer fails to start when Lootr is installed. Both mods hooked the same spawn protection check and only one of them can hold it: whichever lost was dropped, and losing was treated as fatal rather than something to carry on from. The load order can change for something as small as a file being renamed, so this could have struck at any time, not only on this update.
- Known limitation on servers with Lootr: dragon ball totems inside the spawn protection radius cannot be opened there for now. Restoring that alongside Lootr needs a different hook and is coming next. Servers without Lootr are unaffected.
Characters rolling back
- A tournament fighter is no longer saved as your real character. Nothing was ever lost: your real character was held safely the whole time.
- Prestiging is saved immediately, so a crash right after no longer takes it back.
- Your character is saved every few minutes while you play, instead of only when you change worlds, switch slots or log out cleanly.
Items
- Fusing and then changing worlds no longer duplicates your items. Both halves of a fusion are protected for the move, not just the one who triggered it.
Fixes
- Portals that send you to spawn reach the spawn that was set.
- Ki shields no longer shove masters, quest givers, raid and tournament hosts, prestige NPCs, the shrine dragon, planet defenders or the Saiyan town villagers. Players, fighters and hostile mobs are still thrown as before.
- The defiled radar matches what is actually out there.
- Dragon ball totems are recognised by the totem itself, not only by the server's record of it.
Network
- Logins and world changes survive a slow moment: a connection was dropped after 30 seconds of silence even though the login itself was allowed two minutes. Server owners who set their own value keep it.
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:YJxqitZZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bLplVEcb:YJxqitZZ"
}

