0.2.7
Compatibility
Required content
Changes

Initial Release
Welcome to AtmosLib! This is the first release of a library designed to expand Minecraft's atmospheric customization possibilities through resource packs and simple JSON configuration files.
New Features
Layered Clouds
Added support for multiple cloud layers, allowing resource packs to create complex skies with clouds stacked at different layers.
Biome-Based Fog
Added customizable fog settings for individual biomes, allowing different environments to have their own unique atmospheric appearance.
Biome-Specific Clouds
Added the ability to configure cloud appearances for specific biomes, creating more diverse and immersive environments.
Custom Skies
Introduced additional sky customization possibilities for resource pack creators.
Custom Atmospheric Colors
Added support for customizing atmospheric colors to create different visual styles and moods.
How to use
Use the following path in your resource pack with the following files:
Path: your-resource-pack\assets\atmoslib
Files: in \assets\atmoslib make atmoslib.json
The JSON file will be like this example:
{
"enabled": ${atmoslibEnabled},
"version": 2,
"clouds": {
"enabled": ${cloudsEnabled},
"base_height": ${baseHeight},
"layers": [
{
"id": "upper",
"enabled": ${layerEnabled},
"color": "${color}",
"opacity": ${opacity},
"height_offset": ${heightOffset},
"size": ${size},
"thickness": ${thickness},
"offset_x": ${offsetX},
"offset_z": ${offsetZ},
"speed_x": ${speedX},
"speed_z": ${speedZ},
"render_distance": ${renderDistance},
"face_brightness": ${faceBrightness}
}
]
}
}
Customization
Resource pack creators can configure atmospheric effects using simple JSON files, making customization easier and more flexible.
General Improvements
Expanded resource pack customization possibilities.
Introduced new ways to create more immersive Minecraft environments.
Designed to make advanced atmospheric customization more accessible to resource pack creators.
Thank you for using AtmosLib!
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:ymDED7s3:WyjFOwFG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ymDED7s3:WyjFOwFG"
}

