Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 2 weeks ago
All versions
2.7.2+1.20.1-fabric
Release
2.7.2+1.20.1-fabric2 weeks ago 3,070
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
2.7.2+1.20.1
⚠️ Read this before updating
This release is a major technical overhaul and is not backwards compatible.
- Requires the matching Spell Engine release. This version will not run on Spell Engine 0.9.x, and mods built against 0.9.x will not work alongside it.
- Update the whole set together. Spell Engine and every RPG Series mod must be on matching versions. Mixing in an older add-on will break at startup or misbehave in play.
Back up your world before updating.
- Thanks to Daedelus for the PR!
- Ported to Minecraft 1.20.1 (Fabric + Forge 47). NeoForge is replaced by Forge on this line; the same Forge jar also loads on NeoForge 1.20.1.
- Requires the matching 1.20.1 releases of Spell Engine (1.10.5) and Spell Power (1.6.0).
- Loot-table modification and the mob-beam packet were rebuilt on Spell Engine's platform seams, so both loaders share one implementation.
- Every registry write goes through Forge's
RegisterEventwindow, so the mod also boots on Forge 47.0-47.3 and on NeoForge 1.20.1, which never unlock the vanilla registries.
Accepted 1.20.1 limitations
- The
typhoonandstonebloomenchantments are registered from Java instead of shipping as data-driven enchantments (1.20.1 has none). Weights, max level, costs, slots and the multi-school exclusivity are unchanged, but they can no longer be overridden or disabled from a datapack. - 1.20.1 has no entity-scale attribute, so everything that read a living entity's scale now uses 1.0.
- Trial Omen and Raid Omen do not exist on 1.20.1:
clearNegativeEffectsno longer clears Trial Omen, and the Tenacity resist check covers Bad Omen only. - Tag entries naming 1.21-only content (
bogged,breeze,wind_charge) are declared optional and are simply absent.
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:Wkc3lwHo:U0alAjGs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Wkc3lwHo:U0alAjGs"
}

