Links
Tags
Creators
Details
Licensed MIT
Published 2 years ago
Updated 2 years ago
All versions
2.0.1
Release
2.0.12 years ago 97
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Mob Farms
- Changed recipe to require a sword instead of lava.
- Changed recipe to include compatible enchantments with swords
- Added the ability to individualize cooked meat based on if the sword has fire aspect on it.
- Added the ability to see what kind of sword is on each farm.
- Added ability to upgrade sword tier using four of the desired items. Back porting (or downgrading is NOT supported)
- Enchantments DO transfer.
- Added ability to add enchanted books with sword compatible enchantments.
- You can’t put multiple enchanted books in at once, but you can stack enchantments on one enchanted book and put that in.
- Putting a farm with enchantments in your crafting inventory or in the crafting table with nothing else will remove ALL enchantments.
- Looting enchantments will cause animals to drop more loot just like in-game.
- Blaze and Wither Skeleton Farms can either be anywhere in the Nether or on top of Nether Brick.
- Striders and Magma Cube Farms can either be anywhere in the Nether or on top of lava.
- Hoglins can be either be anywhere in the Nether or on top of Crimson Nylieum.
- The Ghast Farm does NOT have an exception block(if you have an suggestions, post it in the Discord!)
- The Special Unnamed Block has a block you must make another block which you combine with the sword of your choice.
- Achievement for the Special Unnamed Block has officially been added. When you get it, you earn 100,000 XP.
- Sword Tier DOES matter. The higher the tier, the faster the farm drops. Gold and Wooden Tiers drop at the same rate.
- Jade and The One Probe integrations now work. You can see what kind of sword is on each block by just looking at it.
- Fixed a bug where farms that are required to be in a specific dimension or on top of a specific block wasn't working
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:VsViZhgh:Ouz8XSHD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VsViZhgh:Ouz8XSHD"
}

