Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 4 days ago
All versions
2.1.3
Beta
[Neoforge] Sky Aesthetics 2.1.33 months ago 36
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client-side
Changes
Sky Aesthetics 2.1.3 for MC 26.1.x changelog
Changes
- Move some logic to client side
Fixes
- Fixed a GPU memory leak that could crash the game for skies using custom sky objects
- Fixed conditional skies, clouds, and fog not working on multiplayer servers
- Fixed a crash when the mod was installed on a dedicated NeoForge server
- Fixed custom sun/moon textures rendering as a thin sliver at the wrong size
- Fixed custom sun/moon not blending transparency and not fading in rain or at dawn/dusk
- Fixed a crash when clicking Duplicate in the editor with an empty or invalid id/dimension
- Fixed which sky is chosen when several skies target the same dimension (now deterministic)
- Fixed the "moving stars" option having no effect
- Fixed custom stars disappearing when the star count was between 1 and 99
- Fixed STATIC sky objects still drifting with the day/night cycle
- Custom cloud recolor/reposition now respects the "disable custom clouds" config option
- Custom skies now render in dimensions with no vanilla sky (e.g. the Nether)
- Fixed the editor silently dropping enabled-but-empty sections; export now warns instead
- Fixed the live preview sky leaking into the next world after leaving one
- Fixed a possible crash from resource reloads freeing sky graphics mid-frame
- Fixed a render pipeline registration race on NeoForge
- Reduced per-frame GPU work for the custom sun and moon
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:2zaNpyqY:lei4hzfm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2zaNpyqY:lei4hzfm"
}

