Tags
Creators
Details
3.9
Compatibility
Changes
🌪️ AeternumSeasons Update 3.9
This update focuses on stability, protection compatibility, and event behavior improvements, especially for servers using WorldGuard and protected regions.
🛡️ WorldGuard Compatibility Improvements
Magic Storm
- Lightning strikes are now blocked inside protected regions.
- Prevents unwanted damage or griefing in spawn, towns, or safe zones.
- Storm visuals and atmosphere still work normally outside protected areas.
Tornado Event
- Tornadoes no longer push, damage, or affect entities inside protected regions.
- Crops and breakable plants will not be destroyed in protected areas.
- Tornado spawn logic improved to avoid generating inside protected zones when possible.
These changes make seasonal disasters feel immersive while still respecting server protection systems.
❄️ Snow & Climate System Fixes
-
Winter snow painter now respects
excluded_biomesfrom climate.yml. -
Snow will no longer form in hot or intentionally excluded biomes such as:
- Desert
- Jungle variants
- Badlands variants
-
Vanilla snow and ice formation is now also blocked in excluded climates during winter.
This ensures seasonal visuals remain consistent with biome design and server balance.
🔧 Internal Fixes & Stability
- Fixed crash on modern Paper versions where
Biomeis no longer an enum. - Improved config path handling for climate snow behavior.
- Various event safety improvements to reduce unintended world interaction.
❤️ Thank you
Huge thanks to server owners and testers reporting issues on protected regions and event interactions. Feedback continues to shape the seasonal system into a more server-friendly and performance-safe experience.
More refinements coming soon.
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:6KGJM0Xi:Ig6ZpzE9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6KGJM0Xi:Ig6ZpzE9"
}

