All versions
1.2.3
Release
Clean View v1.2.3last month 2,381
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Required content
Any compatible version
Any compatible version
Changes
CleanView 2.0
Version 1.2.3
π Changes
- Reintroduced distance-based particle filtering
- Added adjustable Particle Filter Distance for improved visibility control
- Added Particle Opacity mode
- Added Particle Opacity (%) slider (0β100%)
- Added separate Opacity Distance setting
- Eating & Potion Effect Particle Visibility now correctly scales from 0β100%
- 100% = Vanilla/default particle amount
- Lower percentages now properly reduce particle density instead of randomly hiding particles
- Improved low-percentage behavior for a much cleaner first-person experience
π Improvements
- More accurate particle reduction system
- Better visibility of nearby players' potion effects
- More consistent filtering across supported particle types
- Particle Opacity can reduce visual clutter without fully removing particles
- Opacity mode only applies when enabled
- Enhanced compatibility with Shaders & Performance Mods
- Ultra-lightweight with zero FPS impact
βοΈ Settings
- Eating Particles:
0β100% - Potion Effect Particles:
0β100% - Particle Filter Distance: Adjustable
- Particle Opacity: Enable / Disable
- Particle Opacity:
0β100% - Opacity Distance: Adjustable
π Notes
- 100% displays the vanilla/default amount of particles.
- 50% noticeably reduces particle clutter while preserving visibility.
- 10% provides a very clean experience with minimal distraction.
- 1β5% keeps only a tiny amount of particles visible for essential feedback.
- 0% completely hides the selected particle type.
- Opacity Mode lowers particle transparency instead of fully removing particles.
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:HeQ9uevZ:Tcwk9GAw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:HeQ9uevZ:Tcwk9GAw"
}

