Skip to content

Teams#

BentoBox manages teams for game modes. Teams enable players to group together on one island. Teams have one owner, or leader, and at least one team member.

Team GUI#

When players issue the team command it brings up a GUI that enables them to see their team, invite other players, search for players, and manage the team. The commands can also be used, but players often like the GUI.

Team commands#

This is a list of team commands available to players. The command is used after the main player command, for example /island team for BSkyBlock.

Command Description Permission
team manage your team [gamemode].island.team
team accept accept an invitation [gamemode].island.team
team coop make a player coop rank on your island [gamemode].island.team.coop
team demote demote a player on your island down a rank [gamemode].island.team
team leave leave your island [gamemode].island.team
team invite invite a player to join your island [gamemode].island.team
team kick remove a member from your island [gamemode].island.expel
team promote promote a player on your island up a rank [gamemode].island.team
team reject reject an invitation [gamemode].island.team
team setowner transfer your island ownership to a member [gamemode].island.team
team trust give a player trusted rank on your island [gamemode].island.team.trust

The Main Team Command#

The main team command is team. To issue this command you must have an island. If run by itself, it will provide the following information to the player:

  • If the player is the owner, it will tell them how many players they can invite onto their team.
  • It will show all the members of the team. This includes info on the player's ranks, online/offline status, and when they were last seen online.

Team Sizes#

Teams can be any size and the maximum size can be set globally on a gamemode-basis or determine by a numbered permission given to the team owner. The default max team size is 4. The maximum number of coop and trusted members is also set to 4.

Team Size Permissions#

  • Team Size: The permission for team size is [gamemode].team.maxsize.X where X is a number.
  • Coop Size: [gamemode].team.coopsize.X where X is a number
  • Trust Size: [gamemode].team.trustsize.X where X is a number

Team Member Ranks#

BentoBox has the following team ranks built-in:

  • Owner - this is the owner of the island. There can be only one owner.
  • Sub-Owner - this is a member rank that has almost the same permissions as the owner. There can be multiple sub-owners.
  • Member - this is the default member rank.

Non-team member ranks#

Islands have other ranks that are related to teams but are not team members:

  • Trusted - this is a non-team member who has permanent permissions on the island, i.e., they have them until they are untrusted by a team member.
  • Coop - this is a non-team member who has temporary permissions on the island and these permissions will cease if the team member who gave them logs off, or if they are uncoop-ed.
  • Visitor - this is the default rank for any players who visit the island
  • Banned - these players have been banned by a team member and cannot enter the island

Configurable Rank Commands#

The owner of the island is able to grant access to team management commands to lower ranks via the Command Ranks menu in the in-game settings menu. This enables the owner to allow other members to invite other members, for example.

Promotion and Demotion#

Team members can be promoted or demoted by the island owner or an island member who has the rank required to use these commands.

A player cannot demote or promote themselves.

Currently, the only promotion or demotion possible is between the ranks of Member and Sub-Owner. In the future, additional ranks or custom ranks may be possible.

Joining Teams#

Inviting#

Players can be invited to join a team using the team invite command. To invite players to join a team, the inviter must be an island owner or have sufficient rank to use the command (see Configurable Rank Command). Players are invited by name and must be online. Invites can only be made to players who are not already on a team. If a player wants to switch teams, they must leave their current team before they can be invited. Invited players cannot be invited again until they reject the invite. Invited players can only have one active invite at a time. This includes team, coop and trusted invites. If a player receives a new valid invite while another is pending, the old one is replaced by the new invite. If the island team size is already at the maximum, the invite command will tell the user that the island is full.

Cooldown#

Invites can be abused by players, so BentoBox prevents the same player being invited to an island in the cool down period. The cool down is imposed on the island as a whole, so it is not possible for various members of the island to spam another player with invites. The default cool down times for the various invites are:

  • Team member - 60 minutes
  • Coop invite - 5 minutes
  • Trusted invite - 5 minutes See the game mode's config.yml to change.

Checking invites#

A player can check who has invited them by using the invite command with no arguments. This will show any current team, coop or trusted invites.

