Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 4 months ago
All versions
1.7.0
Release
TeamsAPI 1.7.05 months ago 10
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Added
TeamsNotificationServiceoptional extension interface for cross-plugin player notifications with provider-controlled authorization viasenderPlugin.- Dual notification type support:
enum-based built-ins (
TeamNotificationType) and custom string notification types for third-party plugin namespaces. - New
TeamsAPInotification facade methods:getNotificationService(),isNotificationAvailable(),registerNotificationProvider(plugin, service),registerNotificationProvider(plugin, service, priority),unregisterNotificationProvider(service). - New
TeamNotificationTypeenum with built-in categories:GENERAL,TEAM_JOIN,TEAM_LEAVE,TEAM_INVITE,TEAM_INVITE_ACCEPT,TEAM_INVITE_DECLINE. - New tests:
TeamsAPINotificationTest(service registration/availability/null-safety) andTeamNotificationTypeTest(enum contract coverage). - API reference docs and public listings updated with notification service method tables, enum documentation, and examples for both built-in and custom string types.
ClaimTerritoryTypeenum (WILDERNESS,TEAM,SAFE_ZONE,WAR_ZONE) to represent classic faction territory classes, including SafeZone and WarZone.TeamClaim.getTerritoryType()default method. Legacy providers map toTEAMautomatically unless they override.TeamClaim.getOwningTeamId()default method for territory-aware ownership lookups. Returns empty for non-team special territory.TeamsClaimServicedefault methods for special territory support:claimSafeZone(...),claimWarZone(...),unclaimSpecialZone(...),getTerritoryTypeAt(...),isSafeZone(...), andisWarZone(...).- API docs, developer docs, README, and public listings updated with new claim territory capabilities and examples.
TeamsAPI.API_VERSIONbumped to1.7.0.
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:2NJKwgXC:P3ZCy2VP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2NJKwgXC:P3ZCy2VP"
}

