Tags
Creators
Details
Licensed MPL-2.0
Published 4 years ago
Updated 2 months ago
All versions
v4.0.4-1.19.2-Fabric
Release
[FABRIC] [1.19.2] ArmorStatues-v4.0.44 years ago 20K
Uploaded by
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Unavailable version
Unavailable version
Unavailable version
Changes
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
[v4.0.4-1.19.2] - 2023-01-17
Changed
- Opening the statue menu now requires a stick to be held in addition to sneaking, this was changed to improve compatibility with the Quark mod
- Removed the option to cycle through statue menu tabs using the tab key, it was conflicting with showing the vanilla server player list (at least on Fabric)
- Instead, you can now scroll through the tabs when your cursor is hovering them
[v4.0.3-1.19.2] - 2023-01-06
Fixed
- Fixed crash when trying to interact with entities using Fabric API 0.72.0+1.19.2
[v4.0.2-1.19.2] - 2022-10-19
Changed
- Any item can now be placed into the head slot on the equipment screen (thanks to Mephodio)
- Tooltips on the rotations screen will no longer obstruct the armor stand model (thanks to Mephodio)
- Tooltips on the style screen are now split into multiple lines to prevent them from flowing off the screen
[v4.0.1-1.19.2] - 2022-10-15
Changed
- Updated to Forge 43.1.40+ which is also now required
Fixed
- Armor stand interactions are now properly disabled when trying to open the menu when the mod is only installed client-side
[v4.0.0-1.19.2] - 2022-09-22
- Initial release
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| ArmorStatues-v4.0.4-1.19.2-Fabric-sources.jar | Unknown | 70.58 KiB |
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:bbGCtEvb:XtGOl7FU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bbGCtEvb:XtGOl7FU"
}

