Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 4 years ago
Updated 2 days ago
All versions
0.7.1+1.20.1-fabric
Release
0.7.1 for 1.20.1-fabric2 days ago 152
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Changes
0.7.1
Fixes & Improvements
- Fix particle texture will be missing until game restart, when change custom footprint particle resourcepack and reload in game.
- Fix saving config will crash the game that causing by configScreen push invalid value to IO system.
- Add some validator to configScreen. Now 'Save & Quit' button will be disabled if there is invalid value until you correct it.
- Fix boat will spit out a lot of particle when placed.
- Refactor list lookup method for better performance, readability and others.
- Now mob list can input tags starts with '#' symbol.
- Add an option to limited max generate distance of our particles. Default is 64 blocks.
- Changed particle direction always rely on entity facing instead of their movement direction if it has.
- Fix '#c' tag in default list cannot be matched on older MC version by replacing them to specific block name. (i.e. composter, froglight)
- Remove accesswidener file that no longer in use from Forge build.
- Remove some entity and block id/tags from default list on old MC version they don't exist.
- Improved performance of self-hosted particle system.
Large internal improvements that clean up a lot of dumb code I wrote before 0.6.0...
- Fix watermark will generate in air.
- Fix watermark will randomize its direction.
- Fix watermark not controlled by blockHeightOffset.
- Fix mixin tick will run meaningless on integrated-server.
- Refactor boat & minecart mixin, improved their performance.
- Improved code readability and performance of generator.
- Improved customPrint pick up performance.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:xZQOoOaY:UIlwhHXX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xZQOoOaY:UIlwhHXX"
}

