1.3.4
Compatibility
Changes
-
Feature: Control Mobs loot when killed (set in dungeon file)
-
Feature: Control Boss loot when killed (set in dungeon file)
-
Change: Fixed player showed in the dungeon while being outside of it
-
Change: Avoid crash when dungeonPortalEntity is null due to potential incorrect dungeon file
-
Change: Add other crash protections and a method for faulty portal to be repeared when opening the portal screen if correct dungeon file is accessible
-
Change: If a player disconnect or quit, it will have similar behavior as "/dungeon leave" command
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:sdPwbV1G:xSpAXgmm"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sdPwbV1G:xSpAXgmm"
}

