All versions
1.0.0
Release
DragonAbilities 1.0.06 months ago 459
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
v3.0.0 — Initial Release
- 5 Dragon Egg abilities: Time Fracture, Reality Rip, Void Pulse, Dragon's Domain: Exile, Fracture Clone Execution
- Full
config.ymlwith all cooldowns, damages, and ability settings /egg give,/egg ability 1/2/3,/egg reloadcommands- F key and Shift+F key bindings for abilities 4 and 5
v3.1.0 — Sound & Visual Overhaul
- Added
master-sound-volumeconfig key — one slider controls all ability sound levels globally - Void Pulse particles significantly thickened — doubled core burst counts, added second ring layer, denser spiral aura (4 arms), finer ring geometry
- Dragon's Domain pull is now config-driven via
pull-strength
v3.2.0 — Domain Rework & Anonymous Identity
- Dragon's Domain now applies Darkness II, Slowness II, and Mining Fatigue V to all exiled players, refreshing every 5 seconds — all effect levels configurable
- Exiled players now have particle trails drawn toward the holder every tick
- All server-wide broadcasts now show a configurable
anonymous-nameinstead of the holder's real username - Fixed damage multiplier double-application bug in the damage event handler
v3.3.0 — Damage Pipeline & No-Death
- Absorption hearts now drain before real health on all ability damage
- Totem of Undying support — abilities check main hand then off hand and pop the totem instead of killing, with full vanilla revival effects
- Added
/egg nodeath <player>command — toggles a silent death floor at half a heart for the target player, blocking all damage sources from killing them - Added
dragonabilities.nodeathpermission node - Fixed config defaults not being written on first load — all keys are now auto-generated correctly
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:wj93G8Kt:hsVB8rho"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wj93G8Kt:hsVB8rho"
}

