Tags
Creators
Details
3.6.0
Compatibility
Changes
Config
- Reworked big parts of the config:
-
Config Fields are now named using the camelCase (e.g.
trimChance) instead of the snake_case (e.g.trim_chance) naming scheme- The snake_case naming scheme still works tho, such that old configs won't break. Config files will be automatically migrated when the mod saves (most likely when saving via config screen)
-
Config Versioning, Deprecation and Migration:
- The config is now versioned using a new
_versionfield. Do not modify this field, unless you know what you're doing, as it's important for config migration - Config Fields from previous config schema's may now be deprecated. This means, the mod will continue to deserialize and load these config fields from the config file, however the mod won't save these config fields anymore. Deprecation is necessary for config migration:
- Config Fields from previous config schema's may now be migrated. This means, deprecated config fields will now, where applicable, be automatically migrated to newer alternatives
- The config is now versioned using a new
-
Lots of internal refactoring
-
Improved Trim Filtering
-
Replaced
material_filterandpattern_filterwithtrimFilter- These two separate filters were quite limiting, due to being separate. You weren't able to handle anything, that requires both trim material and pattern. For example, you couldn't blacklist single specific trims, without blacklisting entire trim materials / patterns
trimFiltercombines these filters into one, allowing for both all previously possible behavior and some new possibilities (for example blacklisting single specific armor trims, without having to blacklist entire trim materials / patterns)- See the according wiki page for documentation about this config field
- Due to being too 'complex', this new field is currently only possible to edit via the config file, and not in the screen.
material_filterandpattern_filterhave been deprecated with automatic migration totrimFilter
-
Removed
predefined_trims- The new
trimFilteralso has the capability to do this, sopredefined_trimsis no longer necessary - See the according wiki page for documentation about
trimFilter predefined_trimshas been deprecated with automatic migration totrimFilter
- The new
-
Removed
trim_system- No longer necessary since
predefined_trimshas been removed trim_systemhas been deprecated as it's needed inpredefined_trims's automatic migration
- No longer necessary since
-
Replaced
texture_validation_filteringwithmissingTextureFiltering- This new config field allows configuring which strategy the mod uses to filter out missing-texture trims
- It was previously very unclear, what kind of additional filtering the mod was actually doing, for users -> this config field makes this more transparent and configurable
- See the according wiki page for documentation about this config field
- Since
texture_validation_filteringwas previously used to control part of this, it has been deprecated with automatic migration tomissingTextureFiltering
-
Renamed
trim_chancetopieceTrimChance(trimMobsconfig category)- The previous name was very misleading
- Automatic Migration exists
-
Inverted and renamed
noTrimsChancetotrimChance- Now that
trim_chance/trimChanceis available, this rename (and inversion, to make the new name actually accurate) makes this config field's functionality much more clear - Automatic Migration exists
- Now that
-
Fixed precautionary trimming (see
missingTextureFiltering) being unnecessarily restrictive- Instead of only allowing following trim combination:
(from vanilla) + (from any mod or vanilla), this now additionally allows for:(from mod A) + (from mod A)
- Instead of only allowing following trim combination:
Other
- Added support for 26.3
- Adjusted default config values, for trims to be rarer
- Added an
openWikibutton to the utils category of the config screen - Updated the wiki, translations, descriptions and the README
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:hHVaPgFK:zHhEsfmD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hHVaPgFK:zHhEsfmD"
}

