0.0.8.5
Compatibility
Changes
πͺοΈ WeatherPhysics v0.0.8.5 β Tornado Shape Variety & Intensity Update
Version 0.0.8.5 introduces distinct tornado structural geometries (Rope, Cone, Wedge), full F0βF5 intensity scaling, dynamic debris limits for performance, and seamless natural supercell spawning!
πͺοΈ Tornado Shape Variety
- πͺοΈ Three Distinct Morphologies: Added Rope, Cone, and Wedge tornado shapes with improved funnel geometry.
- π Independent Shape & Intensity: Tornado visual models can now spawn independently of their actual physical intensity (e.g., violent high-wind tornadoes with narrow rope-like funnels).
π¨ Intensity Scaling & Destruction Mechanics
- π F0βF5 Intensity Scale: Implemented complete F0 through F5 structural and force categories.
- πͺ΅ Scaled Debris Generation: Stronger tornadoes tear through tougher block types and throw higher volumes of dynamic debris.
- β‘ Performance Capping: Strict debris limits enforced to maintain server and client FPS during violent storm events.
βοΈ Natural Supercell Spawning
- π©οΈ Natural Formation: Supercells now select and generate tornado shapes dynamically as they evolve naturally, without requiring admin commands.
- π¨ Visual Diversity: Greater visual variance across naturally occurring tornadic events.
βοΈ Technical Enhancements
- π Server-Client Sync: Extended cloud network packets to transmit active tornado intensity and shape parameters in real time.
- π‘οΈ Full Engine Compatibility: Preserved all existing atmospheric systems (frontal rains, hail, 3D lightning, and landspouts).
π οΈ Technical Details
- Mod Version: 0.0.8.5
- Minecraft Version: 1.21.1
- Loader: NeoForge
- Environment: Client & Server required
π Note: This update focuses specifically on expanding tornado structural diversity, F-scale intensity grading, and dynamic destruction physics!
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:Hkua8vWc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wI13khII:Hkua8vWc"
}

