Voxel Shop beta is live. Expect occasional bugs. Learn more  
JustTeams icon

JustTeams 2.8.5

A Minecraft premium modern teams plugin

Page 1
justTeams 2.8.5

New
[1] /team glow me turns team glow off or back on just for you, for example when the outlines get in the way. The same switch is in /team usersettings. /team glow still turns it on or off for the whole team (owner and co owners). Your choice is saved, so it stays after a restart and on every server of a network.


[2] New relational placeholders %rel_justteams_relation_name% and %rel_justteams_glow_name% give the player name already in the relation or glow colour.


[3] %rel_justteams_relation_color%, %rel_justteams_glow_color% and the two name placeholders take an ending for other formats: _legacy gives &c, _hex gives #FF5555 and _mini gives <red>, for example %rel_justteams_relation_color_mini%. Without an ending they work as before.


Fixed
[4] On networks with Redis the console stays quiet now. Lines for every chat message and team update only show with settings.debug, a lost Redis connection is logged once with a short summary every five minutes, and reconnects wait longer between tries. While Redis is down, team chat goes through MySQL instead of failing. Team chat messages with a | in them no longer break on the other servers.


[5] The /team glow help now says that it switches the glow for the whole team.


Changed
[6] The allow_unicode comment in config.yml now explains what it allows (for example Chinese or Cyrillic team names) and what to look out for, and the FAQ has an entry on it.


Replace the JAR and restart. Existing settings and team data are retained. New messages are added to messages.yml on their own and the database gets a column for the personal glow choice. On a network, update every server that shares the database before starting them again.

justTeams 2.8.4

New


[1] The PvP button in the team menu and the public status button in the team settings can now do something different for each click. In gui.yml under click-actions, set each click (LEFT, RIGHT, SHIFT_LEFT, DROP for Q and so on) to toggle or none, or to on / off for PvP and public / private for the status. Every click still toggles by default.


[2] The words used by %justteams_pvp_status%, %justteams_team_public%, %justteams_pvp_toggle_cooldown% and %justteams_home_location% can now be changed in the placeholder_output section of placeholders.yml.


[3] Member heads in the team menu now fill in PlaceholderAPI placeholders such as %luckperms_prefix% for the member the head belongs to.


Fixed


[4] Other plugins could not find JustTeams since 2.8.3. Team support in JustDuel, the teammate checks in justCombat and justTerritory, and addons that use the JustTeams API work again.


[5] With features.team_tag set to false, team tags no longer show in the team list, invites, allies, leaderboard and admin menus.


[6] %justteams_display% shows the team name again instead of only the icon, and team_display.show_name works again.


Changed


[7] The plugin file now only hides private code. Every class name and every public method keeps its name, so addons keep working, and console errors show file names and line numbers again.


Replace the JAR and restart. Existing settings and team data are retained. On a network, update every server that shares the database before starting them again.

justTeams 2.8.3

Better protection of the plugin files. No config changes needed.


Replace the JAR and restart. Existing settings and team data are retained. On a network, update every server that shares the database before starting them again.

justTeams 2.8.2

[1] Added placeholders for each team member, for scoreboards that list the team line by line: %justteams_member_name_<n>%, plus the same with online, role, health, max_health or level in place of name. The teammate_ versions (for example %justteams_teammate_health_1%) leave out the player looking at the scoreboard. %justteams_teammate_papi_<n>_<placeholder>% shows any other placeholder for that member, such as %justteams_teammate_papi_1_auraskills_mana%. Vanished members show as offline.


[2] Added a Lands integration. Like ExcellentClaims and HuskClaims, team homes and warps can't be set in or teleported into land where no team member is trusted. Configure it under integrations.lands.


[3] Added <primary> and <secondary> colour tags for every message, menu name and lore line. Their colours are set in settings.colors in config.yml.


[4] Fixed %justteams_top_amount_<n>% always showing kills. It now shows the value the list is sorted by (settings.top_default_metric), like top_name and top_tag.


[5] The one second wait between team commands now only applies when the same command is repeated. Clicking two different menu buttons quickly no longer shows "Please slow down".


