2.0.0
Compatibility
Required content
Changes
This version is a major rewrite of the plugin.
The previous implementation was limited by hardcoded worlds and fixed file paths, making it difficult to use on real Hunger Games setups. Starting from this version, the plugin is fully configurable and no longer tied to specific world names or map structures.
Worlds can now be freely defined in the configuration, and chest location files can be loaded from custom paths, allowing different maps and layouts to be used without modifying the plugin.
Hologram handling has been improved and made more reliable, with safer reload and cleanup logic. Commands have been simplified and made more consistent, and optional persistence for looted chests has been added.
Overall performance and stability have been improved, making the plugin suitable for production environments and network-based setups.
Optional dependencies
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:axLTU62Z:UBP0Dpd8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:axLTU62Z:UBP0Dpd8"
}

