Tags
Creators
Details
1.0.0+fabric
Compatibility
Required content
Changes
Its own mod at last. The Hardcore Nuzlocke and Soul Link rules have been running inside Routes for a while; from here they live in their own jar. It is 1.0.0 and not a beta: the code is the same one people have been playing, only in a different box.
Install this next to Routes 1.0.33 or newer. Routes is a required dependency — the "one catch per zone" rule is defined against its zone model, so the routes, areas and towns it generates are the capture zones. 1.0.33 is the version that learned to host this add-on, so the loader will ask for at least that.
What is in it
- ☠️ Hardcore Nuzlocke — one catch per zone, permadeath with heal-blocking, mandatory nicknames, shiny clause, a configurable Defeated-Catch window, and whiteout handling.
- 🎲 Starter randomiser, with filters for legendaries, paradox forms and Ultra Beasts.
- 📈 Level caps and EXP tuning, plus battle-mechanic restrictions (Mega / Gigantamax / Z-Moves / Terastallisation).
- 🤝 Soul Link co-op — linked parties share fates, and a lone-combat block keeps anyone from grinding ahead alone.
- 🧩 Its own NUZLOCKE tab on the create-world screen: pick the run once, then play.
If you were already playing with Routes
Nothing is lost and there is nothing to do. Your world keeps its zone log, its deaths and its soul links: the save data is read from the same place it always was. Your settings come across too, both the global ones and the per-world rules.
Routes notices this mod and stands down, so the rules run once — not twice. Keeping Routes alone also keeps working exactly as before.
One rename you will see: Soullock is now Soul Link, its real name. The command is
/nuzlocke soullink.
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:wHlszYZN:gR3HU9dc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wHlszYZN:gR3HU9dc"
}