[6] Fixed the team ender chest staying open for a member who was kicked by an admin on another server of the network.


The permission based join fee (feature_costs.permission_based_join_fee) stays off by default for new installs. Existing configs keep their setting, so set it to false yourself if you don't want it.


Replace the JAR and restart. Existing settings and team data are retained. On a network, update every server that shares the database before starting them again.

JustTeams 2.8.1

[1] Fixed teammates and allies getting combat-tagged by combat plugins while team PvP is off. Hits between them are now blocked before other plugins see them, including arrows, tridents, snowballs, fishing rods, harmful splash and lingering potions, flame arrows and tamed pets. Healing potions still reach teammates.


[2] Team ender chest: members on the same server now share one live chest instead of getting "in use". Leaving the team, a disband or losing chest access, also on another server of the network, closes an open chest right away. Fixed a chest staying locked and unsaved when the last viewer closed it while a teammate was still opening it, and repeated save errors after disbanding with the chest open. On Folia one member at a time can open the chest, as before.


[3] Fixed paid team features (ender chest, home, set home, warp, set warp) charging the team bank and showing the bank message while the bank is switched off. They now pay like upgrades: bank first, wallet for the rest, and only the wallet while the bank is off. Renaming a team follows the feature_costs switches and shows the charge message.


[4] The bank_deposit and bank_withdraw prices in clan-settings were never charged. They are now charged when clan-settings.charge-bank-fees is true. The switch is off by default, so deposits and withdrawals stay free until you turn it on.


[5] Fixed team tags still showing in the leaderboard tag placeholders and in team, ally and /tm chat after setting features.team_tag to false.


[6] Fixed /teammsg showing a raw <team_color_close> tag and raw colour tags. Added /team chat <message> to send one team message without switching team chat on.


[7] Added settings.glow.use_color_teams. Set it to false to keep TAB sorting and nametag colours untouched while teammates glow. Added integrations.tab.enabled to turn the TAB hook off.


[8] Added %rel_justteams_glow_color%, %rel_justteams_relation_color% and %rel_justteams_relation% for TAB and nametag plugins that colour players per viewer. Fixed a new alliance not getting the ally glow colour until a reload.


[9] Fixed placeholders and English texts in translated messages: warp names, team colour tags with gradients, broadcasts, invites, combat messages, admin replies, /team points and /team platform now use each player's language.


[10] Any message can now be switched off by setting it to "". Nothing is sent then, no empty line and no lone prefix. Added settings.notify-updates to turn off the update notice for admins.


[11] The cancel word for chat prompts is now translatable (input_cancel_keyword in each language file). "cancel" keeps working.


[12] Fixed %justteams_join_date% and %justteams_created_at% ignoring date_time.join_date_format and date_time.timezone.


[13] Fixed promotion, invite and kick messages arriving twice with Redis enabled.


[14] Updates now add new options together with their comments, keep long texts on one line, and fill language files with the shipped translation instead of English. Fixed updates removing the empty dummy-items sections of gui.yml together with their explanation and examples.


[15] Config and language backups are no longer deleted after seven days. Added settings.backups.keep_per_file to keep only the newest copies of each file; the default -1 keeps all of them.


[16] /team help now lists every command you can use, 10 per page. Fixed /team gui not opening the menu. /team accept and /team deny work without a team name when you have one invite.


[17] Bedrock names can be typed with or without the Floodgate prefix in invite, kick, promote, demote, transfer and blacklist. Added bedrock_support.username_prefix for proxies with another prefix. Kick, promote, demote and transfer now work for offline members and never match only part of a name.


[18] A promotion over settings.max_co_owners now says the limit was reached instead of "Failed to promote player".


[19] Fixed menu buttons such as the PvP sword showing attack damage and attack speed. Added default-item-flags and per-item item-flags to gui.yml.


[20] PlaceholderAPI placeholders now work in menu titles, item names and lore.


[21] custom-model-data, item-model (1.21.4 and newer) and nexo-id now also work on the home button, list entries, page buttons and fill items. Fixed updates removing nexo-id, item-model, item-flags, enabled: false and added fill items from customised gui.yml files.


