
Core Teams
CoreTeams is a lightweight, modern, and highly configurable team management plugin designed for Spigot/Paper servers (1.20+). It features unique gradient-based team visuals, string-based IDs for custom team names, and a comprehensive admin GUI.
Tags
Creators
Details
4.1.0-SNAPSHOT
Compatibility
Changes
CoreTeams 4.1.0-SNAPSHOT
Clearer automatic team formats and easier player/admin menus, with full member browsing, better navigation, and more informative team-management screens.
Added
/ta autoteam TO2andTO3create teams of up to 2 or 3 players./ta autoteam 2Tand3Tcreate exactly 2 or 3 teams, distributing eligible players as evenly as possible. Any positive number works, and input is case-insensitive.- Tab completion suggests both team-size and team-count formats, plus the existing assignment modes. Plain numeric arguments continue to mean players per team.
- Automatic Teams menu in the admin browser, with examples explaining players per team versus number of teams, selection of
random,balanced,snake, orcaptains, and a shortcut to the existing command preview. - All Members browser for players and staff, including members beyond the seven shown on the team overview. Lists are paginated and sorted with the leader first, then online members and names.
- Search and Clear Search controls in the admin browser. Search and Create a Team shortcuts provide clickable command suggestions in chat.
- Leave Team confirmation with a clear explanation of leadership transfer or removal of the last member's team.
Changed
- Menus use subtle header/footer strips, readable control names, consistent action hints, and visible page indicators.
- Settings explain what they change and whether the next click enables or disables them. Open Joining is labelled Join Without an Invite; Friendly Fire is labelled Teammate Damage.
- Member-limit cards distinguish the server default, this team's setting, and its current limit. Increase/decrease controls describe their effect.
- Team splitting supports multiple pages and preserves selections between them. Selected players show green checks; the summary shows moving/staying counts and the new leader.
- Icon pickers identify the current icon with a green check. The custom model category is labelled Custom Icons.
- Merge previews show team summaries and explain which team is removed and where members will go.
- Empty team searches, invite lists, icon categories, and merge lists explain what to do next.
- Staff controls unavailable through permissions remain visible with an explanation. Teleport to Member is disabled while the player is offline.
Fixed
- Player Home buttons are no longer removed by the menu theme.
- Members beyond the first seven can be reached from the player/admin team overview; members beyond the first split page can also be selected.
- Returning from the split screen or merge-selection pages preserves the original admin-browser page.
- Split member cards no longer show a misleading Click to manage hint, and merge candidates describe opening a merge preview.
- Dragging items into modern team menus is blocked, matching their click protection.
- Mode tab completion no longer suggests assignment modes after
/ta autoteam apply.
Compatibility
- Exact team counts cannot exceed the number of eligible players. In captains mode, the eligible captain count must match the requested team count.
- Existing auto-team eligibility settings and
/ta autoteam applycontinue to work. Command previews now explain the requested size or count. - Java 21 and Paper requirements are unchanged. No storage migration is required.
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:AHAls57P:fm2WInTd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AHAls57P:fm2WInTd"
}
