Links
Tags
Creators
Details
Licensed ARR
Published 5 months ago
Updated 5 months ago
All versions
0.0.4-Beta
Beta
Dungeons Tower 0.0.4-Beta5 months ago 18
Compatibility
Minecraft: Java Edition
1.21.11
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
[0.0.4-Beta] - Latest
🚀 Highlights / Major Optimization
- Ultra-Fast Generation (Step-4 Optimization): Completely revolutionized the biome generation process. By updating biome data in 4x4x4 chunks (matching Minecraft's native 3D biome grid) instead of block-by-block, the processing loop was drastically reduced from ~90 million iterations down to ~1.3 million!
- Benchmark Result: Successfully generated a colossal 765 x 765 x 155 blocks maze (totaling 90,709,875 blocks, equivalent to ~25,000 rooms) in just 10 seconds! (Down from the original 530 - 830 seconds before optimization. Tested on AMD Ryzen 5 7600).
✨ New Features
- PlaceholderAPI Integration: Added
%dt_...%placeholders for seamless integration with scoreboards, holograms, and menus! Available variables:%dt_maze%,%dt_floor%,%dt_total_floors%,%dt_room_type%,%dt_room_shape%,%dt_room_label%
- Dungeon Spawn Control: Introduced a smart
DungeonSpawnListener. It automatically cancels natural vanilla mob spawns on top of dungeon roofs, while safely allowing custom mob spawners (e.g., MythicMobs) to function normally inside the dungeon rooms. - Performance Profiler: Added a detailed execution time breakdown. Upon generating a maze, the console/player now receives a precise summary of the time taken for Preparation, Foundation, Carving, Pasting, and Finalizing.
🛠 Improvements
- Enhanced grouping and multi-block pasting logic for custom boss/secret rooms (
BOSS_3x3,MINI_BOSS_2x2, etc.) during the carving phase. - Enhanced boss bar display states to accurately reflect FAWE/WorldEdit flush cycles.
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:cDQ5XOxU:z0IBUjhi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cDQ5XOxU:z0IBUjhi"
}

