Tags
Creators
Details
1.0.0
Compatibility
Changes
Random Chest Spawner
Bring your server to life with Random Chest Spawner, the perfect plugin for creating exciting loot events that keep players exploring, competing, and coming back for more.
Random Chest Spawner automatically generates loot chests at random locations within configurable areas, rewarding adventurous players with customizable treasures. Whether you're running a Survival, PvP, Factions, or Event server, every chest spawn creates a new objective and an opportunity for players to race, fight, or team up for valuable rewards.
⨠Features š¦ Spawn loot chests at random locations. š Fully customizable loot tables. š Support for multiple worlds and configurable spawn regions. ā±ļø Adjustable spawn intervals and despawn timers. š¢ Broadcast chest spawn announcements to all players. āļø Easy-to-use configuration with flexible customization. š Lightweight, optimized, and built for high-performance servers. š® Perfect For Survival servers PvP & Factions Skyblock SMP communities Seasonal events Custom game modes š Why Choose Random Chest Spawner?
Transform ordinary exploration into exciting adventures. Encourage player interaction, create hotspots for PvP encounters, reward exploration, and keep your world feeling alive with dynamic loot events.
Every chest spawn becomes a memorable moment, giving players a reason to venture into the unknown and compete for exclusive rewards.
Simple to configure, powerful to customize, and designed to provide an engaging experience for players of all skill levels.
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:q2bCcCB8:92OO1UxL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q2bCcCB8:92OO1UxL"
}

