Creators
Details
1.0.1
Compatibility
Changes
Fix: Cobblemon DiscParticleEmitterShape crash (bound must be finite and positive)
Root cause: Cobblemon's DiscParticleEmitterShape.getNewParticlePosition() calls Random.nextDouble(radius) where the radius is resolved from a MoLang expression (e.g. q.entity_radius * 0.95). When the entity radius evaluates to
0, negative, or NaN, nextDouble() throws IllegalArgumentException because it requires a finite positive bound. This affects ~10 particle files that use emitter_shape_disc without clamping the radius (psychic_target,
dragonclaw_aura, shrooms, bodyslam_actor_dust, superfang, waterpulse, infestation, etc.).
Fix: A client-side Mixin in the CobblemonFieldMoves mod that redirects the Random.nextDouble(bound) call inside getNewParticlePosition() to return 0.0 when the bound is invalid, instead of crashing.
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:mMymctME:DHlCAiYZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mMymctME:DHlCAiYZ"
}

