Tags
Creators
Details
All versions
4.4.2
Release
Chest Spawn 4.4.26 months ago 44
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Paper
Purpur
Spigot
Changes
SpawnChestPlugin v4.4.2
IN THIS VERSION FOLIA SUPPORT WAS REMOVED
What's New
bStats Integration
- Added anonymous usage statistics to help improve the plugin
- Plugin ID: 31206
- View stats at: https://bstats.org/plugin/bukkit/SpawnChestPlugin/31206
- Fully compliant with privacy - no personal data collected
Customizable Guardian Types
Configuration Example
Add to your config.yml:
features:
guardians:
enabled: true
# Guardian counts per tier
common-count: 2
rare-count: 3
legendary-count: 5
# NEW: Guardian mob types
# Valid types: ZOMBIE, SKELETON, WITHER_SKELETON, SPIDER, CAVE_SPIDER,
# CREEPER, ENDERMAN, PIGLIN, ZOMBIFIED_PIGLIN, BLAZE, STRAY, HUSK,
# DROWNED, VEX, VINDICATOR, PILLAGER, RAVAGER, SHULKER, PHANTOM, etc.
common-type: ZOMBIE # Default guardians for Common chests
rare-type: SKELETON # Default guardians for Rare chests
legendary-type: WITHER_SKELETON # Default guardians for Legendary chests
# Example 1: Spider-themed server
features:
guardians:
common-type: SPIDER
rare-type: CAVE_SPIDER
legendary-type: CAVE_SPIDER # with more spawns
# Example 2: Nether-themed
features:
guardians:
common-type: ZOMBIFIED_PIGLIN
rare-type: BLAZE
legendary-type: WITHER_SKELETON
# Example 3: End-themed
features:
guardians:
common-type: ENDERMITE
rare-type: ENDERMAN
legendary-type: SHULKER
# Example 4: Raid-themed
features:
guardians:
common-type: PILLAGER
rare-type: VINDICATOR
legendary-type: RAVAGER
- Fixed compatibility issue with mob types across MC versions
- Improved version-safe entity type detection
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:AOhB9MQL:nCO8S4gb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AOhB9MQL:nCO8S4gb"
}

