Links
Tags
Creators
Details
Licensed BSD-3-Clause
Published 9 months ago
Updated 9 months ago
All versions
1.3.0
Release
Elemental Dragon Plugin 1.3.09 months ago 22
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Changes
๐ฎ For Players (Gameplay Changes)
โ ๏ธ Important: One-Fragment Limit
- You can now only carry ONE fragment type at a time!
- If you have a Burning Fragment, you cannot pick up or equip any other fragment (Agility, Immortal, Corrupted Core)
- To switch fragments, you must DROP your current fragment first
- Use
/withdrawabilityto unequip your current fragment without dropping it
๐ฅ Fire Fragment Fixes
- Dragon's Wrath (
/fire 1) now deals consistent damage- Always deals exactly 3 hearts of damage
- Damage ignores armor (as originally intended)
๐ Corrupted Core Fixes
- Dread Gaze (
/corrupt 1) duration changed to 4 seconds (was 10 seconds) - Frozen targets now properly cannot move, eat, or use inventory
๐ง For Server Operators
๐ก๏ธ One-Fragment Limit Implementation
- Comprehensive fragment checking across inventory, equipped, and cursor
- Players can no longer bypass limit by:
- Picking up fragments while holding another on cursor
- Clicking equipped fragment while standing on another
- Using equip commands with fragments in containers
๐ง Bug Fixes
- BurningFragment: Simplified Dragon's Wrath damage calculation
- CorruptedCoreFragment:
- Added debuff metadata for tracking frozen players
- Implemented persistent freeze using Bukkit teleportation (anti-cheat compatible)
- Fixed freeze duration to 4 seconds
๐งช Testing
- Added
FragmentManagerOneFragmentLimitTestwith 5 comprehensive test cases - Updated
FragmentItemListenerTestfor new API
Full Changelog: https://github.com/cavarest/elemental-dragon/blob/main/CHANGELOG.md
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:66f6mWei:6JMOdAni"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:66f6mWei:6JMOdAni"
}

