Teams API

Initial release of TeamsAPI, a universal, provider-agnostic bridge plugin for Paper servers, modelled on Vault.

---

What is TeamsAPI?

TeamsAPI decouples plugins that provide team data (faction, clan, guild plugins) from plugins that consume it (scoreboards, chat formatters, quest systems). Neither side needs to know about the other. When the team plugin changes, every consumer keeps working without a recompile.

---

API highlights

• TeamsAPI static facade — getService(), isAvailable(), registerProvider(), unregisterProvider()
• TeamsService interface — team lifecycle, lookup, membership management, and predicate helpers
• Team / TeamMember — read-only snapshot interfaces; providers own the backing data
• TeamRole enum — OWNER (100) › ADMIN (50) › MEMBER (10) with outranks() and canManage()
• 5 cancellable events — TeamCreateEvent, TeamDeleteEvent, TeamJoinEvent, TeamLeaveEvent, TeamRoleChangeEvent
• Graceful fallback — if no provider is registered, isAvailable() returns false and all facade methods return safe empty/false values

---

Requirements

• Paper 26.1+
• Java 25+

---

Installation

Drop teams-api-plugin-1.0.0.jar into your server's plugins/ folder alongside a compatible team plugin, then restart.

---

For developers

Add the API to your project via JitPack:

• Maven - com.github.ez-plugins:teams-api:1.0.1 (scope provided)
• Gradle - compileOnly 'com.github.ez-plugins:teams-api:1.0.1'

See the Developer Guide for provider and consumer integration walkthroughs, and the API Reference for full method tables.