Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated last month
All versions
2.1.0
Release
Apotheosis Balance Configurator 2.1.0last month 1,423
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
2.1.0
-
Bug fix
- Aggressive multipliers (e.g.
apotheosisMultiplier=0.3) no longer spamUnsupportedOperationExceptionfromStepFunction.fromBounds()during affix loading. The old build was intercepting the structural accessorsStepFunction.max()andStepFunction.getForStep(int)— those are read by Placebo's bounds-style codec to round-trip step functions, and lying about them broke the(max - min) / stepvalidation. Removed both injections; tooltips and gameplay still see multiplied values becauseStepFunction.get()/getInt()are still scaled.
Thanks to the modpack dev who narrowed it down to attribute affixes.
- Aggressive multipliers (e.g.
-
Optional integration: Iron's Apothic
- When the Iron's Apothic compat mod is present (which itself bridges Apotheosis with Iron's Spells & Spellbooks), the following affixes are now scaled by
apotheosisMultiplier:SchoolAttributeAffix(attribute toggle)ManaCostAffix,SpellLevelAffix,SpellEffectAffix,SpellTriggerAffix(special toggle)
- No action needed in modpacks — if Iron's Apothic is installed, its spell-related affixes balance themselves automatically. If it's not, this mod behaves exactly as before.
- Iron's Apothic is declared as an optional NeoForge dependency; the mod loads cleanly with or without it.
- When the Iron's Apothic compat mod is present (which itself bridges Apotheosis with Iron's Spells & Spellbooks), the following affixes are now scaled by
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:nDQt0Hbn:sjEjwU9E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:nDQt0Hbn:sjEjwU9E"
}

