[lewisgibson]

/team is disabled in the base patch because the scoreboard is shared by every region. This enables it as a feature patch: every /team subcommand runs on the global region, like /time and /weather, so team changes are applied one at a time. The team maps become concurrent and the team options volatile so that Entity#getTeam, which was stubbed to return null, can read them from any region again. A joining player is sent the existing teams from a global region task and only receives team changes after that, so each team reaches it exactly once. /scoreboard, /teammsg and the Bukkit scoreboard API stay disabled. Like /time and /weather, the command's result is not returned to the caller, so execute store on /team gets 1.

Tested on ver/26.2.x with a headless client script that counts the team packets each client receives. 9 of 9 checks pass: team add, modify and join from the console, the set_player_team packet reaching a connected client, @s[team=red] matching and @s[team=blue] not (that is Entity#getTeam), a late joiner receiving each existing team once, every one of 9 clients seeing each of 40 teams exactly once while 6 of them join, and no exception or leftover team after the console and a player hammer add, join and remove on the same teams at once. On the unpatched build the first check fails because /team is not registered.

This was done with AI (Claude Opus 5.5 and GPT Astra, high effort). I've reviewed it and tested it myself.

[Dueris]

Do not spam this repository with your AI slop

[lewisgibson]

Hello. Have you actually reviewed the changes? This is not slop, and I know what I'm doing. I've been working on changes for a while and intentionally broke these out so they're easier to review