Links
Tags
Creators
Details
1.1.0
Compatibility
Required content
Changes
This update is a small but significant change: when players are already in a team, it will not put them in the afk team. When players are not in the afk team when returning, they will not be removed from their team.
The behavior <1.1 would naively override the team, and then leave whatever team the player was in regardless of if it had changed when the player returned.
I believe this new behavior is an improvement, but if it causes issues for you, please open an issue on GitHub and I'll look into it ASAP. However, this should be a more reliable system over all.
Tested on 1.18 and 1.21
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:cm4wuX9d:YSllOPtW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cm4wuX9d:YSllOPtW"
}

