Tags
Creators
Details
3.0
Compatibility
Changes
AeternumSeasons 3.0 — Bug Fix Update
This release is focused on fixing reported issues and making the overall experience smoother across all dimensions. Thanks for all the reports and testing!
❄️ Aeternum Frost — Calendar Fixes
- Days now advance correctly when sleeping in
aeternum_frost. - Fixed a bug where you could enter the Frost dimension but the calendar wouldn’t advance.
- Glacialis Armor crafting is fixed and works again (including multi-language setups).
- Daily spawn chance has been increased to make encounters/events feel more consistent.
🔥 Aeternum Heat — Full Loot & Enchant Control
- The
aeternum_heatdimension has been adjusted and improved. - In
config.ymlyou now have full control over enchantment levels (caps/overrides), so things like Mending X won’t happen (Mending stays at the real level). - Heat loot is now fully configurable.
- Want to support more worlds? You can now add additional worlds easily in the config.
🌱 Rich Soil / Compost Improvements
- The Compost block now converts into Mud, allowing you to place Kelp and Sugar Cane.
- If you need it for farming: right-click with a hoe to convert it into Farmland for normal crops.
- The crop bonus from Rich Soil has been slightly increased to encourage compost/fertilizer setups.
🌐 Client Language Support
/season infonow properly displays text using the player’s client language.
🌾 CustomCrops Compatibility
- Growth mechanics were adjusted to reduce conflicts with CustomCrops.
- Since I don’t have the plugin installed for full testing, I added a configuration option to prevent collisions.
- If any bugs show up later, this area was improved to help both plugins coexist better.
✅ Final Notes
AeternumSeasons 3.0 brings many important fixes that improve stability and gameplay feel across the board. I hope you enjoy the update!
— Kinkin
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:QR2kfmcy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6KGJM0Xi:QR2kfmcy"
}

