TeamX
一款为 Paper 1.21+ 打造的简洁而高效的团队插件。
创建团队,为其设置自定义的十六进制颜色,设定共享的家和末影箱,
使用团队聊天进行通讯,组建联盟,并通过一个整洁的 GUI 面板管理一切。
轻量级、可配置,且能与 TAB + PlaceholderAPI 良好配合,用于显示标签列表和头顶名称标签的颜色。
功能特性
- 团队 (Teams) — 创建、邀请(聊天中提供可点击的接受/拒绝按钮)、接受/拒绝、踢出、退出、解散
- 角色 (Roles) — 拥有者、官员、成员,支持
/team promote 与 /team demote
- 自定义 (Customization) — 团队十六进制颜色、重命名、描述、友军伤害开关
- 团队家 (Team home) —
/team sethome + /team home,带有动作栏预热倒计时
(移动、受到伤害或退出时取消)
- 共享末影箱 (Shared ender chest) — 大小可配置(9–54 格);当箱子缩小时,溢出的物品会安全地掉落给拥有者
- 团队聊天 (Team chat) —
/tc,可切换,带有 [Team] 前缀(与标签/名称标签标签分开保留)
- 广播 (Announce) — 向你的团队成员广播消息,可选 BossBar 显示
- 联盟 (Alliances) — 请求/接受/拒绝/解除,盟友间禁止 PVP,最大数量可配置
- 标签列表 + 头顶名称标签 — 通过 PlaceholderAPI (
%teamx_tag% 等) 与 TAB 集成。TeamX 会自动检测 TAB 并将渲染工作委托给它
- GUI 面板 —
/team 打开可点击菜单;解散操作有确认页面
/team list — 分页、可排序 (sort:members / sort:name)、可搜索,
带有可点击的前后翻页导航
- 音效 (Sounds) — 邀请、晋升/降级、团队创建、联盟事件音效
- 基于团队的 YAML 持久化 — 原子保存 +
.tmp 崩溃恢复机制
- 可配置的消息 — 支持 MiniMessage 和传统
& 颜色代码,多语言就绪
- 管理员工具 — 只读末影箱检查、物品扫描、
/team reload
命令
别名:/teams, /t
| 命令 |
描述 |
/team |
打开团队 GUI 面板 |
/team create <name> |
创建一个新团队 |
/team disband |
永久删除你的团队 |
/team invite <player> |
邀请一名玩家(他们会收到可点击的接受/拒绝选项) |
/team accept |
接受待处理的邀请 |
/team deny |
拒绝待处理的邀请 |
/team leave |
离开当前所在团队 |
/team kick <player> |
踢出一名成员(支持通过名称离线执行) |
/team promote <player> |
将成员提升为官员 |
/team demote <player> |
将官员降回成员 |
/team sethome |
将当前位置设为团队家 |
/team home |
传送至团队家(预热倒计时) |
/team delhome |
移除团队家 |
/team echest |
打开共享末影箱 |
/team chat [message] |
发送消息到团队聊天,或在没有消息时切换团队聊天模式 |
/team announce <message> |
向你的团队成员广播消息(+ BossBar) |
/team info [team] |
显示你的团队信息,或其他团队的信息 |
/team list [page] [sort:name|members] [search:term] |
浏览所有团队 |
/team rename <name> |
重命名你的团队 |
/team color <#hex|name> |
设置你的团队颜色 |
/team description <text> |
设置你的团队描述 |
/team settings |
打开设置 GUI(仅限拥有者) |
/team ally [request|accept|deny|break|list] [team] |
管理联盟关系 |
/team unally <team> |
/team ally break <team> 的快捷方式 |
/team friendlyfire |
切换同队 PVP(别名 /team pvp) |
/team help |
显示命令参考 |
团队聊天
| 命令 |
描述 |
/tc <message> |
向团队聊天发送消息(别名 /teamchat, /tchat) |
管理员命令 — 需要 teamx.admin 权限
| 命令 |
描述 |
/team admin echest <team> |
打开某团队共享末影箱的只读快照 |
/team admin echest scan <item> |
扫描每个团队的末影箱以查找特定物品(材质或名称) |
/team reload |
重载配置文件 + 消息 + 团队数据 |
权限
| 权限节点 |
默认值 |
描述 |
teamx.use |
true |
基础访问权限 — 使用 /team、/tc 以及 GUI 面板 |
teamx.create |
true |
创建一个新团队 |
teamx.admin |
op |
管理员权限 — /team reload 和 /team admin echest 工具 |
teamx.* |
op |
父节点 — 授予以上所有权限 |
LuckPerms 推荐设置
为所有玩家赋予基础节点,并为管理人员保留管理员权限:
/lp group default permission set teamx.use true
/lp group default permission set teamx.create true
/lp group admin permission set teamx.admin true
想要仅限捐赠者的团队?只需从 default 组中移除 teamx.create 并将其授予捐赠者组:
/lp group default permission set teamx.create false
/lp group vip permission set teamx.create true
teamx.* 是一个父节点,它授予 teamx.use、teamx.create 和 teamx.admin,
因此你通常只需要在拥有者/管理员身上设置它。
占位符 (PlaceholderAPI)
| 占位符 |
输出 |
%teamx_tag% / %teamx_prefix% |
带颜色的 [Team] 括号(准备好用于标签/名称标签) |
%teamx_team% |
团队显示名称 |
%teamx_color% |
团队颜色,格式为 &#rrggbb |
%teamx_role% |
你的角色 — Owner / Officer / Member |
%teamx_owner% |
团队拥有者的名称 |
%teamx_members% |
当前成员数量 |
%teamx_has_team% |
yes / no(常用于条件判断) |
所有占位符对于没有加入团队的玩家都会返回空值 / 0 / no,因此不在团队中的玩家不会显示任何内容。
在 TAB 中使用它们
将 %teamx_tag% 添加到你的 groups.yml 下的 _DEFAULT_(以及任何覆盖它的组)中:
_DEFAULT_:
tabprefix: "%teamx_tag%%luckperms-prefix%"
tagprefix: "%teamx_tag%%luckperms-prefix%"
tabprefix = 标签列表,tagprefix = 头顶名称标签。TeamX 会检测 TAB 并
放弃其自身的记分牌名称标签逻辑,以避免冲突。
配置亮点 (config.yml)
teams.max-members、teams.name-min/max-length、teams.name-regex
teams.default-color + teams.allowed-colors(为空 = 允许任意十六进制颜色)
home.warmup、home.cancel-on-move、home.cancel-on-damage、home.warmup-actionbar
echest.size(9–54,且为 9 的倍数)
announce.bossbar、announce.bossbar-seconds、announce.bossbar-color
sounds.enabled + 各事件的声音键值
list.page-size
tab / nametag 格式字符串(当未安装 TAB 插件时使用)
settings.locale、settings.legacy-color-codes
消息文件位于 messages.yml(支持 MiniMessage 和传统的 & 颜色代码)。
设置步骤
- 将
TeamX.jar 放入服务器的 plugins/ 文件夹中。
- 重启服务器(必须是完整重启,而非仅执行
/reload,以便正确解析软依赖的加载顺序)。
- (可选,用于标签页列表及头顶名字标签的颜色)安装 PlaceholderAPI 和 TAB,然后按照上述说明将
%teamx_tag% 添加到 TAB 的 groups.yml 中。
- 根据需要调整
config.yml 和 messages.yml,然后执行 /team reload。
要求与兼容性
- 服务器: Paper 1.21+(Purpur 兼容)。不兼容 Spigot(因为它使用了 Paper 的 Adventure/MiniMessage 文本组件)。
- Java: 21 或更高版本。
- 可选依赖: PlaceholderAPI(用于
%teamx_*% 占位符)、TAB(用于标签页列表及头顶名字标签渲染)。两者均为软依赖 —— TeamX 在没有它们的情况下也能正常运行,并在未检测到 TAB 时回退到使用基于记分板的自定义名字标签。
常见问题
如果没有安装 TAB / PlaceholderAPI,它能正常工作吗?
可以。未安装时,TeamX 会使用自带的记分板队伍来实现头顶标签,并使用 playerListName 来处理标签页列表。PAPI/TAB 集成只是在您已运行标签页插件时的推荐方案。
一个玩家可以加入多个队伍吗?
不可以 —— 默认情况下每个玩家只能属于一个队伍(teams.one-per-player: true)。将其设置为 false 即可允许多队归属。
队伍数据如何保存?
每个队伍在 plugins/TeamX/data/ 目录下对应一个 YAML 文件,采用原子写入方式。如果因崩溃留下 .tmp 临时文件,下次加载时会自动恢复。
是否支持 MySQL?
暂不支持 —— 仅采用基于文件的持久化存储(这是为了保持轻量级而刻意设计的)。
TeamX 是开源软件,采用 MIT 许可证。
TeamX
A simple but effective team plugin for Paper 1.21+.
Create teams, give them a custom hex color, set a shared home and ender chest,
talk in team chat, form alliances, and run it all from a clean GUI panel.
Lightweight, configurable, and plays nice with TAB + PlaceholderAPI for
tab-list and above-head nametag colors.
Features
- Teams — create, invite (clickable Accept/Deny in chat), accept/deny, kick, leave, disband
- Roles — Owner, Officer, Member with
/team promote & /team demote
- Customization — hex team colors, rename, description, friendly-fire toggle
- Team home —
/team sethome + /team home with an action-bar warmup countdown
(cancels on move, damage, or quit)
- Shared ender chest — configurable size (9–54 slots); overflow is safely
dropped to the owner when the chest shrinks
- Team chat —
/tc, toggleable, with a [Team] prefix (kept separate from the
tab/nametag tag)
- Announce — broadcast to your team, with an optional BossBar
- Alliances — request/accept/deny/break, PVP blocked between allies, configurable max
- Tab list + above-head nametag — integrates with TAB via PlaceholderAPI
(
%teamx_tag% and more). TeamX detects TAB and defers rendering to it automatically
- GUI panel —
/team opens a clickable menu; disband has a confirmation page
/team list — paginated, sortable (sort:members / sort:name), searchable,
with clickable prev/next navigation
- Sounds — invites, promotions/demotions, team creation, ally events
- Per-team YAML persistence — atomic saves +
.tmp crash recovery
- Configurable messages — MiniMessage + legacy
& color support, multi-locale ready
- Admin tools — read-only echest inspection, item scanning,
/team reload
Commands
Aliases: /teams, /t
| Command |
Description |
/team |
Open the team GUI panel |
/team create <name> |
Create a new team |
/team disband |
Permanently delete your team |
/team invite <player> |
Invite a player (they get a clickable Accept/Deny) |
/team accept |
Accept a pending invite |
/team deny |
Deny a pending invite |
/team leave |
Leave your current team |
/team kick <player> |
Kick a member (works offline by name) |
/team promote <player> |
Promote a member to Officer |
/team demote <player> |
Demote an Officer back to Member |
/team sethome |
Set the team home to your location |
/team home |
Teleport to team home (warmup countdown) |
/team delhome |
Remove the team home |
/team echest |
Open the shared ender chest |
/team chat [message] |
Send to team chat, or toggle team-chat mode with no message |
/team announce <message> |
Broadcast a message to your team (+ BossBar) |
/team info [team] |
Show info about your team, or another team |
/team list [page] [sort:name|members] [search:term] |
Browse all teams |
/team rename <name> |
Rename your team |
/team color <#hex|name> |
Set your team's color |
/team description <text> |
Set your team's description |
/team settings |
Open the settings GUI (owner only) |
/team ally [request|accept|deny|break|list] [team] |
Manage alliances |
/team unally <team> |
Shortcut for /team ally break <team> |
/team friendlyfire |
Toggle same-team PVP (alias /team pvp) |
/team help |
Show the command reference |
Team chat
| Command |
Description |
/tc <message> |
Send a message to team chat (aliases /teamchat, /tchat) |
Admin commands — requires teamx.admin
| Command |
Description |
/team admin echest <team> |
Open a read-only snapshot of a team's shared chest |
/team admin echest scan <item> |
Scan every team's chest for an item (material or name) |
/team reload |
Reload config + messages + teams |
Permissions
| Permission |
Default |
Description |
teamx.use |
true |
Base access — use /team, /tc, and the GUI panel |
teamx.create |
true |
Create a new team |
teamx.admin |
op |
Admin powers — /team reload and /team admin echest tools |
teamx.* |
op |
Parent node — grants all of the above |
Suggested LuckPerms setup
Give every player the base nodes, and reserve admin for staff:
/lp group default permission set teamx.use true
/lp group default permission set teamx.create true
/lp group admin permission set teamx.admin true
Want donator-only teams? Just withhold teamx.create from default and grant it
to a donor group:
/lp group default permission set teamx.create false
/lp group vip permission set teamx.create true
teamx.* is a parent that grants teamx.use, teamx.create, and teamx.admin,
so you usually only need it on owners/admins.
Placeholders (PlaceholderAPI)
| Placeholder |
Output |
%teamx_tag% / %teamx_prefix% |
Colorized [Team] bracket (ready for tab/nametag) |
%teamx_team% |
Team display name |
%teamx_color% |
Team color as &#rrggbb |
%teamx_role% |
Your role — Owner / Officer / Member |
%teamx_owner% |
Team owner's name |
%teamx_members% |
Current member count |
%teamx_has_team% |
yes / no (useful for conditions) |
All placeholders return empty / 0 / no for teamless players, so nothing
shows for players who aren't in a team.
Using them with TAB
Add %teamx_tag% to your groups.yml under _DEFAULT_ (and any group that
overrides it):
_DEFAULT_:
tabprefix: "%teamx_tag%%luckperms-prefix%"
tagprefix: "%teamx_tag%%luckperms-prefix%"
tabprefix = tab list, tagprefix = above-head nametag. TeamX detects TAB and
stands down its own scoreboard nametag logic so the two don't conflict.
Configuration highlights (config.yml)
teams.max-members, teams.name-min/max-length, teams.name-regex
teams.default-color + teams.allowed-colors (empty = any hex allowed)
home.warmup, home.cancel-on-move, home.cancel-on-damage, home.warmup-actionbar
echest.size (9–54, multiple of 9)
announce.bossbar, announce.bossbar-seconds, announce.bossbar-color
sounds.enabled + per-event sound keys
list.page-size
tab / nametag format strings (used when TAB is not present)
settings.locale, settings.legacy-color-codes
Messages live in messages.yml (MiniMessage + legacy & codes supported).
Setup
- Drop
TeamX.jar into your server's plugins/ folder.
- Restart the server (a full restart, not just
/reload, so the soft-depend
load order resolves).
- (Optional, for tab + above-head nametag colors) Install PlaceholderAPI and
TAB, then add
%teamx_tag% to TAB's groups.yml as shown above.
- Tweak
config.yml / messages.yml to taste, then /team reload.
Requirements & compatibility
- Server: Paper 1.21+ (Purpur works). Not compatible with Spigot (uses Paper's
Adventure/MiniMessage text components).
- Java: 21 or newer.
- Optional: PlaceholderAPI (for
%teamx_*% placeholders), TAB (for tab list +
above-head nametag rendering). Both are soft-dependencies — TeamX runs fine
without them, and falls back to its own scoreboard-based nametag when TAB isn't
present.
FAQ
Will it work without TAB / PlaceholderAPI?
Yes. Without them, TeamX uses its own scoreboard teams for the above-head tag and
playerListName for the tab list. The PAPI/TAB integration is just the recommended
path when you already run a tab plugin.
Can a player be in multiple teams?
No — one team per player by default (teams.one-per-player: true). Set it to
false to allow more.
How are teams saved?
One YAML file per team in plugins/TeamX/data/, written atomically. A leftover
.tmp from a crash is recovered on the next load.
Does it support MySQL?
Not yet — file-based persistence only, by design (keeps it lightweight).
TeamX is open-source and MIT-licensed.
评论 0
登录后参与评分
还没有评论,来抢沙发吧