Creators
Details
Licensed ARR
Published 11 months ago
Updated 2 months ago
All versions
Forge-0.1.0
Beta
Project Atmosphere for TFC 0.1.07 months ago 54
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Project Atmosphere for TFC
Added
- Centralized bridge climate sampler for Project Atmosphere runtime values:
- authoritative temperature sampling by
ServerLevel + BlockPos + calendarTicks - authoritative wind sampling by
ServerLevel + BlockPos + calendarTicks - shared TFC wind-vector conversion boundary in one place
- authoritative temperature sampling by
Changed
- TFC runtime climate temperature override now uses the live Project Atmosphere orchestrator path consistently.
- Weekly forecast integration now hooks the live
TemperatureGenerator.generateWeekForecast(...)entrypoint directly. - TFC wind vector integration now uses Project Atmosphere wind as the authoritative source.
- Mixin gating was tightened to apply climate patches only when required core classes are present.
- Bridge entrypoint and season wiring were cleaned up for safer lifecycle behavior.
Fixed
- Removed obsolete temperature override assumptions tied to older Project Atmosphere APIs.
- Eliminated brittle pointer/key-based temperature sampling in favor of live world-position sampling.
- Fixed season-change tracker initialization edge case.
Notes
- This refactor keeps Project Atmosphere as the canonical source for temperature and wind in TFC climate integration.
- No extra sync packet layer was introduced; existing server-authoritative Project Atmosphere data paths remain the source of truth.
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:nx3Le5Rv:pr3jxjGe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nx3Le5Rv:pr3jxjGe"
}

