Tags
Creators
Details
1.2.1-alpha
Compatibility
Changes
๐ 1.2.1-alpha โ The Builder Update
Big jump from 1.2.0 โ five major systems added.
๐ NEW: Spellbook GUI (/spell)
A fully visual spellbook. Browse unlocked spells, see cooldowns / mana / class gating, and pick your active spell with one click. No more typing spell names.
๐ฎ NEW: Built-in Spell Editing in Spell Forge
Edit ANY built-in spell live in-game. Adjust:
- Cooldown, damage, range
- Mechanic chains (damage / heal / effect / particles / sound)
- Targeters & conditions
- Class & level requirements
Overrides save to spells.yml and survive restarts.
One-click reset to default for every spell.
โ๏ธ NEW: Class Profile Runtime
Six fully-implemented classes:
- ๐ก๏ธ Knight โ tank / melee bruiser
- ๐ฎ Mage โ arcane caster
- ๐น Ranger โ marksman with marks & arrows
- โ๏ธ Cleric โ healer / support
- ๐บ Beastmaster โ pet bruiser
- โ๏ธ Engineer โ gadget / turret DPS
Each has unique stat scaling, spell pool, starter item, and click bindings. Fully data-driven.
๐ ๏ธ NEW: Class Forge GUI
- Admin editor:
/class admin forge(perm:vortex.admin.classes) - Player browser:
/vortex classes - Edit display name, lore, spells, attribute scaling, starter item
- Live preview before saving
๐ฑ๏ธ NEW: Click Clarity System
One rule across all class items:
- Left-Click = basic attack / class skill
- Right-Click = cast equipped spell
Vanilla wins where it matters: Knight melee on L-Click, Ranger arrow on R-Click.
๐จ NEW: Premium Item Tooltips
- Color-coded lore with icon prefixes
- Italic auto-formatting disabled
- Full
ยง-code rendering
๐ NEW: Live Lore Refresh
Old items in player inventories auto-rebrand on join, hotbar scroll, inventory click, swap hands, or respawn. No re-give commands needed.
๐ฆ Compatibility
Paper ยท Spigot ยท Folia ยท Java 21 ยท MC 1.21+
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:vuXiXUvx:a8pecm9m"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:vuXiXUvx:a8pecm9m"
}

