1.0.1
Compatibility
Required content
Changes
This version requires RPGMana 1.0.8.2 as a dependency. By default, the SP and Mana bars no longer overlap each other.

Additionally, it now allows registering spells that consume both SP and Mana simultaneously.
To register a spell that consumes both SP and Mana, follow these steps:
- Blacklist Configuration: Add the spell id to the "blacklist_spell_casting_regex" field in the server.json configuration files of both mods (rpgmana and rpgsp).
- Whitelist Configuration: Add the same spell id to the "whitelist_spell_casting_regex" field in the server.json file of the rpgsp mod.
- Custom Resource Costs: Specify the SP and Mana consumption values for your spell in the respective server.json files under dedicated fields.
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:d4IQJ6OR:Ur1cOPPl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d4IQJ6OR:Ur1cOPPl"
}

