0.2.0
Compatibility
Changes
🩸 Core Gameplay Update
Nocturne Slayer now introduces a DOOM-inspired combat loop, focused on aggression, momentum, and rewarding close-combat execution.
Enemies no longer die instantly — they enter a DOWNED state, allowing you to perform Glory Kills, recover health, and build Fury.
⚔️ New Mechanics 🩸 Glory Kill System
Enemies enter a DOWNED state instead of dying instantly.
Right-click a downed enemy to execute it.
Executions:
Restore health instantly
Grant Souls
Build Fury
Trigger visual & sound feedback
Works with bare hands or any weapon.
🔥 Fury System
Killing enemies builds Fury stacks.
Fury increases combat tempo and rewards aggressive play.
Fury decays naturally if combat stops.
Fully configurable via config.yml.
💀 Soul System
Each hostile mob grants Souls.
Souls are used for progression.
Different mobs grant different soul values.
Nether mobs grant bonus souls.
🧠 Player Progression
Player-specific profiles (UUID-based).
Persistent level, souls, fury, and stats.
ActionBar HUD displays:
SLAYER | Lv X | Souls Y/Z | Fury A/B
🔥 Combat Behavior
Enemies get stunned instead of dying.
Downed enemies glow and stop moving.
Execution must be performed within a time window.
Failing to execute allows the enemy to recover.
🌋 Environment Interaction
Nether gives bonus rewards.
Visual feedback using particles and sound.
Fast-paced, aggressive gameplay loop.
⚙️ Configuration
Everything is configurable:
Soul gain per mob
Fury limits
Execution window
Healing amount
Nether multipliers
UI update frequency
🧩 Technical Info
Built for Paper 1.21+
Lightweight and optimized
No NMS
Multiplayer-safe
Fully server-side
🛠 Fixed / Improved
Fixed entity death desync
Fixed glory execution timing
Improved combat responsiveness
Improved performance & stability
🧪 Known Limitations
No custom animations (vanilla engine limit)
Uses particles instead of custom models
Requires permission: nocturneslayer.use
🚀 What’s Next
Boss entities with phases
Custom sound packs
Visual rage effects
Optional screen effects
Lore system & progression tree
🩸 Become the Slayer. The world is no longer safe.
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:GDDkW0er:8KF7M72R"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GDDkW0er:8KF7M72R"
}

