justTeams

Teams, clans, guilds, whatever you call them

justTeams

Roles, a shared bank and ender chest, homes, warps, allies, team glow, quests and rankings. Players manage nearly all of it through menus, on one server or across a whole network.

Five stars, "Battle-tested".

• 3: roles per team
• 5: upgrade tiers
• Redis: instant network sync

Screenshot: "The team menu" (/team), titled "Team 5/12", with a member tooltip: "RowanVale [JE], Role: Co-Owner, Joined: 02 Aug 2026, Server: Local".

Feature list along the bottom: Roles and rights, Shared bank, Team ender chest, Homes and warps, Allies, Team glow, Quests and points, Cross-server.

The team menu: run the whole team from one menu.

/team opens members, bank, chest, home, warps, allies, quests and settings. The commands are still there for anyone who prefers typing.

• The member list. Hover a member to see their role, join date, platform tag and the server they are on right now.

• No accidents. Leaving, kicking, transferring and disbanding always ask first, and the disband button has a short delay against double clicks. (Screenshot tooltip: "Disband Team. Permanently deletes the team. This action cannot be undone!")

• Create a team with /team create <tag> <name>. The tag comes first, the name can have spaces

• Pick a solid colour or a hex gradient with /team setcolor or the colour button in team settings

• The colour follows the tag and name in chat and placeholders

• Public teams anyone can join, private teams with join requests, and /team browse to see every team

• Clear errors when a name or tag is rejected: which field, what was typed, the limit and the blocked word

• Chat prompts keep working when another chat plugin cancels chat, and /team input <answer> answers them without chat at all

Roles and rights: the owner decides who can do what.

Three roles per team plus switches per member, so a co-owner gets exactly the control you hand over and nothing more.

• Rights per member. Bank withdraw, ender chest, set home, use home and the management rights are switches in the member menu. No commands needed. (Screenshot tooltip: "Use Ender Chest. Allow this member to use the team ender chest. Status: ENABLED")

• Know who you promote. Role and join date on hover before you promote, demote or kick.

• Optional co-owner limit per team. Lowering it never demotes anyone, it only blocks new promotions

• Team size by rank: give a group justteams.size.<N> and its owners get a bigger member cap

• Hand the team over with /team transfer <player>

• Keep unwanted players out with the team blacklist

Shared storage: the team's money and loot, in one place.

A bank and an ender chest for the whole team, with rights per member and the same contents on every server.

• The team bank. A Vault balance with deposit and withdraw, a withdraw right per member and a maximum balance you set. (Screenshot: "Team Bank", "Current Balance. Balance: 47,350")

• The team ender chest. 1 to 6 rows, more with tier upgrades. Open it from the menu or with /team ec.

• One player at a time. Only one player can hold the team chest at a time, on one server or across a network. A member who is kicked or leaves loses access that moment, even with the window still open, and reconnecting does not bring an old chest window back.

• Bank changes are written to the database before other servers hear about them, so every server works with the same balance

• Feature costs: charge the team bank first and the player's wallet second. Items can be costs too

• Switch the bank, chest, home or warps off in the worlds you choose

Homes and warps: get the team together, wherever it is.

A team home and named warps with warmup and cooldown, optional passwords and prices. On a network they work across servers.

Team warps. Every warp shows which server it is on. Lock one with a password or put a price on it. (Screenshot: "Team Warps", a warp named "Vault", "Server: survival", "Password Protected".)

• /team sethome and /team home with warmup and cooldown. Tier upgrades shorten the cooldown
• As many warps as you allow, with a use right per member
• A home or warp on another backend sends the player there through Velocity or BungeeCord
• Claim checks for GriefPrevention, ExcellentClaims and HuskClaims: no homes or warps inside land the team has no right to
• With EternalCombat installed, teleports and other team actions can be blocked during combat

Team glow: spot your teammates through walls.

Teammates glow in the colour you choose, inside a range you set. Glow uses PacketEvents; without it, everything else keeps working.