Accepting an invite#

A player accepts an invite by issuing the team invite accept command.

Confirmation#

The admin can decide whether confirmation is required or not for this command. The default is to require it for team membership but not require it for coop or trusted status. This is because team members lose their island if they join another one. If confirmation is required, the player will receive a warning that if they have an island then it will be lost. Once the player accepts the invite a second time, they will become a team member and teleport to the team island.

There is a small chance that the inviter loses the rank required to invite players before the player accepts the invite. In this case, the acceptance will not process and the user will be told that the invite is no longer valid.

Confirmation time

The default time players have to confirm a command is 10 seconds. If your players need more time, increase this value in BentoBox's config.yml. Players can also press the up arrow to recall the previous command rather than retyping it.

What happens when a player accepts#

When a player accepts a team invite, BentoBox automatically:

  • Removes them as owner of their previous island (if they had one) and begins deleting it
  • Clears the player based on the game mode's config settings (ender chest, inventory, money, health, hunger, experience)
  • Adds them as a member of the new island and teleports them to its home point

Inventory cleanup

By default, BentoBox does not clear a player's inventory when they join a team, to avoid accidents during initial setup. However, admins should enable this in the game mode's config.yml to prevent players from carrying items from their old island to the new one. Check the config for the on-join cleanup settings.

Rejecting an invite#

A player rejects an invite by issuing the team invite reject command.

A player must have a valid invite to reject otherwise they just receive an error. Once rejected, the inviter is notified.

Changing Team Ownership#

Owners can make another team member an owner using the team setowner command with the new owner's name as the parameter. Once ownership transfers, the previous owner becomes a Sub-Owner.

Owners must select a new owner before they can leave a team.

Kicking A Player#

Sometimes a team member needs to be forced out of a team. This is done using the team kick command. The owner can always kick players and the owner can allow lower-ranked team members to kick too via the Command Ranks menu in island settings. The team member does not have to be online to be kicked.

The command by default requires confirmation. This can be configured in BentoBox's config.yml.

When a player is kicked, BentoBox removes them from the island, runs any configured on-leave commands, cleans up their inventory/ender chest/money based on the game mode config, and notifies both parties. An invite cooldown is applied to prevent the exploit of repeatedly kicking and re-inviting players.

Leaving a Team#

A player can voluntarily leave a team using the team leave command. The command requires confirmation by default, but this can be switched off in the BentoBox's config. When leaving a team voluntarily, a player may use up one of their allowed island resets. This is set in the GameMode's config and the default is not to lose a reset. If the player will lose a reset, then they will be warned about it if the leave command has a confirmation requirements. Note: is it possible for a player to use up all their resets by leaving a team and therefore not be able to make a new island of their own. That is something admins will have to consider.

When a player leaves the island, the sequence and process is the same as when a player is kicked, except that the player may lose a reset.

Trusting and Cooping Other Players#

Sometimes players want to help out on other islands without having to join the team as a full member. This can be done by trusting a player or cooping an online player:

  • team trust <player>: the player becomes a permanent member of the island at a rank below Member
  • team coop <player>: the player becomes a temporary member of the island at a rank below Trusted

Island owners can trust or coops players and also enable lower-ranked players to use these commands via the Command Ranks page in the island settings.

These commands actually send an invite to the player that they can accept or reject, just like the team join command. If the invite is rejected, it will not be possible to send another invite for a cool down period, which is set to 5 minutes by default. This protects players from invite-spam.

If a player already has an invite pending from someone else or for a different rank, then that invite will be replaced by this one.

Once accepted, the player will receive the rank given for the new island. The inviter is notified of the acceptance.

Coop players hold their rank until the player who invited them logs out, or until the server shuts down, whichever occurs first.

Untrusting or uncooping players#

Island owners, or players with a high enough rank, can issue the team untrust or team uncoop commands to remove players from the island with these ranks. The removed player reverts to Visitor status.

Disabling Teams Per-World#

