All versions
1.8.0-mc1.20.1
Release
SuperFancyClouds: Rearchitected 1.8.0-mc1.20.14 months ago 32
Compatibility
Minecraft: Java Edition
1.20–1.20.1
Platforms
Fabric
Forge
Supported environments
Client-side
Server-side
Client and server
Required content
Changes
Grand Introduction of SFCR 1.8
We're excited to bring you this major update, which includes several new features, a handful of fixes, and numerous optimizations. We highly recommend upgrading.
Core changes
- Fully rewritten from v2.0 (major internal rework).
- Ported 1.21.6+ vanilla mesh build (integrated normal/circular culling).
Features
- Added custom dimension support.
- Added cloud bottom dim.
- Added night density slider.
- Added "No Cloud, No Rain" feature.
- Added Distant Horizons compatibility (manual enable required).
- Added Particle Rain compatibility (manual enable required).
Fixes
- Fixed infinite loop when performing a long-distance teleport.
- Fixed dawn/dusk blush color flicker.
- Fixed excessive thread creation causing severe lag.
- Fixed occasional weather detection failure leading to density flicker.
Optimizations
- Increased cloud top density during rainfall.
- Adjusted network and event hooks.
- Simplified server-side commands and behavior.
- Reworked the config, config screen, and config I/O system.
- Reworked server synchronization.
- General performance and stability improvements.
Known Issues
- Position culling works incorrectly when close to clouds.
- Mesh rebuilds when the Y-coordinate changes have a slight delay due to concurrent updates, and cloud height is not sufficiently accurate.
Note
- Particle Rain compatibility requires Particle Rain version v4.0.0-beta.5. As this mod is in beta and frequently rework (as our, well...). This compatibility may expire soon. New update will come accordingly at that time.
Optional dependencies
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:Hoop89kN:r3HAQxDK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hoop89kN:r3HAQxDK"
}