Own team only. By default players see only their own team glow, up to 30 blocks away. Both can be changed. (Screenshot: a teammate's glowing outline visible through a tree trunk.)

• Allied teams can glow in a separate colour
• Plays well with TAB and other nametag plugins: when glow ends, nametag colours and prefixes are back to normal
• /team glow switches it per player, and /team visibility hides teammates completely for players who want a clear view
• Glow settings apply with /team reload

Allies and chat: talk to your team. Team up with others.

Team chat that reaches every server, alliances both sides confirm, and a channel for you and your allies.

• Allies. Send, accept and remove alliances from a menu. Both teams have to agree. (Screenshot: "Team Allies" menu with the ally "Emberwatch", "Click to remove ally!")

• Team chat and broadcasts. Invites, joins and leaves are announced to the team, each member in their own language. (Screenshot chat: "[Teams] You have invited Brambleton to your team.", "[Teams] Brambleton has joined the team.", team chat lines prefixed with the team tag, and an "[Ally]" line from a member of an allied team.)

• /team chat toggles team chat, #hello sends one quick line

• /team allychat (or /team ac) reaches your team and every ally

• Set a maximum number of allies, globally or per tier. Lowering it never breaks existing alliances

• Staff can follow every team chat with /team chatspy

• Team PvP toggle with a cooldown

• Friendly fire protection also covers arrows and TNT lit by teammates

Team quests: goals the whole team works on.

Teams get quests from a pool you control. Every member's progress counts, on every server, and the reward goes to the team.

• Shared progress. Blocks, kills and distance from every member add up toward one goal. (Screenshot: quest "Builders Guild, place blocks toward a shared build", progress 1640/2500, reward +200 points and +500.0 coins.)

• Points and money. A finished quest pays team points and bank money, claimed from the quest menu. (Screenshot: quest "Void Walkers, hunt down endermen as a team", progress 18/30, reward +500 points and +1200.0 coins.)

• 16 quests ready to go, 3 active per team by default, each with its own time limit

• Add your own quests in quests.yml

• Objectives: kill players, kill mobs, break blocks, place blocks and travel distance, plus a CUSTOM type other plugins can drive through the API

• No farming: player-placed blocks and re-placed blocks do not count, and killing the same player again only counts after 5 minutes

• Quest names and texts can be translated per language. German is included

• Staff can give, reset or complete a team's quests

Points and tiers: give teams something to climb.

Points rank the teams, tiers make them stronger, and buffs reward the ones that stick together.

Tier upgrades. Five tiers by default. Each one raises the member cap, chest rows, PvP damage bonus and home cooldown reduction. (Screenshot: "Team Upgrades, Tier 2/5". Next tier 3: max members 15, ender chest rows 5, damage bonus 2%, home cooldown reduction 20%, cost 50,000.)

/team top rankings:

• /team top opens all four rankings, /team top points opens one directly
• Pay for tiers with money, points or both. If one side cannot pay, the other is refunded, so an upgrade never half charges
• Team buffs: when enough members stand close together they get the effects the owner picked, such as Regeneration or extra mining XP, paid with points
• Leaderboard placeholders such as %justteams_top_points_1% for scoreboards and tab

Team prices: let owners set their own prices.

You choose which team actions an owner may price, and the highest price allowed. Members pay the team's price, the owner and permitted co-owners do not.

Team settings. Owners open Team Prices from settings or with /team prices. Left click sets a price, right click resets it. (Screenshot tooltip: "Team Prices. Set your team's own prices for the actions the server lets you change.")

• Opt in per action. Nothing changes until you allow it
• The join fee for public teams sits in the same menu
• Creating and renaming a team always use your prices
• Stored per team and synced across the network

The admin panel: every team, from one staff menu.

/team admin lists every team. Change members and their rights, bank and points, or look at a team's home, warps and chest.

• Rights at a glance. A member's role, online state and every right in one tooltip. Click to change them. (Screenshot: member "MiraLune", role MEMBER, online, withdraw disabled, ender chest enabled, set home disabled, use home enabled.)

• Look inside any team. Warps with name, coordinates and server, plus the team home and ender chest.

• Modules menu: turn quests, prices, upgrades, buffs, allies, ally chat and more on or off in game

• A module switch changes only its one line in config.yml, comments stay

• /team admin bank and /team admin points also run from the console, for schedulers and event scripts

• Force disband, kick, promote and demote. Staff permission is checked again on every click

• Optional auto disband for teams whose members have all been inactive for 30 days. Off by default

• Discord webhooks for new and disbanded teams, joins, leaves, kicks, promotions, invites and join requests

Networks: one team, every server.

Point every backend at the same MySQL or MariaDB database and teams, banks, chests and points stay in step. Add Redis and changes arrive in under 100 ms.

• One server: H2 file storage, nothing to set up.

• Network: shared MySQL or MariaDB, checked every few seconds.

• Network with Redis: instant updates over Redis.

• Team chat, member changes, bank, settings and disbands reach every server on Velocity or BungeeCord

• Each member shows online with the server they are on. Vanished staff stay hidden

• Homes and warps on other servers send players there through the proxy

Make it yours: menus and messages that fit your server.

Change any button or message, and let each player pick the language justTeams talks to them in.

• Menus. gui.yml controls every slot, material, name and lore. Buttons accept CustomModelData and Nexo items and fall back to the normal material when the Nexo item is missing. An optional Clan Forge menu skin is available.

• Languages. English, German, Spanish, French and Russian built in. Players pick theirs with /team usersettings, and any language can be added as lang/<code>.yml. Missing lines fall back to English.

• Placeholders. More than 90 PlaceholderAPI placeholders: tag, coloured tag, role, members online, bank, points, glow colour, teammates in range and leaderboard positions.

• MiniMessage everywhere, gradients included

• /guild and /clan aliases on by default, /party available, each one can be switched off

• Bedrock players through Floodgate and Geyser can be invited and kicked by name, and the menus show their platform

• Updates add new keys to your files and keep your comments

What's new: what changed lately.

2.8.1 is a small fix on top of 2.8.0. Full notes are on the Updates tab.

2.8.1 (current version):

• Fixed duplicate entries in messages.yml and the language files

2.8.0:

• Glow colour modes: TEAM, ROLE and RELATION
• Points ranking in /team top
• Colour button in the team settings menu
• Clearer name and tag errors, blocked words and a minimum tag length
• Prompts that work when another plugin cancels chat, plus /team input
• Quest texts per language, German included
• Glow no longer disconnects players when TAB or another plugin uses scoreboard teams

2.7.0:

• Optional co-owner limit per team
• Glow for allied teams in their own colour
• CustomModelData and Nexo items in menus
• GriefPrevention checks for homes and warps
• Friendly fire protection for arrows and TNT
• Admin menus check staff permission on every change

Commands: one command, and most of it is a menu anyway.

Players:

Staff:

justTeams, by kotori. Version 2.8.1.

• Owner, co-owner and member roles with rights per member
• Shared Vault bank and team ender chest
• Team home and warps, across servers too
• Allies, ally chat and team chat
• Team glow with TEAM, ROLE and RELATION colours
• 16 ready-made team quests
• Points, rankings, five tiers and team buffs
• Team prices set by owners, capped by you
• Admin menu with in-game module switches
• MySQL, MariaDB and Redis network sync
• Five languages, chosen per player
• Paper 1.21.4 to 26.3, plus Paper forks

Free download. Updates included, support on Discord.

Documentation: setup guides and the full command list. Install, roles, bank, glow, quests, placeholders and network setup. deltura.net/docs/justteams

Compatibility: built for Paper and its forks.

One jar for Paper and Paper forks such as Purpur and Folia. On a network, every backend runs that same jar against one shared database.

Supports from 1.21.4, every version in between, all the way to 26.3. Java 21, Java 25 on 26.x. Versions shown: 1.21.4, 1.21.5, 1.21.6, 1.21.7, 1.21.8, 1.21.9, 1.21.10, 1.21.11, 26.1.1, 26.1.2, 26.2, 26.3.

• Paper: 1.21.4 to 26.3
• Purpur: Paper fork
• Folia: Paper fork
• Velocity: network sync
• BungeeCord: network sync

Requirements:

• Java: Java 21 or newer; Java 25 for 26.x servers
• Server: Paper or a Paper fork. Plain Spigot is not supported: justTeams needs the Adventure API that Paper provides
• Plugins: Nothing else is required. Optional: Vault (bank and costs), PlaceholderAPI, PacketEvents (team glow), TAB, Nexo, GriefPrevention, ExcellentClaims, HuskClaims, EternalCombat, PvPManager, Phoenix, Floodgate
• Storage: H2 out of the box, MySQL or MariaDB for networks, Redis optional for instant sync