Tags
Creators
Details
1.1.b.2
Compatibility
Changes
Plugin won't try to apply the skin again if the returned skin is the exact same as the previous fetch. Won't meaningly effect fetch-retries config. Hopefully getting out of GeyserMC's way.
Situational values replaced with hastags in this example.
[##:##:## WARN]: [Geyser-Spigot] Expected tag to be a literal string, a list of components, or a component object with a text/translate key: {
"extra": [
""
],
"player": {
"properties": [
{
"name": "textures",
"value": "###################################################################"
}
]
}
}
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:ST76Q4is:KuHenSmV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ST76Q4is:KuHenSmV"
}![Bedrock Skin Restorer [GeyserMC/Floodgate]](https://cdn.modrinth.com/data/ST76Q4is/203831a5c43fb605055cd0c610147967877d4014.webp)