As of BentoBox 3.16.0, a game mode can opt out of the team subsystem on a per-world basis via the WorldSettings#isTeamsDisabled() API (default false). When enabled, the action commands that add, remove or reorganise team members refuse to run with the locale message commands.island.team.errors.teams-disabled.

Blocked when teams are disabled:

  • /island team invite and team invite accept (TEAM invitations only — COOP and TRUST invitations remain accepted)
  • /island team kick, team leave, team promote, team demote, team setowner
  • /[admin] team add

Still available:

  • Read-only player commands: /island team panel, team info, team invites, team invite reject
  • Trust and coop relationships: trust, coop, untrust, uncoop — these are the supported alternative when teams are off
  • Admin commands that operate on existing teams: kick, disband, disbandall, setowner, fix, maxsize

After flipping isTeamsDisabled on for a world that already has teams, run /[admin] team disbandall once to clean up pre-existing teams. This admin command strips every member and sub-owner from every island in the current world in one confirmable pass. Trusted and coop players are intentionally untouched.

What's new in v3.16.0

Released: 2026-05-10

See the full notes: Release 3.16.0

Team handling

  • New WorldSettings#isTeamsDisabled() API (default false) lets a game mode opt out of the team subsystem on a per-world basis.
  • New admin command /[admin] team disbandall strips every member and sub-owner from every island in the current world in one confirmable pass.
  • /[admin] team kick now requires explicit x,y,z coordinates when the target is on multiple team islands, and refuses to kick island owners (pointing the admin to setowner or disband instead).
  • Setowner cap is now enforced on both /island team setowner and /[admin] team setowner — transfers refuse when the recipient is at their concurrent-islands cap.

Bug fixes

  • ISLAND_RESPAWN no longer drops players at world spawn (0,0) when their home block is missing — it now walks a fallback chain ending in SafeSpotTeleport.
  • OFFLINE_GROWTH now blocks every spreading plant (vines, weeping/twisting vines, etc.) and trees/mushrooms growing from saplings — not just kelp and bamboo.
  • Dynmap area/polygon markers now use the world's full min/max height instead of always rendering at y=64.

API additions

  • CraftEngineHook.getItemStack(String id) and CraftEngineHook.getItemId(ItemStack item) let addons render and recognise CraftEngine custom items without depending on CraftEngine directly.

Locale

  • New keys: commands.admin.team.disbandall.{description,confirmation,success}, commands.island.team.errors.teams-disabled, commands.admin.team.setowner.errors.at-max.
  • Updated commands.admin.team.kick.cannot-kick-owner message that points admins to setowner/disband.
  • Removed the dead commands.admin.team.kick.success-all key.
  • All 22 bundled translations are in sync.

Compatibility: Paper Minecraft 1.21.5 – 26.1.2, Java 21+.

What's new in v3.16.2

Released: 2026-05-19

Small follow-up patch. See the full notes: Release 3.16.2

  • 🐛 Team-accept no longer eats inventories under InvSwitcher. Players who accepted a team invite while standing in a non-BentoBox world (with island.reset.on-join.inventory: true — Boxed and AOneBlock ship with this) could return to that world to find their items gone. The on-join inventory/XP/health/hunger/money resets now run after the teleport into the island world completes, so InvSwitcher (and similar plugins) save the player's real inventory under the old world before the reset fires. Fixes the case reported against AOneBlock 1.25.0 / Boxed 3.3.0 / InvSwitcher 1.17.1.
  • 🔺 API: Island.setRange no longer silently corrupts island data. setRange now refuses any value that disagrees with the game mode's configured distance-between-islands and logs the calling stack frame. Game modes that legitimately resize claims (e.g., StrangerRealms) continue to work — they already override GameModeAddon.isEnforceEqualRanges() to return false. If you maintain an addon and see Refusing Island.setRange(...) warnings, the log names the exact caller.
  • 🐛 CraftEngine 26.5+ compatibility. CraftEngineHook.getItemStack(id) now uses BukkitItemDefinition#buildBukkitItem() and works against the rewritten CraftEngine API.

Compatibility: Paper Minecraft 1.21.5 – 26.1.2, Java 21+.


Last update: May 23, 2026 01:58:08