Links
Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 5 days ago
All versions
3.0.0
Release
[NeoForge]Visuality: Reforged 3.0.0 for 1.21.115 days ago 64
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Changes
Visuality: Reforged 3.0.0
Added
- Add a configurable RGB color for slime blob particles under
slime.colorin the client config. - Add
#namespace:tagitem selectors to entity armor particle-emitter entries while keeping existing item ID entries compatible. - Add distinct cold and warm feather hit particles for the matching chicken variants on Minecraft 1.21.8.
- Add German, Argentinian Spanish, European Spanish, French, and Polish translations, and translate the new slime color option.
Changed
- Blend rain water-circle colors using Minecraft's client biome color blending instead of using a single raw biome color.
- Update the emerald particle texture from Fabric Visuality and refresh the normal chicken feather texture on Minecraft 1.21.8.
Fixed
- Prevent non-living client entities such as Ender Dragon parts and interaction entities from entering the living-entity hit-particle path (#32, #34).
- Keep malformed particle-emitter JSON files unchanged, log a clear error, and retain the last valid runtime configuration instead of silently replacing files with defaults (#25).
- Reduce the default soul-sand and soul-soil ambient particle rate and add an optional per-entry
intervalsetting (#13). - Spawn armor sparkles during living-entity ticks instead of only attempting them when the wearer takes damage (#23, #36).
- Add
#namespace:tagblock selectors and use NeoForge common ore tags so compatible modded ores, including GTCEu ores, can sparkle (#24). - Apply resource-pack emitter JSON without a
conditionsobject instead of skipping it.
Build and publishing
- Upgrade Mod Publish Plugin to 2.1.1, add an opt-in
-PpublishDryRun=truevalidation mode, and declare the project as client-only for CurseForge and Modrinth. - Upgrade the Gradle wrapper to 9.2.1 and ModDevGradle to 2.0.143.
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:z13R7Et1:9dXZfZ5O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z13R7Et1:9dXZfZ5O"
}

