Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 weeks ago
All versions
Forge-0.7.0.0
Beta
Project Atmosphere 0.7.0.07 months ago 168
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
Project Atmosphere
Added
- TFC canyons, TFC salt marshes biomes support.
- Crafting recipes for dust and sand layers.
- Wind bending for realistic particles (smoke, ash, dust, snowflakes).
- Telemetry logging for cloud history and periodic region forecast/state samples.
Changed
- Default constructor to support older versions of Forge
- Pressure/temperature limits tuned for more realistic values.
- Sunlight curve/seasonal tilt updated for stronger midday and deeper winter dimming.
- Forecast data now persists across world reloads instead of regenerating every time.
- Missing-forecast warnings now log once per biome to reduce spam.
- Storm siren behavior updated for severity 7 storm warnings and tornado proximity alerts.
Fixed
- Avoided loading client-only Aurora/Rainbows classes on servers by switching mixins to string targets.
- Prevented client-only mixins from loading on dedicated servers.
- Thermometer recipe output corrected.
- Cloud telemetry logging aligned with updated signatures.
- Fixed wind-bent particle mixin compatibility by replacing the switch expression with explicit checks.
Notes
AS ALWAYS UPDATING TO THIS VERSION REQUIRES DELETING YOUR OVERWORLD FOLDER (created by Project Atmosphere) TO AVOID ISSUES WITH THE NEW REGION SYSTEM.
Go to your worlds folder and delete the "overworld" folder to allow the new region system to generate fresh regions.Note that this will reset the current forecast and could introduce desynced weather effects if the forecast isn't regenerated properly. (/temperature regenerate)
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:qIWoLcKJ:A61eMwJz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qIWoLcKJ:A61eMwJz"
}





