
Tensura:Dungeon
Tensura: Dungeon expands on Tensura Reincarnated by introducing a full dungeon system inspired by Rimuru’s Labyrinth. Explore a procedurally generated dungeon filled with traps, shrine trials, rare mobs, and boss fights — all tied into a progression-based
Tags
Creators
Details
1.0.0.7
Compatibility
Changes
Tensura: Dungeon v1.0.0.7 – Fixes & Additions
Fixes & Systems • Fixed Stellar challenge rewards showing two chest models when only one should appear. • Fixed shrine activation on servers incorrectly showing "This shrine is already active" when it was not. • Changed shrine timer to waves for protection objectives. (Removed the confusing countdown; now purely wave-based.) • Fixed tames and clones granting players first boss kill rewards. • Fixed receiving the rule violation confirmed message in the Overworld. • Chests should now despawn consistently after 5 minutes. (Report if there are any chests that still aren’t despawning.)
Additions & Changes
• All shrines now properly give 1 chest upon completion.
• Shrine progression rewards are what grant multiple chests.
• Added/adjusted progression bonus for completing multiple shrine challenges:
- 1 Challenge Completed: +5% Coin Bonus
- 2 Challenges Completed: +10% Coin Bonus, +5% Elite Mob Spawn Rate
- 3 Challenges Completed: +15% Coin Bonus, +10% Elite Mob Spawn Rate
- 5 Challenges Completed: 1 Guaranteed Uncommon Loot Roll, +15% Elite Mob Spawn Rate
- 6+ Challenges Completed: +10% Coin Bonus, +25% Elite Mob Spawn Rate, +0.20% Loot Explosion Chance (shrine-spawned mobs)
- 10+ Challenges Completed: +10% Coin Bonus, 2 Chests at Once, +50% Elite Mob Spawn Rate, +0.50% Loot Explosion Chance
- 20+ Challenges Completed: +10% Coin Bonus, 3 Chests at Once, +95% Elite Mob Spawn Rate, +1% Loot Explosion Chance
• Added a command to let you see your shrine challenge progress as well as dungeon cooldown:
/dungeonStats player <playername>
• Shrines will now display the remaining cooldown time before they can be used again.
- Other minor adjustments
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:CAsFfbXy:Ccyy35Mb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:CAsFfbXy:Ccyy35Mb"
}
