All versions
1.0
Release
Visuality: Reforged 1.0 for 1.18.24 years ago 227.1K
Uploaded by
Compatibility
Minecraft: Java Edition
1.19–1.19.2
Platform
Forge
Supported environments
Client-side
Changes
Visuality: Reforged 1.0
Changes
- Moved most particle config to new json config system Particle Emitters.
- Moved all particle colors to extra parameters instead of using velocity.
visuality:sparkleis now colorable, all use cases are tweaked to proper color.- Hit particles now only spawn from melee attack.
- Hit particles now generates more with damage enchantments.
- Made
minecraft:wandering_traderto spawn emerald particles on hit by default. - Modified most particles' spawn interval due to code changes.
- Added Spanish-Mexican(es_mx) localization by @CerealConJugo.
Particle Emitters
- Particle Emitter configs are located under
/config/visuality/particle_emitters/folder, currently there areblock/ambient.json,block/step.json,entity/armor.jsonandentity/hit.json. - Particle Emitters can also be loaded via resource packs, located under
assets/<namespace>/particle_emitters/folder with the same name. - Particle Emitters in resource packs accept a
conditionsfield like recipes which uses Forge's loading condition system, useful for loading mod specific stuffs. - Particle Emitters reload along with resource packs (use F3+T for reload), Particle Emitter configs loads first.
- Particle Emitters from resource packs can only merge their
entriesfield, other fields is only available for Particle Emitter configs. - Further information about the format will be post on the GitHub Wiki later, reference the default Particle Emitter configs for now.
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:V86m03RC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:z13R7Et1:V86m03RC"
}

