Tags
Creators
Details
4.4.2
Compatibility
Changes
Fixed particle rendering crash on MC 1.21+ The ChestEffectsTask was calling world.spawnParticle() with offset/extra parameters that MC 1.21+ no longer accepts for certain particle types without explicit ParticleData. This caused the beacon beam effect to throw IllegalArgumentException: missing required data class java.lang.Float every tick.
What changed: Simplified END_ROD particle spawning to use single-parameter method
Removed problematic offset/extra float parameters that require ParticleData in 1.21+ Beacon beam effect now renders correctly without console spam Technical details:
// Before (broken in 1.21+): world.spawnParticle(Particle.END_ROD, x, y, z, 1, 0.1, 0.0, 0.1, 0.0f);
// After (works everywhere): world.spawnParticle(Particle.END_ROD, x, y, z, 1);
Affected versions: MC 1.21 - 1.21.4 Recommended for all Paper/Purpur 1.21+ users experiencing console warnings
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:AOhB9MQL:uWZcwgY4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AOhB9MQL:uWZcwgY4"
}

