Links
Tags
Creators
Details
All versions
2.5.0
Release
Infused Mobs 2.5.03 months ago 17
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client and server
Required content
Unavailable version
Changes
[2.5.0] - 2026-07-27
Added
- 26 unit tests (up from 21) — new config validation tests for
abilityCount,spawnChance, null tiers - Config validation hardened —
isValid()now checks all tier fields; old configs fall back to defaults
Changed
- Unified ability pool — abilities drawn from all trigger types mixed together
- Cinder: 1 ability, Shade: 2, Doom: 3 (was per-type HURT/TICK/DEATH counts)
- Spawn rates increased — Cinder 40%, Shade 20%, Doom 10% (was 10%/5%/2.5%)
- Debuff pass — all HURT/TICK effects are level I, 3s duration (was II–III, 5s)
- Chill no longer hardcoded to level III — uses config amplifier like everything else
- Version bump to 2.5.0
Removed
BY_TRIGGERindex (dead code — populated but never read since unified pool)- Redundant shuffle in
getRandomAbilities - Stale metadata (fabric.mod.json still referenced Ember/Surge/Tempest)
Fixed
- Config validation missing
abilityCountcheck — old configs silently got 0 abilities
[2.4.0] - 2026-07-26
Added
- Persistent tier state (
TierSavedData.java) — mobs keep their tier (or rolled-nothing state) across world reloads - Despawn cleanup (
EntityRemoveMixin) — tier tracking cleaned up when mobs despawn, not just on death - Immutable collection safety — codec deserialization wrapped in
HashMap/HashSetto prevent crash
Fixed
- Duplicated nametags —
mob.getName()was reading previously-set custom names; now usesgetType().getDescription()for the base entity name - Duplicated announcement — same fix in
MobHurtTriggerchat message
Changed
- No particles on TICK abilities — status effects on mobs (Strength, Resistance, etc.) no longer show particles
- Combust quieted — silent area damage instead of explosion (no particles, no block damage)
- Version bump to 2.4.0
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:J3NKKD4Y:vd2V5ZCA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:J3NKKD4Y:vd2V5ZCA"
}