[22] Added a Quests button and a translatable "How it works" guide to the main team menu. On existing installs they only take free slots.


[23] The Team Prices buttons can now be set per click type (left, right, Q and others) in gui.yml. The PvP button accepts <status_text> as well as <status>.


[24] Fixed the quests menu ignoring its fill item. Added default-fill-item for menus without their own, and old material names such as STAINED_GLASS_PANE with data: 14 are understood. An unknown material is now named in the console.


[25] Fixed a warning about duplicate entries in messages.yml and the German, Spanish and French language files on Paper 26.2 and newer. The message texts are unchanged.


[26] Fixed the configuration health check reporting messages.yml, gui.yml, commands.yml and placeholders.yml as missing on the first start of a new installation.


Replace the JAR and restart. Existing settings and team data are retained. New keys are added to config.yml, messages.yml, gui.yml and the language files automatically, with their comments; the previous files are kept in the backups folder. On a network, update every server that shares the database before starting them again.

v2.6.4

Makes PacketEvents fully optional, stops your custom GUI items being wiped on update, and blocks look-alike team names. Adds admin bank commands, custom GUI buttons that run commands, resource-pack glyphs in tags and names, and explicit team or player targeting for the admin commands.


[1] PacketEvents is genuinely optional now. The plugin refused to start at all when PacketEvents was not installed, even though it has always been listed as an optional hook, because the chat input system referenced its classes directly and the server loads those before any setting is read. Those references are isolated now, so the plugin starts normally without PacketEvents and only Team Glow switches off. An installed but broken or mismatched PacketEvents no longer takes the plugin down either. Nothing changes if you already run it.


[2] Custom GUI items you added yourself are no longer deleted on update. The updater removed any key that was not in the shipped defaults, and everything under dummy-items in gui.yml is yours by definition, so custom decorative items and custom buttons were silently wiped the first time an update rewrote the file. That section is left alone now. This matters a lot with the new command buttons, which live in exactly that section.


[3] Team names can no longer be used to impersonate another team when Unicode names are turned on. Cyrillic and Greek letters that are drawn exactly like Latin ones (and full-width variants) meant a second team could take a name that looked identical to an existing one in chat, tab and every menu. Creation and rename now compare a folded form of the name, so those look-alikes are rejected as already taken. Names are still stored exactly as typed, genuinely different names in any language are unaffected, and the check only runs when settings.creation.allow_unicode is on.


[4] New admin bank commands: /team admin bank add <team> <amount>, remove and set. Handy for event rewards and fixing an economy by hand. Like the points command it also accepts a player name, in which case that player's clan is used, and it takes either argument order. The money change runs through the same atomic database step the player bank uses, so it cannot collide with a deposit or withdraw happening at the same moment on another server, it respects your maximum bank balance, and the other servers re-read the team straight away.


[5] Custom GUI items can run commands now. Any item you add under dummy-items in gui.yml takes a commands list, so a button can open another plugin's menu (zMenu and the like), run a warp, or hand out a reward. Prefix a line with [console] to run it from console or [player] to run it as the clicker, and [close] to close the menu. %player% and PlaceholderAPI placeholders both work. Commands fire a tick after the click with the menu already closed, which is what lets another plugin's inventory open cleanly.


[6] Optional resource-pack glyphs in tags and names, set separately for each. settings.creation.allow_custom_glyphs has a tag and a name switch, so you can let players put your pack's custom icons in their tag while keeping names plain, or the other way round. Both off by default. Only the Private Use Area range that packs use is allowed, so each icon counts as one character against your length limits and no formatting or invisible character can slip in. Players without your pack see an empty box.


[7] Admin commands can target a team or a player explicitly. /team admin points and /team admin bank accept team:<name> and player:<name>, so if a team happens to share a name with a player there is no guesswork about which one gets the points or money. A bare name behaves exactly as before.


Database changes run automatically on first boot and your team data is preserved. Drop the jar in and restart. New config keys are merged into your existing files, nothing you have set is touched.

v2.6.1

