Tags
Creators
Details
1.1.237
Compatibility
Required content
Changes
DMZ Ragnarok 1.1.237
Mostly a large piece of work for people running several linked servers. On a single server almost all of it is inert, so the short version for everyone else is: a saga difficulty change, and some fixes.
Everyone
- Hard saga difficulty now requires having prestiged at least once. The option is shown locked with the reason until then. This only applies where the prestige system is actually running: if your server does not run prestige, hard difficulty is available exactly as before. A saga already in progress on hard is untouched.
- A handshake line was logged on every join, which on a network meant every server switch. It is now quiet unless debug logging is on.
For networks of linked servers
These do nothing at all on a single server, which keeps its existing behaviour on every one of them.
- The auction, bounties, mail, trading and warps now work across servers. Previously each server had its own: listings and bounty pools were stranded where they were created, mail arrived only on the server it was sent from, warps set in one place were invisible everywhere else, and you could not see a player on another server to trade with them at all.
- Backpack contents travel with the backpack. Sophisticated Backpacks stores contents per server, so a backpack that changed hands or changed servers used to open empty.
- Raids and tournaments are now network events. One server is chosen to host, weighted by how many players are on each, announcements reach everybody, and joining sends you to wherever it is running.
- Supporter perks, staff hours, event windows and airdrops are shared rather than per server. Staff hours are summed across servers rather than fragmented.
- Cooldowns no longer reset by changing server, including the hakai and dungeon re-entry cooldowns, which could previously be bypassed by hopping.
- Staff vanish, form cosmetics and quest repeat timers now follow you between servers.
Fixes
- Mail could be lost. Reading marked a message read before it was shown, so disconnecting, changing server, or a crash in that moment discarded it, and reading everything at once could discard a whole inbox. A message is now only marked read once it has actually been delivered.
- A guild raider who disconnected mid-raid could be handed an emptied inventory if they reconnected to a different server, while their real items stayed behind. Their belongings now travel with them and are returned wherever they log back in.
- Several stores could resurrect deleted entries after a restart, including paid-out bounties, read mail and deleted personal warps.
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:kTBhStny"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bLplVEcb:kTBhStny"
}




