Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last week
All versions
2.6.2+1.21.1-fabric
Release
2.6.2+1.21.1-fabric4 months ago 955
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Changes
2.6.2 - 1.21.1
Elemental Wizards Spell Expansion:
- New Spell Choices for the Spell Tier's 2-4 for every Elemental Wizard Spell Book!
- Earth: T2: Impale T3: Shattering Stones (Old LNE Spell) T4: Stone Golem
- Impale: Impales a target with a sharp stone, blocking its movement and dealing damage to it.
- Shattering Stones: Launch a stone that shatters on impact, sending fragments in all directions that cause bleeding wounds.
- Stone Golem: Summons a Earth Golem, that smashes the ground and summons damaging spikes that deal damage and knock up on contact.
- Water: T2: Waterballs T4: Tidal Wave
- Waterballs: Shoots multiple water balls that deal {damage} damage.
- Tidal Wave: Tidal Wave that travels back and forth and deals damage and knocks targets back.
- Wind: T2: Twister T3: Windfield T4: Storm Draft
- Twister: Launch a circling-moving whirlwind, that knock's back targets it hits and damages them.
- Windfield: Calls a field of strong wind that deals damage and reduces movement speed.
- Storm Draft: Channel bursts of high pressure air that deal damage and shortly stun enemies.
- Huge thanks to Slepykat for the new Projectile- & Effect- and Entity Models <3 Fixes and Changes
- Moved the LNE-Extra Spells to the LNE-Wizards Mod (Explosive Bubble & Aeroburst)
- Improved the Tornado Model (by Slepykat)
- Fixed some Missing Weapon Recipes
- Internal Changes for some Spell Spawned Entities to improve their behaviour
- Improved the Spell Textures for some of the existing Earth Wizard Spell Icons
- Cleaned up the Code
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:kJgoIleS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PeZ4h4i0:kJgoIleS"
}





