Tags
Creators
Details
2.0.1
Compatibility
Changes
Fixes a packet that older clients cannot handle.
initTeam sends a REMOVE before the CREATE so that rebuilding the glow teams really changes their colour - a CREATE for a team the client already knows is ignored, so without it a config change would only ever reach players who reconnect. On a fresh join, though, the client has never seen those teams, and clients before 1.13 look the team up and then use it without checking for null. That REMOVE was going out for something that never existed there.
It is now only sent when the teams were created for that player before, which is exactly the rebuild case it was added for.
No API change, no config change. Everything in 2.0.0 applies unchanged.
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:dyy71SJC:id8mxJtY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dyy71SJC:id8mxJtY"
}

