Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated 2 weeks ago
All versions
1.1.0+1.21.1-neoforge
Beta
1.1.0+1.21.1-neoforge5 months ago 45
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
1.1.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.
- Ray of Frost, Flamerush & Falling Star are now Tier 5 Spells, they got slightly buffed
- These Spells can now also be learned in the Spell Binding Table
- Moved the Spells Aeroblast & Explosive Bubbles from Elemental Wizards to this Mod
- Reworked Explosive Bubbles, its now a channeled spell, that spawns Bubble Entities that Explode on Impact
- Moved all the structures from loot_n_explore to lne_wizards, so it's clearer that these structures come from this add-on New Content
- Added a new T5 Extra Spell for the Earth Wizard: Rock Crash (A Giant Meteor Projectile that crashes in the ground)
- Added 6x Elemental Evoker MobEntities
- They are able to cast two Spells from the Wizards and Elemental Wizards Weapons & Spell Books according to their element
- You now have to fight them, in the LNE-Wizard themed structures!
- The primary spell that these evokers can cast are hard-coded weapon skills from the elemental wands & staffs
- What other secondary spells these evokers can cast is fully configurable with spell tags: "resources\data\lne_wizards\tags\spell\mob\evoker"
- These entities also drop materials for their element's magic runes, they also have a chance to drop spell scrolls from their element
- For technical info how these spell casting mobs work, take a look at the More RPG Library Readme!
- The Evokers can also spawn in Raid's, this can be turned off in the tweaks config
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:vukREL4F:nDcT4EwG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vukREL4F:nDcT4EwG"
}



