Tags
Creators
Details
1.0.2-neoforge-1.21.1
Compatibility
Changes
Skin packs now use one unified format
Previous versions loaded skins from a separate resource pack + datapack pair, which meant you needed a world already created before the datapack half could even be enabled.
Skin packs are now self-contained: drop a folder or .zip into the new mcpskins folder (it appears next to mods and saves) and it's loaded automatically as both assets and data. No resource pack menu, no editing a world's data packs, no pack.mcmeta.
Old-format skin packs (separate resourcepack + datapack) will not load with this version. To update one, merge its assets/ and data/ folders into a single folder and drop that into mcpskins/. Full layout and examples: [wiki link].
The wiki has been rewritten for this format only. It no longer documents the old resourcepack/datapack setup, so if you stay on an older mod version, its install steps won't match the current wiki.
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:NiMg4Heu:VgQtr9ZG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NiMg4Heu:VgQtr9ZG"
}

