All versions
0.0.2-1.21.1
Release
Better Combat Particle 0.0.2-1.21.19 months ago 75.8K
Compatibility
Minecraft: Java Edition
1.21.1
Platforms
Fabric
Forge
NeoForge
Supported environments
Client and server
Required content
Changes
- Change data settings to be on client instead. Because there is why spend all of server connection on particle rotation data and color. this should fix the particle spawing problem between host player and client player.
- location folder from data to assets.
- added color string "remove" to set alpha to 0. so you can hide the particle for some enchantment or custom weapon. example: "color_hex": "remove" , "color_hex_sec": "remove"
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:Nc3f2m7t:ei0rju1s"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Nc3f2m7t:ei0rju1s"
}


