0.2.5
Compatibility
Changes
๐ ArcanaConcept v0.2.5 โ The Discipline of Command
The Ethereal Grimoire records a new development in the study of necromantic orchestration. The Arcanist Synod has concluded that the summoning of the departed is not merely a ritual of power, but an art of balance. To command the dead is to conduct a fragile symphony between will, mana, and the fading echoes of forgotten warriors.
Refinement of the Pavane of the Departed. The ritual has been extensively reworked. The spectral legions now respond with greater clarity and coordination, their instincts sharpened by improved animus patterns. The command interface has been refined to better reflect the arcanistโs strategic intent, and the election mechanism that governs leadership within the summoned ranks has been stabilized.
Arcane Economy Rebalanced. The metaphysical cost of sustaining the dead has been recalibrated. Mana upkeep, kill-to-invocation ratios, and the maximum number of manifested units have been adjusted to ensure a more coherent equilibrium between conjuration and attrition.
Expanded Tactical Awareness. The command interface now reveals the energetic tension between regeneration and drain more clearly, allowing arcanists to maintain control of their spectral host without destabilizing their own reserves.
Stability Restoration. A spatial distortion that previously obstructed perception when the practitioner strayed too far from their summoned army has been resolved. The veil between commander and legion now remains intact across greater distances.
Mana Progression Adjustment. The growth curve governing maximum mana capacity has been revised. As arcanists deepen their mastery, their reserves now expand along a more natural conceptual trajectory.
Master the concepts. Trust the vision, for the canvas is as vast as your will.
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:e4cV5rrI:CoQJVasQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:e4cV5rrI:CoQJVasQ"
}

