1.3.1
Compatibility
Changes
Hive Collective - v1.3.1 Changelog
This release delivers full native support for the Nether dimension, alongside targeted gameplay refinements, critical bug fixes, and stability optimizations to extend the mod’s core mechanics across all playable dimensions.
Core Feature: Full Nether Dimension Compatibility
- Hive Collective events now trigger natively within the Nether dimension, extending the mod’s signature night-time threat system beyond the Overworld and the End.
- Implemented dimension-aware spawning logic tailored to the Nether’s unique terrain generation. The system automatically searches for valid, navigable spawn positions within the Nether’s standard vertical range (Y=33 to Y=96), ensuring mobs generate on solid, traversable blocks rather than in lava, void spaces or unpathable terrain.
- Light-level spawning restrictions are automatically relaxed for the Nether, eliminating unnecessary spawn failures caused by the dimension’s inherent ambient fire and block lighting. This adjustment preserves consistent event intensity while respecting the Nether’s environmental properties.
Gameplay and Spawning System Refinements
- Removed all dimension-specific spawn restrictions. Hive Collective events can now initiate and operate normally in any non-peaceful Minecraft dimension, creating a uniform survival challenge across all player exploration spaces.
- Optimized the global spawn position validation algorithm. The updated system reduces failed spawn attempts in complex terrain, ensuring each scheduled mob wave executes reliably and maintains the event’s intended pressure curve.
- Revised the default mob spawn pool with progressive difficulty scaling. The default configuration now introduces tougher mobs at predefined event milestones, delivering a natural difficulty progression without requiring manual user configuration edits.
Configuration and Stability Improvements
- Restructured configuration key naming conventions for improved readability and consistency. All legacy configuration files from v1.3.0 remain fully compatible, with automatic migration support built into the new release.
- Removed redundant world-join validation routines, reducing mod initialization overhead and improving server/client world load performance.
Critical Bug Fixes
- Fixed residual event state persistence issues that could leave partial event effects active after the Hive Collective night concluded.
- Corrected edge-case spawn failures that occurred in high-elevation and cave-heavy terrain across all dimensions.
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:lBdzeWMO:JYHX0bfv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lBdzeWMO:JYHX0bfv"
}

