Tags
Creators
Details
2.2.0
Compatibility
Changes
TeamsAPI now ships official extensions for three popular team plugins. Drop the
extension JAR in your plugins/ folder alongside the team plugin and TeamsAPI
will automatically pick it up as a provider. No code changes needed.
New: official provider extensions
TeamsAPI 2.2.0 introduces three ready-to-use provider extensions. Each is
bundled inside the main teams-api-plugin JAR and provisioned automatically to
plugins/TeamsAPI/extensions/ on first startup.
BetterTeams
extension (teams-api-extension-betterteams)
- Exposes teams, members, invites, warps, and ally/neutral relations through TeamsAPI.
- Invite support:
invitePlayeranddeclineInvitework for offline players;acceptInviterequires the invitee to be online at the time of the call. - Relation support covers
ALLYandNEUTRAL; BetterTeams does not model enemies or truces. MEMBER,ALLY, andNEUTRALrelation constants are supported.
Towny Advanced extension
(teams-api-extension-towny)
- Maps Towny towns to teams, residents to members, and nation relationships (ally/enemy) to TeamsAPI relation constants.
- Claim lookup fully supported; claim and unclaim mutations are not exposed (Towny manages its own chunk lifecycle).
MEMBER,ALLY,ENEMY, andNEUTRALrelation constants are supported;TRUCEis normalized toNEUTRAL.
KingdomsX extension
(teams-api-extension-kingdomsx)
- Maps KingdomsX kingdoms to teams, members to members, and diplomatic relations to TeamsAPI constants.
- Claim lookup supported; mutations return
false(require a liveKingdomPlayercontext not available through TeamsAPI). - Power read-only;
getPlayerMaxPowerandgetTeamMaxPoweralways return0.0(KingdomsX does not expose a per-player power ceiling in its public API). MEMBER,ALLY,TRUCE,ENEMY, andNEUTRALrelation constants are supported; relations are applied symmetrically.
New: extension management commands
| Command | Permission | Description |
|---|---|---|
/teamsapi install <extension> |
teamsapi.install (op) |
Copies a bundled extension JAR to plugins/TeamsAPI/extensions/. Valid names: betterteams, towny, kingdomsx. |
/teamsapi load <file>.jar |
teamsapi.load (op) |
Loads and enables an extension from plugins/TeamsAPI/extensions/ without a server restart. |
Installation quick-start
- The extension JARs are pre-bundled. TeamsAPI copies them to
plugins/TeamsAPI/extensions/on startup automatically. Nothing to download for first-time setup. - Run
/teamsapi install betterteams(ortowny/kingdomsx) to stage the extension for the next restart, or run/teamsapi load teams-api-extension-betterteams-2.2.0.jarto activate it immediately without a restart. - Install the matching team plugin if it is not already present, then restart (or reload) the server.
Full details and a feature matrix are in the Provider Catalog.
Optional dependencies
Supplementary resources
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:brvSO8Y1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2NJKwgXC:brvSO8Y1"
}