Makes the team name and tag prompts safe with CMI and other chat plugins, and folds in a batch of fixes from a full pass over the menus. If you already run 2.6.0, just drop this in, nothing to configure.


[1] Fixed the leaderboard category menu ignoring your gui.yml edits. Its title, item names and lore were being read from messages.yml, so editing the leaderboard-category-gui section in gui.yml did nothing (while the specific leaderboard view already read gui.yml, which is why that one worked). It now reads gui.yml like every other menu, so your edits apply, and any item you add or remove there shows up. The old leaderboard_category_* keys in messages.yml are no longer used and are removed on update.


[2] Fixed team name, tag, price and bank prompts leaking into public chat when you run CMI. When the plugin asks you to type something, that line is now caught at the packet level, before the server turns it into a chat message, so nothing downstream ever sees it. CMI (and some other chat plugins) take over chat and format it themselves without honoring another plugin's cancellation, which is why the text you typed for a prompt still got broadcast to everyone. This needs packetevents, which the plugin already uses for the glow feature; if it is not installed the plugin falls back to cancelling the chat event like before.


[3] Fixed the admin team-management menu failing to reopen after you set a balance, edited stats or kicked a member. It reopened the menu straight from the chat-input thread, which throws on Paper (async inventory open) and lands on the wrong region on Folia, so the menu silently did not come back and an error hit the log. Those now hop to the right thread first and the menu reappears.


[4] Admin menus re-check the justteams.admin permission on every click, not just when the menu is opened. If someone's admin access is taken away while they still have a menu open (common with timed permission grants), the menu stops working for them instead of letting them keep disbanding teams or setting balances through it.


[5] The admin member editor no longer acts on a member who already left. If another staff member kicks the player while you have their edit menu open, clicking now tells you they are no longer in the team instead of writing changes for someone who is gone.


[6] The team blacklist menu title now supports colors and gradients like the other menus. It was drawn as plain text before, so any color tags showed up literally. Also removed two duplicate admin sections from the default gui.yml that never took effect (it listed admin-team-list-gui and admin-team-manage-gui twice).


[7] The team leaderboard is cached for 30 seconds. Opening the top-teams menu ran a fresh database query every time; on a busy server the same list got re-queried constantly for numbers that barely move. It reuses the result for half a minute now.


[8] The three admin menus are now fully editable from gui.yml, the same as the player menus. The team list, the manage-team menu and the member editor read every button's material, name, lore and slot from their admin-team-list-gui, admin-team-manage-gui and admin-member-edit-gui sections, including the enabled and disabled look of each toggle. Before, these menus were built in code and ignored those sections, so editing them did nothing. Two buttons that only existed in code, teleport to home and view warps, are now in the config. On first load the updater adds them and bumps the gui version, making a backup first, so your edits are kept. If a key is missing the menu falls back to a built-in default for that item, so a partial or hand-edited section will not blank a slot or break the menu. Each team head in the list stores the team's real name, so a custom name-format cannot change which team a click opens. The member list in the manage menu no longer overlaps the bottom row on a full page.


[9] ExcellentClaims support. If you run ExcellentClaims, team teleports now respect land protection. A team can't teleport to a home or warp that sits inside a claim none of its members own, and can't set a home or warp while standing in one. A claim counts as the team's if any member owns it, so shared clan land is fine. You choose whether it's on and which of the two checks apply under integrations.excellentclaims in config.yml. It talks to ExcellentClaims through its API by reflection, so the plugin runs the same whether or not ExcellentClaims is installed, and if a check ever fails it lets the teleport through instead of blocking it.


[10] You can show a custom name for players instead of their Minecraft username. Set settings.player_name_placeholder to any PlaceholderAPI placeholder, for example %cmi_user_nickname%, and player names in the menus, member lists and team heads use that. Leave it empty, the default, to keep usernames. If PlaceholderAPI is missing or the placeholder has no value for a player, the username is used, so nothing breaks.


For server admins: drop the new JAR in and restart, nothing to change. Your config files update themselves and a backup is made first.Makes the team name and tag prompts safe with CMI and other chat plugins, and folds in a batch of fixes from a full pass over the menus. If you already run 2.6.0, just drop this in, nothing to configure.


