2.1.0
Compatibility
Changes
🔥 DragonsWrath 2.1.0 — Aetheric Awakening (Alpha)
This update transforms DragonsWrath from a powerful weapons plugin into a true Unique Relic System built around scarcity, PvP tension, and server-wide impact.
🌍 One-Per-Server Global Lock
Each relic is now limited to ONE copy per server
Crafting checks:
Stored relic ownership data
Online player inventories
If already held, the forge refuses to craft it
Clear error messages and feedback replace silent failures
True scarcity. Real power.
🧭 Dynamic Forge GUI (Live Status System)
The forge now acts as a live relic tracker.
Green status: ● AVAILABLE
Red status: ● CURRENTLY HELD BY: PlayerName
Automatic lore updates
Release toggles in config.yml to hide future relics
released: bow: true mace: false sword: false
💀 Aetheric Shriek (Death Reset System)
Relics cannot be permanently hoarded.
When a relic holder dies:
A Wither roar plays server-wide
A broadcast announces the relic’s return to the Aether
The relic slot is instantly marked Vacant
The next player can craft it immediately
This creates natural PvP-driven relic cycles.
🪨 Heavy Density Enforcement (Crusher Mace)
The Crusher is Aetherically heavy.
Players holding it cannot use Elytra
Elytra is automatically unequipped if attempted
Wings are safely returned to inventory
Forces grounded “Tank” gameplay.
🛠 Admin Management GUI (/dwadmin)
New 9-slot admin dashboard:
View current relic holders
Check crafting status
Right-click to Force Vacate relics
Perfect for banned or inactive players
⚖️ Balance & Quality Improvements
Improved feedback messages
Better data tracking system
More consistent relic state handling
Cleaner internal data structure
⚠️ Alpha Notice
This is a Alpha release. Please report bugs or edge cases before full release.
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:NYzhJjMN:HHg4vlx1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NYzhJjMN:HHg4vlx1"
}

