Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated last week
All versions
1.3.8-1024px
Release
DynamicSkins 1.3.8last week 552
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Unavailable version
Changes
DynamicSkins 1.3.8 — Forge
Fixed
- Fixed a brief ping spike for some nearby players right after someone changed skin. The fast lane for nearby players (about 480 KB/s) could send faster than a viewer's connection could carry, and the queued skin data delayed that viewer's keep-alives (measured on the live server: 26 ms → 370 ms for about 1 s). The fast lane checked only the keep-alive ping, which updates every 15 seconds and cannot see a queue that builds within a second.
- The server now reads each player's live TCP round-trip time and compares it with the lowest seen on that connection. The fast lane is used only while that connection shows no queue (40 ms or less above normal).
- When a player's connection is already queued by more than 150 ms (for example while loading chunks), the server stops sending skin data to that player until it drains, for up to 1 second, then continues at the normal rate (about 160 KB/s).
- Players with clear connections still get skins as fast as in 1.3.7. The uploader is not affected (the measurements showed no ping change for uploaders).
- Works on Linux servers using the native (epoll) network transport, the default. On other servers delivery behaves as in 1.3.7.
Compatibility
- Server-side change only; network protocol unchanged (version 2). 1.3.2 and newer clients can connect.
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:RQtFfZ30:EbL1pDMZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RQtFfZ30:EbL1pDMZ"
}

