0.0.3
Compatibility
Changes
Version 0.0.3 is a major leap forward for WeatherPhysics: storms now form, evolve, and dissipate dynamically, rather than simply acting as a global weather effect.
โ๏ธ Volumetric Clouds & Cloud Lifecycle
- ๐ Volumetric Cloud System: Clouds now have realistic volume, varied shapes, and large dynamic structures.
- ๐ฑ Growth Stages: Clouds independently evolve over timeโsome grow, others weaken and fade away.
- โ๏ธ Cumulonimbus Formation: Select clouds can now mature into full-scale convective storm clouds.
- โ๏ธ Cumulonimbus Variants: Storm clouds can have different shapes, sizes, and heights. Some have large anvils, while others are more compact. Each storm can develop differently.
๐ง๏ธ Visuals, Rain Curtains & Hail
- ๐ง๏ธ Localized Rain Curtains: Rain now renders directly beneath specific clouds, matching their exact shape and size.
- ๐ง Cloud-Generated Hail: Hail originates inside Cumulonimbus clouds, falling with physics, bounce mechanics, and surface interactions.
- ๐ Impact Sounds: Added sound effects for hailstones hitting surfaces and targets.
โก Independent Electrical Activity
- โก In-Cloud Lightning: Dynamic lightning bolts generated inside storm clouds.
- ๐ Dynamic Thunder: Thunder sound effects tied directly to localized electrical activity.
๐ฆ๏ธ Weather System Rework
- ๐ง Autonomous Storms: Storm generation now relies entirely on the custom cloud evolution system.
- ๐ซ Vanilla Overhaul: Vanilla weather commands have been disabled as WeatherPhysics gains independence from the base game's weather engine.
- ๐๏ธ Deprecated Commands: Removed the temporary
/weatherphysics severethundercommand.
๐ก Note: WeatherPhysics is in active development. Bug reports and community feedback are greatly appreciated!
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:wI13khII:8AjJo2iX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wI13khII:8AjJo2iX"
}

