-
Notifications
You must be signed in to change notification settings - Fork 1
FAQ.md
Minecraft 1.18 – 1.21.x and 26.1 / 26.1.1 (Java Edition only).
Server software:
- Spigot, Paper, Purpur, Pufferfish — fully supported
- Folia — fully supported
- Forge, Fabric, Bedrock — not supported
Yes. Free and open source under MIT.
- GitHub Issues — bug reports
- Discord — quick help and community
- Correct Minecraft version? (1.18+)
- Using Spigot or Paper, not Vanilla?
- JAR in the
plugins/folder? - Server restarted after installing?
- Check console for errors.
UnsupportedClassVersionError → Update Java to 17+
NoClassDefFoundError → Re-download the JAR
- Stop server
- Back up
plugins/SpawnChestPlugin/ - Replace the old JAR with the new one
- Start server
Config files are always preserved.
/chestconfig get settings.enabled-worlds # check world list
/nextchest # check remaining time
/chestnow # force spawn for testing
/testchestzone # preview coordinates
settings:
chest-count-per-interval: 3 # spawn 3 chests at once
chest-spawn-delay-seconds: 5 # 5 s between eachsettings:
spawn-zone:
min-distance: 400
max-distance: 2000
min-height: 50
max-height: 200Run /testchestzone to preview sample coordinates.
Configure surface exclusions:
settings:
spawn-zone:
exclude-surfaces:
water: true
lava: true
ice: trueUnopened chest — disappears after chest-disappear-minutes from spawn time.
Opened chest — gets a fresh chest-disappear-minutes from the moment it was opened.
Set chest-disappear-minutes: 0 to keep chests forever.
When pre-open-timer.enabled: true, chests start locked. The first player to right-click starts a countdown (default 30 seconds). Anyone can open the chest after the countdown ends. This gives distant players time to run.
/chestconfig get legendary-items.enabled
/chestconfig get legendary-items.dragon-slayer-sword.enabled
/cooldowns
/chestconfig get abilities.pvp-protection
If pvp-protection: true, items do not work on other players.
- Find them in Legendary chests (15% spawn chance)
- Admin command:
/getlegendaryitems - Add to custom loot via
/putintothechest
/togglelegendary dragon-slayer-sword
Or in config:
legendary-items:
dragon-slayer-sword:
enabled: falseControlled by:
abilities:
pvp-protection: true # items do NOT work on players
pvp-protection: false # items work in PvP- Must be in inventory when you die
- One-time use — consumed on death
- Does not protect against
/kill - Check:
/chestconfig get legendary-items.phoenix-feather.resurrection
Works on: Iron Ore, Gold Ore, Copper Ore, Ancient Debris.
Does not smelt: Diamond, Emerald, Coal, Redstone, Lapis.
Check: /chestconfig get legendary-items.master-pickaxe.auto-smelt
Four: random, common, rare, legendary. Each forces a specific chest tier or picks one randomly.
/giveapple random Steve 1
/giveapple common Steve 1
/giveapple rare Steve 1
/giveapple legendary Steve 1
No. Apples spawn an extra chest without affecting the main timer.
When world-apple-drop.enabled: true, a Summoner Apple spawns as a physical item in the world each time a chest appears. Players see coordinates in chat and race to pick it up. The item never despawns until collected.
- Get items in your inventory
- Run
/putintothechest - Click a tier
- Drag items into the chest area
- Set fraction (how many items spawn per chest)
- Click Save
- Did you click Save?
- Is custom loot shown as enabled (green) in the main menu?
- Is the fraction too low? 1/10 of 5 items = 0–1 items.
Yes. Common, Rare, and Legendary each have their own independent loot table.
No. Reset only deletes items (dropped at your location). Chest type and fraction are preserved.
Yes. Copy plugins/SpawnChestPlugin/custom_loot.yml to the other server.
With 4.4+ they don't. The plugin detects WorldGuard, GriefPrevention, GriefDefender, and Lands automatically and skips protected locations.
protection:
enabled: true
check-worldguard: true
check-grief-prevention: true
check-grief-defender: true
check-lands: trueA temporary zone around each active chest that blocks breaking and placing blocks. Removed automatically when the chest disappears or is opened. Uses WorldGuard regions when available, falls back to built-in event blocking otherwise.
chest-protection-zone:
enabled: true
radius: 5features:
bossbar:
enabled: trueThen grant players the spawnchest.notify.bossbar permission.
Update to 4.4 — this was a known bug. The bar now hides explicitly when both show-countdown and show-active-chest are false.
The plugin uses spawnchest.notify.* permissions. On servers where all permissions are denied by default, grant these to the default group:
/lp group default permission set spawnchest.notify.spawn true
/lp group default permission set spawnchest.notify.coordinates true
/lp group default permission set spawnchest.notify.countdown true
/lp group default permission set spawnchest.notify.disappear true
/lp group default permission set spawnchest.notify.bossbar true
Players without spawnchest.notify.coordinates still see the spawn announcement — coordinates are just omitted: "A Legendary Chest has appeared somewhere in the world."
/chestconfig get statistics.enabled
/togglefeature statistics
/mystats # your own stats
/leaderboard # top 10 players
Check progress in /mystats. Make sure statistics.achievements.enabled: true.
features:
effects:
particles: false
chest-beacon-beam: false
features:
guardians:
common-count: 1
rare-count: 2
legendary-count: 3Increase spawn interval: /setchesttimer 1800
Yes — these are detected automatically for both chest protection zone creation and spawn location filtering.
Yes. No conflicts. You can use legendary items as high-value trade goods or configure Summoner Apples as donator rewards.
Yes. Legendary items still gain McMMO XP normally.
language: "ru" # or any supported codeRun /reloadchestconfig after changing.
Edit plugins/SpawnChestPlugin/lang/en.yml (or your language file). Run /reloadchestconfig after saving.
Yes. Version 4.4 handles Mojang's new versioning scheme automatically. No changes needed on the server side.
- Search existing issues first
- Include: Minecraft version, plugin version, server software, console error, steps to reproduce
- Submit at GitHub Issues
Yes — GitHub. Open source under MIT.