All versions
0.1.0-alpha
Alpha
Deep Dark Depths 0.1.0-alpha10 months ago 295
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Folia
Paper
Spigot
Changes
📋 Changelog
v0.1.0-alpha — Initial Release
The depths open for the first time.
✨ New Features
🔊 Sound Detection System
- All player actions now generate noise (mining, walking, running, combat, chest interactions)
- Configurable noise levels for each action type
- Debug mode shows real-time noise levels in action bar
🎯 Sound-Based Mob Targeting
- Mobs below Y=64 hunt by sound instead of sight
- Deeper zones = more sensitive mob hearing
- Creepers and Endermen remain visual-only (configurable)
🥷 Stealth Mechanics
- Sneaking reduces noise by 90%
- Silk Touch tools reduce mining noise by 50%
- Wool blocks nearby dampen sound by 70%
⚔️ Progressive Difficulty
- Mobs scale in strength based on depth:
- Surface (Y≥64): Normal stats
- Shallow (Y 0-63): +25% HP, +15% damage
- Deep (Y -32 to -1): +75% HP, +50% damage
- Abyss (Y<-32): +150% HP, +100% damage
💎 Depth-Based Loot
- Bonus loot chance increases with depth (10% → 50%)
- XP multipliers scale with depth (1.25x → 2.5x)
- Rare drops: diamonds, ancient debris, echo shards in Abyss
☠️ Environmental Hazards
- Cave-ins: Mining can trigger ceiling collapse (5-15% chance)
- Gas pockets: Random poison/nausea when mining (3% chance)
- Darkness debuff: Applied below Y=-48 without light source
🏆 Depth Milestones
- 5 achievements for reaching new depths
- Title announcements with sound effects
- Track your deepest Y level with /deepdark stats
⚙️ Commands
/deepdark — Plugin info
/deepdark info — Gameplay tips
/deepdark stats — Your depth statistics
/deepdark reload — Reload configuration
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:MqeeIrWo:9GAtQS7z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MqeeIrWo:9GAtQS7z"
}

