Tags
Creators
Details
2.8.0
Compatibility
Changes
Version 2.8.0 Fixed players being disconnected with "Cannot remove from team 'JT_...'" or a similar team name while team glow is on. Glow no longer lets the client receive a team removal for a player it shows in a different team, whether the removal comes from vanilla teams, TAB, another plugin or an old JT_ team left in the world data. When glow ends after a kick, leave, disband or glow toggle, the player returns to their previous scoreboard team for the viewer, so nametag colours and prefixes are correct again. When another plugin puts a glowing player into a team, the glow colour comes back on the next update. Added settings.glow.color_mode. TEAM keeps the team colour, ROLE always uses the role colours, and RELATION shows your own team in one colour and every other team in another (relation_colors.own and relation_colors.other). Changes to glow settings now apply after /team reload. Added a points ranking to /team top. /team top kills, points, balance and members open a ranking directly. Added a colour button to the team settings menu. Owners and co-owners with justteams.setcolor can change the team colour there. Team name and tag errors now name the field, the typed value, the reason and the limit, including the characters that are not allowed and the blocked word. The command, the menu and the admin menu use the same rules. Added settings.min_tag_length and settings.creation.blocked_words. Chat prompts now work when another plugin cancels chat. Added /team input <answer> for servers where chat never reaches JustTeams, a clickable hint under each prompt, and a message when a prompt times out. Fixed typing the cancel word in the tag or description prompt setting it as the new tag or description. Fixed an empty team chat line after answering a prompt with team chat mode on. /team enderchest now tells administrators which config key switches the chest off. Quoted values such as "true" and older key names are read correctly and converted on startup. Members without chest access get their own message. Quest names, descriptions and all quest menu texts can now be translated per language. German quest texts are included. Fixed help lines showing /team <player> instead of /team invite <player> and similar.
Version 2.7.0 Added an optional limit for co-owners per team. Lowering the limit keeps existing ranks and prevents further promotions until a place becomes available. Added optional glow for mutually allied teams, with a separate color and the existing visibility and distance limits. Added CustomModelData and optional Nexo items for menu buttons and decorations. Unavailable Nexo items use the configured material. Added optional GriefPrevention checks for team homes and warps, using existing claim ownership and build trust. Fixed friendly-fire protection for TNT ignited by team members. Projectile and TNT damage can also be blocked while team PvP is enabled. Team administrator menus now check the administrator's current permission before changing members or their permissions. Fixed item duplication when a member is removed while their team chest is open. Reconnecting does not restore access to an old chest window. Restored the configured team-color and pending-invitation buttons. Fixed bank balance refreshes from console and system actions. Fixed update notices incorrectly recommending an older release.
Version 2.6.10 Restored the configured team-color button in the settings menu. Selecting a color updates the existing team and checks the player's permission again. Restored configured pending-invitation buttons in the menu for players without a team. Fixed Redis bank refreshes from console and system actions. Bank notifications now reload the stored balance instead of applying potentially outdated message values.
Updating Replace the JAR and restart. Existing settings and team data are retained. New keys are added to config.yml, messages.yml and gui.yml automatically; name and tag messages you have not edited are updated to the new texts. The blocked word list now defaults to admin, staff, moderator, console, server and minecraft; set settings.creation.blocked_words to change it. Tags need at least 2 characters on every path, set settings.min_tag_length to 1 to allow single-character tags. JustTeams needs Paper or a Paper fork such as Purpur or Folia; plain Spigot is not supported.
Coming from 2.6.x: back up team and player data, stop every backend sharing the database, replace the JAR on each backend, then restart. Existing settings and team data are retained. Do not mix older chest implementations with this release. Unfinished chest sessions remain locked until their contents have been reconciled.
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:DjgMtRwZ:HHK3hIRo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DjgMtRwZ:HHK3hIRo"
}

