Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last week
All versions
2.6.0+1.21.1-fabric
Release
2.6.0+1.21.1-fabric5 months ago 79
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
2.6.0 - 1.21.1
Update to use Spell Engine 1.9.0
- DISCLAIMER: All spell books and spell scrolls will be reset, due to major API changes.
- The Elemental Wizard Spell Books now offer 3 spells only, to match other classes
- Splash, Gust & Stone Throw are not in the Spell Book any longer, they're Weapon Spells for Wand's
- Water Whip, Wind Cutter & Stone Spear are not in the Spell Book any longer, they're Weapon Spells for Stave's
- The Elemental Staff, Avatar's Staff & Valkyrie Elementalist Staff can now choose between all three Elemental Staves Weapon Spells
- Hydro Beam is no longer the Tier 4 Spell of the Water Wizard, it is now a Tier 3 choice with the Springwater Spell
- Hydro Beam's Damage was nerfed and knockback buffed
- New Tier 4 Water Wizard Spell: Healing Rain Cloud, a new Entity that is following the caster or the Ally with the lowest health.
- The Healing Rain Cloud deals damage to targets and heals allies that are below the cloud entity standing in the rain
- All Heal coefficients of Water Spells where slightly nerfed
- The following spells where changed from Spell Cloud Entities to custom Entities: Terra Circle, Tornado, Earthquake
- Earthquake and Terra Circle received some new renderers for better visuals
- Enemies cant move through the Terra Circle Entities now
- The Tornado Entity will now pull enemies in its center
- The Tornado & Terra Circle can now be spawned at the targets location
- I've added Spell Book Descriptions in the Spell Binding table
- Already added some internal code, for future extra Spells
- The Elemental Avatar Passive from the Avatar's Staff will now show in the tooltip which spell will trigger.
Optional dependencies
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:PeZ4h4i0:ctqzv63i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PeZ4h4i0:ctqzv63i"
}





