Tags
Creators
Details
3.8
Compatibility
Changes
AeternumSeasons 3.8 Update
New climate.yml option
A new setting was added to climate.yml:
respect_naturally_snowy_biomes: true # true = respects cold/snowy biomes, false = melts everything
## true = respeta biomas fríos/nevados, false = derrite todo
This option lets you decide whether naturally snowy/cold biomes should keep their snow behavior.
Important:
If you set this option to false, it can melt snow even in naturally snowy biomes.
This setting exists for servers that want stricter seasonal control, but keeping it on true is recommended for more natural biome behavior and better realism.
Magic Storm adjustment
Magic Storm was adjusted so hostile mobs properly return to normal after the event ends.
This prevents mobs from staying permanently buffed after receiving the Magic Storm effects.
Actualización de AeternumSeasons 3.8
Nueva opción climate.yml
Se añadió una nueva configuración a climate.yml:
respect_naturally_snowy_biomes: true # true = respeta los biomas fríos/nevados, false = derrite todo
## true = respeta los biomas fríos/nevados, false = derrite todo
Esta opción permite decidir si los biomas naturalmente nevados/fríos deben mantener su comportamiento de nieve.
Importante:
Si se establece esta opción en false, se puede derretir la nieve incluso en biomas naturalmente nevados.
Esta configuración existe para servidores que desean un control estacional más estricto, pero se recomienda mantenerla en true para un comportamiento más natural del bioma y un mayor realismo.
Ajuste de Tormenta Mágica
Se ajustó Tormenta Mágica para que los enemigos hostiles vuelvan a la normalidad correctamente después de que finalice el evento.
Esto evita que los enemigos queden potenciados permanentemente tras recibir los efectos de Tormenta Mágica.
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:Ej72Vp0g"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6KGJM0Xi:Ej72Vp0g"
}

