Tags
Creators
Details
1.9
Compatibility
Changes
Skkaemok 1.9
Major Changes:
• Fixed per-viewer tablist names reverting shortly after being changed
• Fixed unlisted players reappearing after display or profile updates
• Separated tablist formatting, nametag team updates, and profile refreshes to avoid unnecessary packets
• Fixed nickname and skin replacement/reset handling by tracking the applied profile for each viewer
• Per-viewer changes now reapply only to the intended viewer
• Added support for HTTP skin image URLs and custom ports, with stricter URL validation
• Fixed delayed skin requests overwriting newer changes or applying after reset or disconnect
• Improved original skin restoration and stored-skin handling on join, reload, and disable
• Limited nickname rewriting to /msg, /tell, and /w recipients to preserve other command arguments and message text
• Improved JSON save safety and reduced redundant storage writes
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:RhiqvLwA:tyczRSPf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RhiqvLwA:tyczRSPf"
}

