Tags
Creators
Details
All versions
2.0.0
Release
Armor Trims Backport v2.0.0 (1.18.2-Fabric)last year 60
Compatibility
Minecraft: Java Edition
1.18.2
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Highlights
- Armor Trims now use color palettes. This means that the way they look lines up with vanilla.
- A color will still be generated from the item texture if no palette is available for an item.
- Support for Fabric has been implemented.
- (On Fabric, JEI is replaced with REI.)
- Support for 1.16.5 has also been implemented.
- In turn, 1.19.3 versions are no longer available.
Other Changes
- I changed the config system (to allow compatibility with Fabric).
This probably won't cause issues with existing packs but if it does delete the file to regenerate it. - Color palettes can be handled by a resourcepack, more information is available on GitHub.
- French translations are available.
- I have removed Russian translations.
- API has been expanded to multiple classes. The old API class is stubbed and no longer functions. It is only present to avoid immediate crashes.
- Source jars are provided for developers. My code is a mess but the api pieces should be clean.
- Any mods using the old API should transfer to the new one. The old API class is not present on 1.16.5.
Smaller Fixes
- Disabling JEI in the config now actually disables JEI.
- Source jars are now supplied to aid developers (be warned my code is a mess).
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| armor_trims-fabric-1.18.2-2.0.0-sources.jar | Unknown | 180.87 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:srKdSMcH:SEPm6Kxd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:srKdSMcH:SEPm6Kxd"
}

