
Ars 'n Spells
Ars ’n Spells bridges Ars Nouveau and Iron’s Spells ’n Spellbooks, creating deeper synergy between two major magic systems. Harness mana, spell power, glyphcraft, and spellbooks together through new compatibility features, cross-mod progression
1.6.3
Compatibility
Required content
Changes
-
Ars 'n' Spells v1.6.3
Bug Fixes
- Fixed startup crash caused by
MixinSanctifiedAbstractSpellusing the wrong parameter type (LivingEntityinstead ofPlayer), preventing the game from loading when Iron's Spellbooks was present - Fixed crash in
IronsBridge.setMana()due to missing null check onMagicData - Fixed potential crash from null
SpellRaritywhen calculating LP costs for Iron's spells and scrolls - Fixed
MixinSanctifiedAbstractSpellnot being registered in mixin config. Sanctified Legacy LP validation was completely non-functional - Fixed
MixinSpellStatsPotencybeing wrongly gated on Iron's Spellbooks. Resonance potency now works even without Iron's installed - Fixed potential double LP charge when using spell scrolls with Cursed Ring equipped
- Fixed
BridgeManagercreating unnecessary bridge instances on every mana query when unification was disabled
New Features
- Added
/ans mana setdefault <value>command (op level 2) to configure default max mana at runtime - Added
/ans mana getdefaultcommand to view current default max mana - Added
ENABLE_LP_SYSTEMconfig toggle to completely enable or disable the LP (Life Points) system - Added
DEFAULT_MAX_MANAconfig option (range:1.0to100,000) - Added startup warning when dual-cost percentages do not sum to
1.0
Improvements
- Rewrote
LPDeathPreventionwith a flag-based immunity system, preventing Corpse mod from incorrectly triggering on LP damage - LP system handlers now respect the
ENABLE_LP_SYSTEMtoggle across all event handlers - Hardcoded fallback mana values now use the configurable
DEFAULT_MAX_MANAinstead of fixed100 - Improved error log formatting in
IronsBridge
Housekeeping
- Cleaned up stray build artifacts (
com/,nul) from repository - Updated
.gitignorewith missing entries - Added Linux
gradlewwrapper
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:NlMT8pQt:GUGqWMcW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NlMT8pQt:GUGqWMcW"
}
