Tags
Creators
Details
Licensed GPL-3.0-only
Published last year
Updated last week
All versions
2.0
Release
SpawnerSystem 2.0last week 141
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
1.19.4
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
đ Spawner System v2.0 - Change Log
đ New Features
- Spawner Storage: While Auto Slayer is on, loot is collected inside the spawner instead of dropping on the ground. It opens with the chest icon in the menu and has pages (
max-pages1-100, 45 slots per page). It can be turned on or off withspawner-storage.enabled(on by default). - Spawner Menu V2 (optional): A fully automatic "Spawner Control Panel", enabled with
spawner-menu-type: "V2". Auto Slayer, Storage and XP Vacuum are always on and no permissions are needed. The default menu stays V1. - Spawner Stacking: Spawners of the same type can be merged into one block (
spawner-stacking). A merged spawner gives the loot and XP of every spawner inside it. Breaking gives 1 spawner, or all except the last one while sneaking. Using spawn eggs on merged spawners is blocked. - Item Spawners: Spawners that produce items instead of mobs. Configurable in the new
spawner_items.ymlfile and theSpawners.ITEMsection. Use/sps givespawner <player> item <MATERIAL> [amount]. They are also shown in holograms. - Spawner Boosters: New
/sps giveboostercommand creates tickets that increase range, reduce spawn delay and boost XP. Includes booster stacking, a per-spawner booster menu, a minimum delay limit andreturn-on-breaksupport. Enabled by default. - Spawner Break Chance: The chance to get the spawner back is controlled by
spawnersystem.chance.<number>permissions (spawner-break-chance). - Natural Spawner Permission: New
natural-spawner-break-permission-requiredoption with thespawner.break.naturalpermission. - Advanced Chunk Limits: Separate limits for mob and item spawners (
separate-limits), a per-mob-type limit (per-mob-type) and-1for unlimited. - Limit Mode:
limit-modelets the mob limit be counted per chunk or per spawner. - Culling Improvements: Leashed, named and tamed mobs are now protected (
ignore-leashed,ignore-named,ignore-tamed). Writing"ALL"invalid-mobsapplies culling to every mob type, and protected mobs are still not removed. - Stored Item Drops: New
spawner-drop-stored-on-breakoption to drop stored items and XP when a spawner is broken. - Improved Explosion Protection: Spawners are now also protected from block explosions (beds, TNT, etc.) and the Wither.
- Menu Lock: Only one player can use a spawner's menu or storage at a time.
- Spawner Item Cleanup: Spawner items of the same type now stack properly in inventories. They are also fixed automatically when a player joins and when containers such as chests, barrels, shulker boxes and hoppers are opened or closed.
- New Menu Settings:
spawner-storage.enabledandspawner-auto-slayer.enabled(V1 only). The icon of a disabled feature is hidden in the menu. - Log Time Format:
log-time-format(auto,12h,24h) applies to both log files and Discord webhook messages. - New Toggles:
update-checkerandbstats-enabled. - Automatic Backups: A zip backup of the plugin folder is created when the plugin version changes (the last 10 backups are kept).
- Smart Config Updates: New config, loot and language entries are merged automatically without touching your existing values. Renamed keys are migrated for you.
- New Mob: Added
SULFUR_CUBEtoloot.yml.
đ§ Changes
- Auto Slayer: Mob spawners with Auto Slayer on no longer spawn real mobs. They give the loot directly to the storage (or drop it if storage is off) and ignore spawn conditions (light level, time of day, free space). A player still has to be in range, and the spawn delay, boosters and stacking still apply. The chunk mob limit (
max-mobs-per-chunk) does not apply to these spawners. - XP Vacuum: It is now tied to Auto Slayer and no longer has its own on/off switch. While Auto Slayer is on, XP is stored automatically, and you click the XP bottle to withdraw it.
- Menu layout: The second row now contains Storage, Auto Slayer, XP Vacuum and the "Active boosters" clock.
spawner-menuis now the master switch: Setting it tofalseturns off the menu, storage, Auto Slayer and XP Vacuum completely. Mob spawners then work like normal spawners and item spawners drop their loot on the ground. Items already stored in spawners are not deleted and come back when the menu is turned on again.- Spawner breaking is now processed at the end: if another plugin (a protection plugin, etc.) cancels the break, the spawner is not given, the pickaxe use is not consumed and nothing is logged or sent to the webhook. When breaking a merged spawner, you only get as many spawners as the pickaxe has uses left, and the uses are consumed accordingly.
- The plugin was rewritten into a modular structure for better performance and stability.
- Improved Folia support with a new scheduler system.
- Minimum API version lowered to 1.19.
- The
spawner.adminpermission now covers all/spsystemsubcommands and the spawner menu. - If
systemis set to an invalid value, a warning is printed to the console andadvancedis used. config.ymlwas reorganized into clear sections, and the separate version keys (config-version,language-version,discord-version,loot-version) were replaced by a singleversionkey.- Default spawner values changed:
amount3 â 4 andspawn-horizontal-radius3 â 4. - Discord webhook: the
webhook.server-namekey was renamed towebhook.webhook-name(migrated automatically) and the player icon was changed. - All 28 language files were updated with the new messages.
â ď¸ Notes
- In V2, spawn conditions and the free space check are ignored for all spawners (mob and item), because no real mobs are spawned. In V1 this only applies to mob spawners that have Auto Slayer turned on.
- Check your
config.ymlafter updating. A backup of your old files is created automatically.
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:4jPGg2yd:UfQmI6Xc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4jPGg2yd:UfQmI6Xc"
}