[1] Fixed the leaderboard category menu ignoring your gui.yml edits. Its title, item names and lore were being read from messages.yml, so editing the leaderboard-category-gui section in gui.yml did nothing (while the specific leaderboard view already read gui.yml, which is why that one worked). It now reads gui.yml like every other menu, so your edits apply, and any item you add or remove there shows up. The old leaderboard_category_* keys in messages.yml are no longer used and are removed on update.


[2] Fixed team name, tag, price and bank prompts leaking into public chat when you run CMI. When the plugin asks you to type something, that line is now caught at the packet level, before the server turns it into a chat message, so nothing downstream ever sees it. CMI (and some other chat plugins) take over chat and format it themselves without honoring another plugin's cancellation, which is why the text you typed for a prompt still got broadcast to everyone. This needs packetevents, which the plugin already uses for the glow feature; if it is not installed the plugin falls back to cancelling the chat event like before.


[3] Fixed the admin team-management menu failing to reopen after you set a balance, edited stats or kicked a member. It reopened the menu straight from the chat-input thread, which throws on Paper (async inventory open) and lands on the wrong region on Folia, so the menu silently did not come back and an error hit the log. Those now hop to the right thread first and the menu reappears.


[4] Admin menus re-check the justteams.admin permission on every click, not just when the menu is opened. If someone's admin access is taken away while they still have a menu open (common with timed permission grants), the menu stops working for them instead of letting them keep disbanding teams or setting balances through it.


[5] The admin member editor no longer acts on a member who already left. If another staff member kicks the player while you have their edit menu open, clicking now tells you they are no longer in the team instead of writing changes for someone who is gone.


[6] The team blacklist menu title now supports colors and gradients like the other menus. It was drawn as plain text before, so any color tags showed up literally. Also removed two duplicate admin sections from the default gui.yml that never took effect (it listed admin-team-list-gui and admin-team-manage-gui twice).


[7] The team leaderboard is cached for 30 seconds. Opening the top-teams menu ran a fresh database query every time; on a busy server the same list got re-queried constantly for numbers that barely move. It reuses the result for half a minute now.


[8] The three admin menus are now fully editable from gui.yml, the same as the player menus. The team list, the manage-team menu and the member editor read every button's material, name, lore and slot from their admin-team-list-gui, admin-team-manage-gui and admin-member-edit-gui sections, including the enabled and disabled look of each toggle. Before, these menus were built in code and ignored those sections, so editing them did nothing. Two buttons that only existed in code, teleport to home and view warps, are now in the config. On first load the updater adds them and bumps the gui version, making a backup first, so your edits are kept. If a key is missing the menu falls back to a built-in default for that item, so a partial or hand-edited section will not blank a slot or break the menu. Each team head in the list stores the team's real name, so a custom name-format cannot change which team a click opens. The member list in the manage menu no longer overlaps the bottom row on a full page.


[9] ExcellentClaims support. If you run ExcellentClaims, team teleports now respect land protection. A team can't teleport to a home or warp that sits inside a claim none of its members own, and can't set a home or warp while standing in one. A claim counts as the team's if any member owns it, so shared clan land is fine. You choose whether it's on and which of the two checks apply under integrations.excellentclaims in config.yml. It talks to ExcellentClaims through its API by reflection, so the plugin runs the same whether or not ExcellentClaims is installed, and if a check ever fails it lets the teleport through instead of blocking it.


[10] You can show a custom name for players instead of their Minecraft username. Set settings.player_name_placeholder to any PlaceholderAPI placeholder, for example %cmi_user_nickname%, and player names in the menus, member lists and team heads use that. Leave it empty, the default, to keep usernames. If PlaceholderAPI is missing or the placeholder has no value for a player, the username is used, so nothing breaks.


For server admins: drop the new JAR in and restart, nothing to change. Your config files update themselves and a backup is made first.

Page 1
Owned
Ready to download
This resource is already attached to your account. You can download the latest file any time.

teams