Tags
Creators
Details
Licensed GPL-3.0-only
Published 3 months ago
Updated 4 days ago
All versions
1.1.420
Release
DMZ Ragnarok 1.1.420last month 28
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
DMZ Ragnarok 1.1.420
Fixes server freezes and join timeouts, getting stuck when travelling between servers, and quest progress lost on server hops.
Server stability
- No more multi-second server freezes and "unable to connect" when joining. An Iron Furnaces bug duplicated furnace entries in player data until some files reached tens of megabytes. Duplicates are now removed whenever that data loads or saves, so it cannot grow again.
Travel between servers
- Players who kept getting sent back to the open worlds can reach the SMP again, including players who were stuck in space. Homes, personal warps, warps and /tpa all land where they should.
- Leaving space returns you to where you took off, even when you flew up from another server.
- /mwtp works from any server to any dimension, handing you to the server that hosts it.
Quests and parties
- Completed quests you have not claimed are no longer reset when you change servers.
- Changing servers no longer changes your quest difficulty to your party leader's.
TP boosts
- Global TP boosts keep their remaining time through network restarts instead of running out while the servers are down.
- TP boost gems show a potion effect while active, and only one can be active at a time. A gem is not used up if another boost is still running.
Staff tools
- /planet info and /planet look show the planet id to staff (click to copy), plus a new /planet search <name> and tab completion for /planet destroy and restore.
Requirements
- Minecraft 1.20.1, Forge 47.4.20 or newer
- DragonMine Z 2.1.3, GeckoLib and Curios (required)
- 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:NHqNdWF1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bLplVEcb:NHqNdWF1"
}

