Tags
Creators
Details
2.4.0-beta.2+1.21.5
Compatibility
Required content
Changes
sorry for the delay with this update! i've been a bit busy, but i'm hoping to get a full release for 2.4.0 out some time soon(ish?). in the meantime, here's another beta. enjoy the copper age!
- added support for The Copper Age (1.21.9)
- skin overrides will also work on mannequins now
- currently, overrides work for both static and dynamic profiles. this may become a config option in the future
- the library screen will now show previews with the player you're modifying
- previously, this would have always been your own skin
- skins are no longer processed (gh#36). this means, for example, if you had a 64x32 skin, it would stay as that original 64x32 image, rather than automatically resizing to 64x64.
- adding skins from a user no longer processes the saved image
- setting your skin globally no longer processes it
- this should improve compatibility with mods that do cursed stuff with skins (like ears)
- your online skin will now show to yourself on offline mode servers
- this also allows you to see any overrides you have (gh#34)
- this will be more configurable eventually
- duplicate library entries will no longer be loaded, and instead a warning will be printed to the log
- marked mod as compatible with pre-patch versions (e.g. the 1.21.8 version is marked compatible with 1.21.6 and 1.21.7)
- this is mainly just so i can get 1.20.x and 1.21.x on the sidebar. i don't recommend using these old versions!
- some bug fixes
- fixed library entries using textures (not files) not sharing or being changed globally
- fixed the scroll bar on the override screen not usable (gh#42)
- fixed identical library entries with different names being merged together
- fixed a crash that could happen when reloading the library screen under certain circumstances (gh#40)
- fixed capes added by name to the library using the skin texture instead on 1.19.4 - 1.20.2
- the code for the mod is now on codeberg rather than github. you can open issues at either place, though!
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:GON0Fdk5:PaQvTtjj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GON0Fdk5:PaQvTtjj"
}


