1.1.1
Compatibility
Changes
š„ SporeWithin v1.1.1 ā "Nether Gate" Hotfix "This code crashes the server upon entering the nether" ā Thanks to the user who dropped this in the comments. You were 100% correct, and the bug is now eliminated. We focused too much on testing the Overworld core mechanics and overlooked dimension scaling. In version 1.1.0, the newly implemented skybase detector and heightmap surface scanner tried to scan for "open daylight" and surface layers straight through the solid bedrock ceiling at Y=127 in the Nether. This triggered a critical dimension exception and crashed the server on the spot. š Changelog v1.1.1: [Fixed] Nether & End Dimension Server Crashes: Skybase altitude checks, smog triggers, floating foundation scans, and mound burrowing routines are now strictly bound to Level.OVERWORLD. The system will no longer execute heightmap or canSeeSky() queries in non-overworld dimensions, permanently fixing portal crashes. Portal Transition Entity Safety: If a player enters a nether portal during an active raid, the server no longer hangs or leaks ghost entities. The assault squad correctly detects the dimension change, drops the target tracker, cleans up action bar debuffs, and initiates a clean burrow retreat. Dimension-Safe Spawn Resolver: Implemented a findSafeDimensionSpawnPos fallback routine for non-overworld environments. It resolves spawn coordinates using local block checks for solid footing and a 3-block vertical headroom clearance, bypassing heightmap calculations entirely. Nether Entity Isolation: Prevented Nether-specific mobs (Piglins, Hoglins, Wither Skeletons) from triggering hidden vessel infection mechanics or attempting to generate parasite mounds inside the Nether or End.
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:dIABKoP3:TWPc3egV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dIABKoP3:TWPc3egV"
}

