All versions
1.10.1
Release
Spore:SRP! 1.10.121 hours ago 99
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Version 1.10.1 – Changelog
Note: This version is still in a testing phase and may disrupt game difficulty balance. If you have any feedback or issues, please report them on the CurseForge comments page.
Changes
- Extra spawns are now rolled independently per tier (small / medium / large / boss) instead of a single shared roll.
- Organoids are no longer globally banned from natural spawning; they are filtered per spawn pool instead, while intentional organoid spawns (mound ring, hivemind skills) are untouched.
- Infected biome spawn table restored to all 44 entries (including the 8 calamities) and rebalanced to a total weight of 422, with calamities at roughly 1.9%.
- Phase 10 now also blocks other mods' mobs from spawning naturally in normal biomes.
- Phase 1 mound ring now spawns level-4 mounds.
- Battle base spawns raised from 4 to 6, and the per-wave cap raised from 30 to 40.
Fixes
- Fixed the infected biome failing to load entirely due to a byte-order mark in the JSON, which caused several "no spawns" reports.
- Fixed the stage upgrade countdown disappearing or becoming abnormally long after switching dimensions; existing saves will self-heal on first load.
- Fixed wrong entity ids in battle pools that silently resolved to pigs (
gargoyl→gargoyle,hinderburg→hindenburg), and added an entity-id existence guard. - Fixed battle spawns still being rejected in daylight even with the sunlight bypass enabled.
- Fixed entity conversion to discard entities immediately on the client.
Notes
- We are still investigating a report that infected mobs only spawn at the edge of the infected biome. If you encounter this, please check the F3
Biome:line at the centre of the infected area and report it on the CurseForge comments page.
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:a5dtLyoL:HYpGOzG5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:a5dtLyoL:HYpGOzG5"
}

