
Enhanced Spawners: Chambers of Control
Enhanced Spawners: Chambers of Control lets players upgrade and customize mob spawners using survival items, with full redstone control and spawn egg integration โ all without commands or GUIs. Designed for clean, technical mob farms and dungeon systems.
1.0.0
Compatibility
Changes
Enhanced Spawners: Chambers of Control Version 1.0.0 โ June 29, 2025
๐งฑ Spawner Upgrades Bring structure to your chaos with a clean upgrade path:
๐ช Iron Ingot โ Tier I: Faster spawn rate
๐ช Gold Ingot โ Tier II: More mobs per wave
๐ Diamond โ Tier III: Increased mob cap
๐ฅ Netherite Scrap โ Tier IV: Stronger spawns (configurable)
๐ช Netherite Block โ Tier V: Max performance, max output
Right-click a spawner with the item to apply upgrades. All handled through persistent block data โ no commands, no GUI.
๐งฌ Spawn Egg Control Set the spawner to any allowed mob type:
Sneak + right-click with a spawn egg
Limited to mobs defined in config.yml
Instant feedback via particles and sounds
Fully survival-compatible
๐ Redstone Behavior Automate and control mob flow with redstone:
Powering a spawner disables it
Supports toggles, traps, dungeon resets, wave systems
โ๏ธ Configuration Highlights Fully customizable in config.yml:
disable-ai: false
redstone-disables: true
max-tier: 5
allowed-mobs:
- zombie
- skeleton
- spider
- blaze
upgrade-items:
tier1: IRON_INGOT
tier2: GOLD_INGOT
tier3: DIAMOND
tier4: NETHERITE_SCRAP
tier5: NETHERITE_BLOCK
๐ฆ Compatibility โ Paper, Purpur, Spigot
๐ฏ Minecraft 1.20.4 โ 1.21.4
๐ Server-only, no PlaceholderAPI, no GUI
๐ฎ Sneak Peek: v1.1.0 โ โSigils & Sanctumsโ Prepare for new systems that deepen spawner mastery:
๐ช Ritual-based Upgrades โ Upgrade spawners with custom structures and multi-step sequences
๐งฟ Spawner Claiming โ Natural spawners can be claimed, protected, and made private
๐บ๏ธ Regional Mob Caps โ Enforce mob limits per player-controlled area for cleaner balance
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:7nS6Lkhw:NZCjC9IX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7nS6Lkhw:NZCjC9IX"
}
