Links
Tags
Creators
Details
Licensed MIT
Published 4 months ago
Updated last month
All versions
1.3.0
Release
CreateMobGrinding 1.3.0last month 211
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Changelog - Version 1.3.0
New Features & Upgrades
- Grinder Upgrades: The Rotational Mob Grinder now supports item upgrades. Right-click the block to insert them.
- Vacuum Upgrade: Automatically sucks up dropped items and Experience Orbs in a 3x3 flat area in front of the blade. Absorbed XP is automatically compressed into Create's Experience Nuggets.
- Protection Upgrade: Makes the Grinder's spinning blade completely harmless to players.
- Native Blade Enchanting: Grinder Blades can now be enchanted natively using Anvils or Enchanting Tables. They exclusively accept utility enchantments (Looting, Fire Aspect, Beheading, Unbreaking, and Mending).
- Structure Loot Integration: Blank Spawner Chunks can now be rarely found (5% chance) inside structure chests (Mineshafts, Dungeons, Ancient Cities, and Strongholds).
- Expanded Mob Roster: Added 19 new mobs to the mod (including Breeze, Bogged, Slime, Armadillo, etc.) complete with their Sequenced Assembly recipes.
Tweaks & Changes
- Datapack Tags for Tiers: Mob Tiers are now entirely driven by Data Tags instead of configs, ensuring perfect synchronization between spawn times and required crafting materials.
- WAILA / Goggles Support: Full integration with Jade and Create's Goggles. You can now see the Tier of living mobs by looking at them, and inspect installed Upgrades and Enchantments inside a Grinder.
- Custom Death Messages: Dying to a Grinder will now display a custom, localized death message in chat.
- Ponder Scenes: Texts updated to reflect the new enchanting mechanics.
Bug Fixes
- Fixed an infinite loop where items extracted by Funnels were instantly sucked back up by the Vacuum Upgrade.
- Fixed an anvil exploit that allowed combat enchantments (like Sharpness) to be incorrectly applied to Grinder Blades.
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:XwIkHYnz:IynAndxD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XwIkHYnz:IynAndxD"
}

