
Horse Powered
Hand-cranked and animal-powered machinery focusing on early game grinding, chopping, pressing, drying, and crushing. Leash horses, donkeys, or llamas to automate the line or generate Forge Energy. Data-driven recipes with full JEI, EMI, and Jade support.
Tags
Creators
Details
1.20.1-1.7.0
Compatibility
Changes
Horse Powered 1.7.0
Backport of the 1.21.1 branch's 2.6.1 release into 1.20.1.
New Content
- Bottles can take fluid out of the Horse Press (#17): glass bottles carry no fluid-handler capability in Forge, so the press never recognised one as a container and fluids that only have a bottled form (fruit juices and the like) could not be removed by hand at all. A new
horsepowered:bottlingrecipe type covers that gap: right-clicking the press with a recipe'scontainerdrains its fluid from the output tank and hands back the filled item, and right-clicking with the filled item does the reverse, filling the input tank and returning the empty container. - One bottling recipe ships by default: a glass bottle takes 250 mB of water from the press and becomes a water bottle. Press ice, snow, snowballs, or pointed dripstone for the water. Mods and packs add their own at
data/<namespace>/recipes/bottling/<recipe>.jsonwithcontainer,fluid,result, and optionalpriority. Result NBT is respected, so potions and other data-carrying items work. SeeREADME.mdfor the full schema. - New Bottling category in JEI and EMI listing every registered bottling recipe, with the Horse Press as its workstation.
Bug Fixes
- Modded spawn eggs now show in Trapping recipes (#18): the recipe panels looked the entity's spawn egg up through vanilla's
SpawnEggItem.byId, which only knows about vanilla eggs. Any mob whose egg was registered throughForgeSpawnEggItemfell back to a plain egg. The lookup now goes throughForgeSpawnEggItem.fromEntityType, which checks Forge's registrations first. If that still finds nothing, an item named<namespace>:<entity_path>_spawn_eggis tried before giving up, which covers mods that register a custom egg item class. - Trapping recipes with an unresolvable entity no longer capture a pig:
BuiltInRegistries.ENTITY_TYPEreturnsminecraft:pigrather than null for an unknown ID, so a recipe naming a mob whose mod was absent (or a typo'd ID) trapped a pig and wrote the bogus ID into the trap's NBT. The trap then went dead on reload: nothing rendered, and no loot ever rolled. Such recipes are now skipped outright, and a saved trap holding an unresolvable entity reports as empty instead of as a pig. The two recipe viewers were affected the same way and no longer show a pig spawn egg for these recipes. - EMI's Trapping category had no name, showing its raw translation key. It now reads "Trapping".
Recipe Viewer
- Trapping recipes now name the animal in text (#19): the JEI and EMI Trapping panels only identified the catch through the spawn egg icon and its hover tooltip, which packs that hide creative items (AStages, GameStages, JEI blacklists) strip out. Each recipe now prints the animal's name as a heading line under the arrow, so the panel reads correctly with no spawn egg visible.
- New optional
titlefield onhorsepowered:trapping: overrides that heading. Accepts a translation key (resolved against the active language) or a plain string (shown as-is). Omit it and the entity's own name is used, so existing recipes and datapacks get the naming for free. - New optional
iconfield onhorsepowered:trapping: an item ID for the panel's output slot, for mobs that have no spawn egg at all. Resolution order isicon, then the entity's registered spawn egg, then the conventional egg item ID, then a plain egg.
Optional dependencies
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:cZml36tg:7CUExkRY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cZml36tg:7CUExkRY"
}
