1.6.1
Compatibility
Changes
๐ Update v1.6.1 - "The Fair Chase" (Hotfix)
A critical balance and stability patch addressing issues found in the 1.6 "No Dimension Is Safe" update.
โ๏ธ Gameplay Balance: The 100-Block Rule
Fair Respawn System: I have fixed a major balancing issue where Hunters would respawn almost instantly on top of the player.
Guaranteed Head Start: Hunters now respawn at a tactical distance of 80โ120 blocks from the player. I've implemented a new circular spawn algorithm to ensure they never spawn "in your face" again. This finally gives players a well-deserved window to heal and regroup after a kill.
๐ Global Localization Fix
The "Trap Message" Bug: I resolved an oversight where trap-related phrases (hunter.msg.trap) were only present in Russianand Ukrainian files.
Community Thanks: Huge thanks to our Discord community members who quickly spotted and reported this issue! Your screenshots helped me find the cause and release this fix immediately.
Universal Support: I have added the missing translation keys for the other 8 languages. Players using English, French, German, Spanish, Polish, Portuguese, Korean, or Japanese will no longer see technical string IDs in chat.
๐ Bug Fixes & Optimization
Stuck Logic Refinement: I optimized the hunters' behavior โ they are now more efficient and "cleaner" when breaking blocks to get unstuck, reducing unnecessary item drops and lag.
Portal Pursuit Gap: Adjusted the arrival distance when hunters follow you through a portal to match the new "Fair Chase" logic.
Performance: Optimized tracking radius to reduce CPU load during long-distance pursuits.
โ๏ธ Technical Note
I apologize for the localization issues in v1.6. It was a classic developer oversight where I only tested new features in two languages. v1.6.1 officially makes the mod globally stable.
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:6yAseuid:NZtoP2wX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6yAseuid:NZtoP2wX"
}

