Tags
Creators
Details
Licensed ARR
Published last year
Updated 3 weeks ago
All versions
NeoForge-1.21.11-5.2.1
Beta
Serene Seasons Plus 5.2.13 weeks ago 106
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Serene Seasons Plus v5.2.1 -> NeoForge 1.21.11
Fixed
- Fixed Better Days sleep cycles waking players at an incorrect time. SSP now applies a configurable wake time of 1000 (7:00 AM) after Better Days completes sleep.
Serene Seasons Plus v5.2.0
Fixed
- Snow placement now treats the
sereneseasonsplus:snow_replaceableblock tag as the single authority for replacing non-air blocks. - Snow can no longer overwrite protected blocks through vanilla precipitation redirects or delayed world-mutation queues.
- Delayed snow changes now verify that the block still matches the state seen when the change was queued, protecting rails and other blocks placed in the meantime.
- Snow clearing no longer removes unrelated blocks when tracked snow data becomes stale.
- Fixed the config screen applying Minecraft's background blur twice.
- Fixed config-screen sizing, clipped controls, toggle state updates, validation feedback, and NeoForge config saving.
- Updated chunk snow restoration to the current per-storm synchronization behavior used by the other supported versions.
Changed
- Natural ground-cover replacements are now declared explicitly in the snow-replaceable tag instead of being accepted by a hidden fallback.
- Removed the older snow-deficit and destroyed-column reapplication behavior.
- CurseForge publishing now uses Mod Publisher and produces release uploads for version 5.2.0.
Optional dependencies
Any compatible version
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:4Al4H3t9:YxD8KH4k"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4Al4H3t9:YxD8KH4k"
}

