Tags
Creators
Details
Licensed MIT
Published 7 months ago
Updated 7 months ago
All versions
1.0.4
Release
Easy Spawner Control 1.0.47 months ago 1,103
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
Easy Spawner Control 1.0.4
Highlights
- Config-first everything – Every gameplay toggle (fragments, mining rules, menu gating, XP rewards, replacement blocks, egg behavior) now reads exclusively from
run/serverconfig/easy-spawner-control-world.cfg, so datapack reloads and server packs stay in sync. - Cleaner world config layout – Introduced dotted groups (
eggDrops.*,spawnerMining.*,fragmentDrops.*,menu.*,recipes.*) with backward-compatible parsing. Admins can scan related options without hunting through the file. - Spawner egg toggle –
spawnerMining.dropMobEgglets you decide whether a mined spawner ejects its stored egg. Tied to per-player egg cooldowns to stop mass farming. - Per-mob egg overrides – New
easy-spawner-control-mob-eggs.cfgships with curated defaults so dangerous mobs start at 0% while passive mobs can stay generous. Entries overrideeggDrops.defaultChance. - Expanded cooldown matrix – Min pickaxe tiers, Silk Touch requirement, menu key bypass/cooldown, fragment and egg cooldowns, replacement block, and XP payout are all wired to config values.
Fixes
- Resolved config
Valuesrecord mismatches that were blocking builds after the new toggles. - Logging helpers now echo the dotted key names you actually edit, so typos are easier to find.
- Silk Touch spawner mining (and any case with
spawnerMining.awardXp = 0) no longer spawns vanilla XP orbs—the override now runs on the server thread.
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:mmaUr7eo:B8VlGADn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mmaUr7eo:B8VlGADn"
}

