Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated last month
All versions
1.4.0
Release
1.4.0last month 367
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Changes
1.4.0
Additions
- invalid upgrade entries are now displayed as "Invalid Upgrade"
- upgrades are invalid if one of their components contains an invalid spell/attribute identifier
- added server config option to hide/show invalid upgrade_entries
- added a new built-in data pack that adds a number of enchantments. They grant the spell modifiers for the new weapon skills and are meant to be a replacement for the weapon skills tab. This data pack requires Spell Engine Extension.
- added built-in data packs for the RPG Series classes + their "Loot & Explore" add-on mods by Fichte. These data packs will automatically replace the default data packs when the corresponding add-on mods are loaded.
- added built-in data packs that add integration for various class mods.
- "Druids (RPG Series Plus)" mod by Rulft44
- "Bards (More RPG Series)" mod by Fichte
- added custom key binding category
Changes
- split the built-in data packs, each content mod now has a dedicated compatibility pack which is automatically disabled if the mod is not installed
- fire mage class is no longer locked behind being in the nether by default
- updated all classes to their latest versions
- locked upgrades are no longer shown when changing upgrades is disabled, instead "Empty Upgrade" is displayed when no upgrade is selected
Fixes
- fixed a crash that sometimes occurred when displaying the class selection screen without having a class selected
Technical
- refactored the class upgrade ids in the built-in data packs to be more in line with the new layout used in the Skill Tree mod
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:VIWS5Sb5:ynu7DECa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VIWS5Sb5:ynu7DECa"
}

