Tags
Creators
Details
1.1.485
Compatibility
Required content
Changes
DMZ Ragnarok 1.1.485
Fixes the crash that took whole worlds down while a dungeon floor was building, stops rewards being lost when you already carry the same item, and closes two ways of resetting the dungeon timer.
Crashes and server health
- Entering a new dungeon floor no longer freezes and kills the server. Building a floor loaded each of its chunks on the main thread and generated them there, so a floor on fresh ground could stall a world past its own watchdog and drop everyone onto another one. Floors now build their chunks in the background and wait for them.
- Backpack contents settle properly after a world change. The check that confirms a backpack arrived ran ahead of the save it was waiting for, so it never tidied the copy left behind.
Fixes
- Items are no longer lost when you already carry some of the same item. Rewards that only partly fitted (dungeon gems, crate, raid and tournament rewards, floor tickets, auction and trade returns, guild vault withdrawals, senzu, runes and kits) kept what fitted and quietly destroyed the rest. The remainder now drops at your feet.
- The dungeon timer cannot be reset by leaving and coming back, whether with /back, /home, /spawn, a death, or by switching between the two overworlds.
- Shift right click works on the gravity chamber again. Opening the gravity and range menu needed both hands empty.
- Stat discount gems take effect on the first use, and buff gems no longer stack into a bigger discount: the strongest one running counts.
- A tournament character can always be left:
/rg tourney cancelcharacter, or/rg tourney forceexit <player>for staff.
Requirements
Minecraft 1.20.1, Forge 47.4.20 or newer, with DragonMine Z 2.1.3, GeckoLib and Curios. Needed on both the client and the server.
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:O3VNvZrS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bLplVEcb:O3VNvZrS"
}

