All versions
1.1.0
Release
Horse Armor Stand 1.1.01 hour ago 1
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Forge
Supported environments
Client and server
Changes
Horse Armor Stand 1.1.0
Added
- Support for Dragn's Livestock Overhaul on Forge 1.20.1 (the only version that mod exists for). With it installed, a stand draws horse armor the way that mod's horses wear it: on that mod's horse model, with that mod's textures, for its own armors and the vanilla ones alike.
- Stands now accept Livestock Overhaul's riot and minimal armors, which they refused before.
- Armor that mod cannot draw keeps the vanilla look. Livestock Overhaul is optional: without it nothing changes.
Fixed
- 1.19.2, 1.20.1, 1.21.1: horse armor whose texture does not exist is no longer drawn as a magenta-and-black checkered horse. It is not drawn at all, and the stand still holds it and gives it back.
- Forge and NeoForge 1.21.11: the log no longer shows "Couldn't load mod/horsearmorstand pack metadata" every time a world is loaded (the recipe loaded before as well).
- A NaN written by hand into renderScale or renderHeightOffset of config/horsearmorstand.json no longer reaches the renderer. Such a value now falls back to the default (1.0 and 0.0).
Changed
- Lower minimum loader versions: 1.1.0 asks only for the oldest build of each Minecraft line it works with. On 1.20.1, for example, 1.0.0 asked for Fabric Loader 0.16.10, Fabric API 0.92.7 and Forge 47.3.0; now it's 0.14.21, 0.83.0 and 47.1.0.
- Fabric 26.1.2 now asks for Fabric Loader 0.19.5 or newer: Architectury API 20.1.14 crashes the game at startup on older loaders even though it claims to accept 0.18.5.
Unchanged
- The stand, its recipe and the config file work exactly as in 1.0.0.
- Same Minecraft versions and loaders as 1.0.0: nothing added, nothing removed.
Known behavior
- With Livestock Overhaul, the horse on a stand keeps the model's default pose with its head up; live horses lower their head in the idle animation.
Compatibility
- Install on both the server and the clients (the mod adds an item, an entity and a recipe).
- Fabric needs Fabric API and Architectury API. NeoForge needs Architectury API. Forge needs nothing else. There are no Forge files for 26.x.
- Optional on Forge 1.20.1: Dragn's Livestock Overhaul (checked with 3.9.4, together with GeckoLib 4.8.4 and Patchouli 1.20.1-85, which it requires).
| Minecraft | Fabric Loader | Fabric API | Architectury API | Forge | NeoForge |
|---|---|---|---|---|---|
| 1.19.2 | 0.14.9+ | 0.66.0+ | 6.6.92+ | 43.1.0+ | - |
| 1.20.1 | 0.14.21+ | 0.83.0+ | 9.2.14+ | 47.1.0+ | - |
| 1.21.1 | 0.15.11+ | 0.102.0+ | 13.0.11+ | 52.1.0+ | 21.1.1+ |
| 1.21.11 | 0.17.3+ | 0.139.4+ | 19.0.1+ | 61.1.0+ | 21.11.0-beta+ |
| 26.1.2 | 0.19.5+ | 0.154.0+ | 20.1.14+ | - | 26.1.2.99+ |
| 26.2 | 0.19.3+ | 0.154.0+ | 21.0.7+ | - | 26.2.0.40-beta+ |
| 26.3 | 0.19.5+ | 0.160.5+ | 22.0.1+ | - | 26.3.0.0-beta+ |
Architectury API is needed on Fabric and NeoForge only.
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:szgu4dcq:7QJBBaMq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:szgu4dcq:7QJBBaMq"
}

