NewGen Team
专为 Paper 和 Folia 打造的团队、阵营与公会现代化基础框架
基于 Java 25 从零构建,完全异步,且完全由配置驱动——无需修改代码即可重塑服务器团队系统的视觉、体验与行为。
Discord • 文档 • 安装 • 常见问题
目录
- 简介
- 为什么选择 NewGen Team?
- 功能概览
- 配置系统
- GUI 系统
- 主题系统
- 语言系统
- 数据库
- 性能
- PlaceholderAPI
- 插件集成
- 开发者 API
- 命令
- 权限
- 安装
- 迁移指南
- 配置示例
- 常见问题
- 路线图
- 兼容性
- 截图
- 支持
- 许可证
2. 为什么选择 NewGen Team?
市面上大多数团队类插件设计于多年前,针对的是早已不复存在的服务器环境。它们假设服务器仅使用单一数据库、单一语言、固定的 GUI 界面和固定的配色方案。任何希望拥有不同风格的服务器都不得不采用变通方案、资源包黑客手段,或者依赖那些在一个赛季内就会过时的分支版本。
NewGen Team 基于一个不同的前提:插件应当适应服务器,而不是反过来。
这一前提塑造了每一个架构决策:
- 配置优于代码。 所有视觉元素——菜单布局、物品摆放、配色方案、文案——均存储在 YAML 文件中,而非编译在 jar 包里。更新插件绝不会覆盖或删除您的自定义设计。
- 默认异步。 所有数据库操作和重型计算均在主线程之外运行。在 Folia 上,这并非事后添加到遗留 Bukkit 代码库上的补丁——该插件从第一天起就是针对 Folia 的区域线程模型构建的。
- 一个核心,多种后端。 无论服务器是运行 20 人的 SQLite 生存服,还是 5,000 人的 PostgreSQL 网络服,其底层代码、功能集和配置模式完全一致。切换后端只需更改配置,而无需进行复杂的数据库迁移项目。
- 原生对话框与协议路由。 支持 Paper 的现代原生 Dialog API(适用于 1.21.6+ 客户端版本),同时自动为旧版客户端回退到虚拟告示牌。
- 主题作为一等公民。 颜色是令牌(tokens),而非硬编码字符串。MiniMessage 驱动每条消息、标题和 GUI 标签,使得文本出现的地方都能实现优雅的渐变、悬停提示和点击动作。
- 开箱即用的双语支持。 英语和越南语作为完整、专业结构化的翻译随附提供,具备自动回退机制,并在更新时安全合并键值。
3. 功能概览
原生 Dialog API 与协议路由
是什么: 一种现代化的用户输入服务,利用 Paper 的原生 Dialog API (io.papermc.paper.dialog.Dialog) 进行文本输入(团队命名、标签更改、余额管理、搜索),并配合协议检测使用。
优势: 消除了现代客户端上笨拙的告示牌界面和数据包黑客手段。玩家可以直接在带有自定义图标和主题化确认按钮的干净原生对话框中输入内容,而不会丢失背包焦点。
技术解释: PacketEvents 读取每个玩家的真实客户端版本。运行 >= 1.21.6 的客户端接收原生的 Paper 对话框。运行 < 1.21.6 的客户端(例如通过 ViaVersion 连接的 1.20 客户端)无缝回退到虚拟告示牌。输入方法也可以通过 gui.input-method 强制指定(AUTO, DIALOG, SIGN)。
异步存储引擎
是什么: 一个非阻塞的存储层,确保没有任何团队查询、银行交易或排行榜计算会阻塞服务器主线程或 Folia 区域线程。
优势: 即使在负载沉重的情况下也能保持稳固的 20.0 TPS,在团队创建高峰期无卡顿延迟,并在临时数据库连接延迟期间表现出极强的韧性。
技术说明: 所有查询均通过异步连接池执行器分发。仅在结果解析完成后,才会安全地将结果返回给调用线程。频繁的读取操作由具有可配置 TTL(生存时间)的内存缓存提供服务。
基于 HikariCP 的数据库层
是什么: 通用 SQL 后端支持——SQLite、MySQL、MariaDB、PostgreSQL——由 HikariCP 企业级连接池提供支持。
优势: 即时获取连接、网络断开时自动重连,且无需手动安装驱动程序(所有 JDBC 驱动程序均已着色并打包在 jar 文件中)。
GUI 布局与角色权限
是什么: 完全可配置的菜单,具备声明式槽位映射、物品描述(lore)、自定义模型数据以及细粒度的按角色权限控制。
优势: 拥有完全的自由度来重新设计界面或将纹理映射到自定义资源包,而无需触碰 Java 代码。超过 20 种细粒度权限可直接在游戏内 GUI 中按角色进行切换。
多页团队宝箱
是什么: 每个团队共享的虚拟容器,可根据团队等级进阶在多页之间扩展。
优势: 安全的物品共享机制,配合事务性自动刷新功能,防止库存不同步及服务器重启时的物品丢失。
团队银行与经济系统
是什么: 与 Vault 集成的共享货币池,支持存款、取款以及完整的交易审计功能。
团队主宅与热身快速路径
是什么: 中央团队传送点,具备可配置的冷却时间、热身倒计时以及移动取消检测功能。
每日审计日志
是什么: 分类的轮换日志文件(daily/、errors/、transactions/、admin/),存储于 plugins/NewGenTeam/logs/ 目录中。
4. 配置系统
NewGen Team 将其设置组织为模块化 YAML 文件:
| 文件 |
用途 |
config.yml |
语言选择(en_US、vi_VN) |
settings.yml |
核心游戏设置、输入方式(AUTO/DIALOG/SIGN) |
database.yml |
后端引擎(SQLite、MySQL、MariaDB、PostgreSQL)及连接池大小 |
theme.yml |
跨菜单和消息引用的中心颜色令牌 |
hooks.yml |
第三方集成(Vault、PlayerPoints、PlaceholderAPI、PacketEvents) |
menus/*.yml |
各菜单的布局、槽位、自定义模型数据和材质 |
lang/*.yml |
全面的语言文件,支持自动键值合并 |
levels.yml |
等级层级、成员容量、升级成本及特权 |
homes.yml |
团队主宅传送规则、热身及冷却时间 |
logs.yml |
文件日志类别及调试开关 |
chest.yml |
团队宝箱页数、尺寸及定期刷新间隔 |
5. GUI 系统
menus/ 下的菜单遵循声明式布局:
title: "<primary>团队菜单"
rows: 6
items:
bank:
slot: 31
material: GOLD_BLOCK
glow: true
custom-model-data: 1234
enabled: true
home:
slot: 29
material: RED_BED
glow: false
enabled: true
members:
slot: 33
material: PLAYER_HEAD
glow: false
enabled: true
文本、描述和标题通过 MiniMessage 解析,关联 theme.yml 和当前活动语言文件,实现设计与本地化的分离。
6. 主题系统
在 theme.yml 中定义的语义化颜色令牌:
colors:
primary: "#5865F2"
secondary: "#8A2BE2"
accent: "#FFD700"
muted: "#808080"
danger: "#E74C3C"
success: "#2ECC71"
warning: "#F1C40F"
info: "#3498DB"
直接在消息和菜单中引用:
messages:
team-created: "<success>您的团队 <primary><team_name></primary> 已创建!</success>"
7. 语言系统
自带完整的 英文 (en_US) 和 越南文 (vi_VN) 翻译。
缺失的键值会自动回退至 en_US。插件更新时会安全地合并新键值,而不会覆盖管理员的修改。
8. 数据库
| 后端 |
所需设置 |
推荐用于 |
| SQLite |
无(默认) |
单机生存模式、SMP |
| MySQL |
外部 MySQL 服务器 |
多服务器代理共享团队数据 |
| MariaDB |
外部 MariaDB 服务器 |
高性能多服务器设置 |
| PostgreSQL |
外部 PostgreSQL 服务器 |
拥有现有 Postgres 集群的大型网络 |
所有驱动程序均已着色并打包在 jar 文件中。如果启动时外部数据库暂时不可用,插件将回退到 SQLite,以确保游戏进程不受中断。
9. 性能与可扩展性(500+ 玩家)
- 批量击杀/死亡持久化: 击杀和死亡统计数据在内存中递增,并以 30 秒为周期刷盘写入,消除了大型团战期间数据库写入的性能瓶颈。
- O(1) 热身快速路径:
PlayerMoveEvent 以 O(1) 的时间复杂度评估 hasAnyWarmup()。当没有玩家正在热身主宅传送时,所有逐区块的地图遍历都会被跳过。
- 5 秒 TTL 排行榜缓存: 排名计算和 PlaceholderAPI 查询从记忆化快照中读取,防止在热路径上产生 O(n log n) 的排序开销。
- 异步资源指标: 资源使用命令异步遍历磁盘结构,确保服务器线程零掉帧。
10. PlaceholderAPI
标识符:newgenteam(所有占位符均直接从内存缓存中读取):
| 占位符 |
说明 |
%newgenteam_name% |
团队名称(若未加入团队则为空) |
%newgenteam_name_display% |
团队名称或可配置的备用文本 |
%newgenteam_tag% |
团队标签 / 前缀 |
%newgenteam_role% |
玩家角色(所有者、官员、成员、新兵) |
%newgenteam_owner% |
团队所有者的名称 |
%newgenteam_members% |
当前成员数量 |
%newgenteam_members_max% |
当前等级允许的最大成员上限 |
%newgenteam_online% |
在线团队成员数量 |
%newgenteam_level% |
团队等级 / 层级 |
%newgenteam_bank% |
团队金库余额 |
%newgenteam_kills% |
团队总击杀数 |
%newgenteam_deaths% |
团队总死亡数 |
%newgenteam_kdr% |
团队击杀/死亡比 |
%newgenteam_rank% |
排行榜排名位置 |
11. 插件集成
| 插件 |
用途 |
必需 |
| PacketEvents |
支持客户端版本检测和虚拟输入路由 |
是 |
| Vault |
将团队金库与服务器经济系统连接 |
否 |
| PlayerPoints |
用于团队层级升级的替代货币 |
否 |
| PlaceholderAPI |
暴露 %newgenteam_*% 占位符 |
否 |
12. 开发者 API
包:me.newgen.team.api.event — 可用于自定义集成的可取消 Bukkit 事件:
| 事件 |
触发时机 |
TeamCreateEvent |
创建了一个团队时 |
TeamDeleteEvent |
解散了一个团队时 |
TeamJoinEvent |
一名玩家加入团队时 |
TeamLeaveEvent |
一名玩家离开团队时 |
TeamKickEvent |
一名玩家被移出团队时 |
TeamLevelUpEvent |
团队提升了其层级时 |
BankDepositEvent |
向团队金库存入资金时 |
BankWithdrawEvent |
从团队金库取出资金时 |
13. 命令
玩家命令 (/team, /t, /f, /guild)
| 命令 |
说明 |
/team |
打开主团队仪表盘 |
/team create <name> |
创建一个新团队 |
/team invite <player> |
邀请一名玩家加入你的团队 |
/team join <team> |
请求加入一个开放加入的团队 |
/team leave |
离开当前团队 |
/team home |
传送至团队出生点 |
/team chat |
切换私人团队聊天频道 |
管理命令 (/newgenteam, /newgen)
| 命令 |
权限 |
说明 |
/newgen status |
newgenteam.status |
实时诊断监控器(JVM CPU/RAM、插件磁盘、活跃对象、任务开销) |
/newgen info |
无 |
服务器团队的公开摘要,包括总成员数和平均值 |
/team admin |
newgenteam.admin |
打开管理团队管理 GUI |
/team reload |
newgenteam.reload |
热重载所有配置、主题、菜单和语言文件 |
14. 权限
| 权限 |
说明 |
newgenteam.use |
访问玩家团队命令 |
newgenteam.status |
访问 /newgen status 诊断命令 |
newgenteam.admin |
访问管理面板和强制团队操作 |
newgenteam.reload |
访问 /team reload |
15. 安装
要求:
- Paper 或 Folia: 1.21.x – 26.3+
- Java 25+
- PacketEvents (必需依赖项,加载顺序为
BEFORE)
设置步骤:
- 将 PacketEvents 放入
plugins/ 目录。
- 将
NewGenTeam-1.2.0.jar 放入 plugins/ 目录。
- 启动服务器以在
plugins/NewGenTeam/ 中生成配置文件。
- 根据需要调整设置并运行
/team reload。
16. 迁移指南
在不同数据库类型(SQLite、MySQL、MariaDB、PostgreSQL)之间切换通过 database.yml 处理。驱动程序已预打包。在切换存储引擎之前请备份数据。
17. 配置示例
# settings.yml
gui:
# 输入方法:AUTO(推荐)| DIALOG | SIGN
input-method: AUTO
team:
max-name-length: 16
min-name-length: 3
disband-on-owner-leave: false
# database.yml
type: MYSQL
host: 127.0.0.1
port: 3306
database: newgenteam
username: root
password: "password"
pool-size: 10
connection-timeout: 5000
18. 常见问题
1. NewGen Team 是否支持 Paper 26.3 和 Java 25?
是的。该插件使用 Java 25 工具链和本地 Paper 26.3 库构建。
2. 它能在 Folia 上运行吗?
可以。所有任务调度和传送都通过 Folia 安全的区域调度器运行。
3. AUTO、DIALOG 和 SIGN 输入有什么区别?
AUTO 动态地将 Paper 对话框路由到 Minecraft 1.21.6+ 客户端,并将虚拟告示牌路由到旧版客户端。DIALOG 强制使用对话框,而 SIGN 强制使用告示牌输入。
4. 玩家可以使用 PlayerPoints 支付层级升级费用吗?
可以。在 levels.yml 中设置支付货币,并在 hooks.yml 中启用 PlayerPoints。
5. 如何更改颜色?
编辑 theme.yml 中的颜色标记。更改会在 /team reload 后即时传播到所有消息和菜单。
19. 路线图
- 通过 Redis / RabbitMQ 进行跨服务器同步
- 领地保护挂钩集成
- Web 仪表板伴侣应用
20. 兼容性
| 平台 |
支持版本 |
备注 |
| Paper |
1.21 – 26.3+ |
完全支持 |
| Folia |
支持 |
区域安全调度 |
| Purpur |
支持 |
兼容的 Paper 分支 |
| Java |
Java 25+ |
现代 Paper 所需 |
21. 截图
主团队仪表盘 (/team)
中央导航仪表盘,显示成员、金库、箱子、出生点、设置和团队进度。
细粒度角色权限
每个角色超过 20 种可自定义的权限,包括金库管理、邀请、箱子访问和出生点传送。
等级升级与套餐特权
交互式进度树,详细说明每个等级的箱子扩容、成员上限和家园限制。
多页团队箱
分页虚拟箱系统,具备自动交易刷新和库存保护功能。
实时资源诊断 (/newgen status)
深度检查工具,报告 JVM CPU、内存、磁盘占用、活动对象及内部任务耗时。
团队统计与性能
在一个集中视图中追踪团队击杀/死亡比、创建日期和余额。
团队设置与访问控制
直接从图形用户界面切换开放邀请、友军伤害和公开加入功能。
全服团队统计 (/newgen info)
公开摘要,显示总活跃团队数、总成员数、在线人数及平均值。
22. 支持
- Discord: discord.gg/P3NSwtJ2aw
- Bug 反馈: 提交包含您的 Paper/Folia 版本、Java 版本和服务端日志的 Issue。
23. 许可证
保留所有权利。
版权所有 © NewGen Team。未经版权所有者事先书面许可,不得复制、修改、重新分发或出售本软件及其相关文档。
专为期望从团队插件中获得更多体验的服务端打造。
Discord
NewGen Team
The modern foundation for teams, factions, and guilds on Paper and Folia
Built from the ground up for Java 25, fully asynchronous, and driven entirely by configuration — no code changes required to reshape how your server's team system looks, feels, and behaves.
Discord • Documentation • Installation • FAQ
Table of Contents
- Hero
- Why NewGen Team?
- Feature Overview
- Configuration System
- GUI System
- Theme System
- Language System
- Database
- Performance
- PlaceholderAPI
- Plugin Integrations
- Developer API
- Commands
- Permissions
- Installation
- Migration Guide
- Configuration Examples
- FAQ
- Roadmap
- Compatibility
- Screenshots
- Support
- License
2. Why NewGen Team?
Most team plugins on the market were designed years ago, for a server landscape that no longer exists. They assume a single database, a single language, a fixed GUI, and a fixed color scheme. Every server that wants something different is forced into workarounds, resource pack hacks, or forks that fall out of date within a season.
NewGen Team starts from a different premise: the plugin should adapt to the server, not the other way around.
That premise shapes every architectural decision:
- Configuration over code. Every visual element — menu layout, item placement, color palette, wording — lives in a YAML file, not in the jar. Updating the plugin will never overwrite or erase your custom designs.
- Async by default. Every database operation and heavy computation runs off the main thread. On Folia, this is not an afterthought bolted on top of a legacy Bukkit codebase — the plugin was built against Folia's region-threading model from day one.
- One core, many backends. Whether a server runs a 20-player SQLite survival world or a 5,000-player network on PostgreSQL, the exact same codebase, feature set, and configuration schema apply. Switching backends is a config change, not a database migration project.
- Native Dialogs & Protocol Routing. Supports Paper's modern native Dialog API for client versions 1.21.6+, while automatically falling back to virtual signs for legacy clients.
- Theming as a first-class feature. Colors are tokens, not hardcoded strings. MiniMessage powers every message, title, and GUI label, enabling clean gradients, hover text, and click actions anywhere text appears.
- Two languages out of the box. English and Vietnamese ship as complete, professionally structured translations with automatic fallback and safe key-merging on update.
3. Feature Overview
Native Dialog API & Protocol Routing
What it is: A modern user input service utilizing Paper's native Dialog API (io.papermc.paper.dialog.Dialog) for text input (team naming, tag changes, balance management, search), paired with protocol detection.
Benefits: Eliminates clumsy sign interfaces and packet hacks on modern clients. Players can type directly into clean native dialog boxes with custom icons and themed confirm buttons without losing inventory focus.
Technical explanation: PacketEvents reads each player's true client version. Clients running >= 1.21.6 receive native Paper dialogs. Clients running < 1.21.6 (such as 1.20 clients connecting via ViaVersion) seamlessly fall back to virtual signs. Input methods can also be forced via gui.input-method (AUTO, DIALOG, SIGN).
Async Storage Engine
What it is: A non-blocking storage layer ensuring no team query, bank transaction, or leaderboard calculation ever stalls the server main thread or a Folia region thread.
Benefits: Rock-solid 20.0 TPS even under heavy load, no lag spikes during team creation bursts, and resilient behavior during temporary database connection latency.
Technical explanation: All queries dispatch through an asynchronous connection-pooled executor. Results return safely to the calling thread only upon resolution. Frequent reads are served from an in-memory cache with configurable TTLs.
HikariCP-Backed Database Layer
What it is: Universal SQL backend support — SQLite, MySQL, MariaDB, PostgreSQL — backed by HikariCP enterprise connection pooling.
Benefits: Instant connection acquisition, automatic reconnection on network drops, and zero manual driver installations (all JDBC drivers are shaded inside the jar).
GUI Layout & Role Permissions
What it is: Fully configurable menus with declarative slot mapping, item lore, custom model data, and granular per-role permissions.
Benefits: Complete freedom to redesign interfaces or map textures to custom resource packs without touching Java code. Over 20 granular permissions can be toggled per role directly within the in-game GUI.
Multi-Page Team Chest
What it is: A shared virtual container per team that expands across multiple pages based on team tier progression.
Benefits: Safe item sharing with transactional auto-flush, preventing inventory desync and item loss across server restarts.
Team Bank & Economy
What it is: Shared currency pool integrated with Vault, supporting deposits, withdrawals, and full transaction auditing.
Team Home & Warmup Fast-Path
What it is: Central team teleportation point with configurable cooldowns, warmup countdowns, and movement cancelation checks.
Daily Audit Logging
What it is: Categorized, rotating log files (daily/, errors/, transactions/, admin/) stored in plugins/NewGenTeam/logs/.
4. Configuration System
NewGen Team organizes its settings into modular YAML files:
| File |
Purpose |
config.yml |
Language selection (en_US, vi_VN) |
settings.yml |
Core gameplay settings, input methods (AUTO/DIALOG/SIGN) |
database.yml |
Backend engine (SQLite, MySQL, MariaDB, PostgreSQL) and pool size |
theme.yml |
Central color tokens referenced across menus and messages |
hooks.yml |
Third-party integrations (Vault, PlayerPoints, PlaceholderAPI, PacketEvents) |
menus/*.yml |
Per-menu layout, slots, custom model data, and materials |
lang/*.yml |
Comprehensive language files with automatic key merging |
levels.yml |
Tier levels, member capacities, upgrade costs, and perks |
homes.yml |
Team home teleport rules, warmups, and cooldowns |
logs.yml |
File logging categories and debug toggles |
chest.yml |
Team chest pages, sizing, and periodic flush intervals |
5. GUI System
Menus under menus/ follow a declarative layout:
title: "<primary>Team Menu"
rows: 6
items:
bank:
slot: 31
material: GOLD_BLOCK
glow: true
custom-model-data: 1234
enabled: true
home:
slot: 29
material: RED_BED
glow: false
enabled: true
members:
slot: 33
material: PLAYER_HEAD
glow: false
enabled: true
Text, lore, and titles resolve through MiniMessage against theme.yml and the active language file, separating design from localization.
6. Theme System
Semantic color tokens defined in theme.yml:
colors:
primary: "#5865F2"
secondary: "#8A2BE2"
accent: "#FFD700"
muted: "#808080"
danger: "#E74C3C"
success: "#2ECC71"
warning: "#F1C40F"
info: "#3498DB"
Referenced directly inside messages and menus:
messages:
team-created: "<success>Your team <primary><team_name></primary> has been created!</success>"
7. Language System
Ships with complete English (en_US) and Vietnamese (vi_VN) translations.
Missing keys automatically fall back to en_US. Plugin updates merge new keys safely without overwriting administrator modifications.
8. Database
| Backend |
Setup Required |
Recommended For |
| SQLite |
None (Default) |
Single-server survival, SMP |
| MySQL |
External MySQL Server |
Multi-server proxies sharing team data |
| MariaDB |
External MariaDB Server |
High-performance multi-server setups |
| PostgreSQL |
External PostgreSQL Server |
Large networks with existing Postgres clusters |
All drivers are shaded inside the jar. If an external database is temporarily unreachable at boot, the plugin falls back to SQLite to keep gameplay uninterrupted.
9. Performance & Scalability (500+ Players)
- Batched Kill/Death Persistence: Kill and death statistics increment in-memory and flush to disk in 30-second cycles, eliminating database write bottlenecks during large team fights.
- O(1) Warmup Fast-Path:
PlayerMoveEvent evaluates hasAnyWarmup() in O(1) time. When no player is warming up a home teleport, all per-block map traversals are skipped.
- 5-Second TTL Leaderboard Cache: Rank calculations and PlaceholderAPI queries read from memoized snapshots, preventing O(n log n) sorting overhead on hot paths.
- Async Resource Metrics: Resource usage commands walk disk structures asynchronously to guarantee zero tick drops on the server thread.
10. PlaceholderAPI
Identifier: newgenteam (All placeholders read directly from in-memory cache):
| Placeholder |
Description |
%newgenteam_name% |
Team name (empty if not in a team) |
%newgenteam_name_display% |
Team name or configurable fallback text |
%newgenteam_tag% |
Team tag / prefix |
%newgenteam_role% |
Player role (Owner, Officer, Member, Recruit) |
%newgenteam_owner% |
Name of the team owner |
%newgenteam_members% |
Current member count |
%newgenteam_members_max% |
Maximum member limit for current tier |
%newgenteam_online% |
Count of online team members |
%newgenteam_level% |
Team level / tier |
%newgenteam_bank% |
Team bank balance |
%newgenteam_kills% |
Total team kill count |
%newgenteam_deaths% |
Total team death count |
%newgenteam_kdr% |
Team kill/death ratio |
%newgenteam_rank% |
Leaderboard rank position |
11. Plugin Integrations
| Plugin |
Purpose |
Required |
| PacketEvents |
Powers client version detection and virtual input routing |
Yes |
| Vault |
Connects team bank to server economy |
No |
| PlayerPoints |
Alternative currency for team tier upgrades |
No |
| PlaceholderAPI |
Exposes %newgenteam_*% placeholders |
No |
12. Developer API
Package: me.newgen.team.api.event — Cancellable Bukkit events for custom integration:
| Event |
Fired When |
TeamCreateEvent |
A team is created |
TeamDeleteEvent |
A team is disbanded |
TeamJoinEvent |
A player joins a team |
TeamLeaveEvent |
A player leaves a team |
TeamKickEvent |
A player is removed from a team |
TeamLevelUpEvent |
A team upgrades its tier |
BankDepositEvent |
Funds are deposited into team bank |
BankWithdrawEvent |
Funds are withdrawn from team bank |
13. Commands
Player Commands (/team, /t, /f, /guild)
| Command |
Description |
/team |
Open the main team dashboard |
/team create <name> |
Create a new team |
/team invite <player> |
Invite a player to your team |
/team join <team> |
Request to join an open team |
/team leave |
Leave current team |
/team home |
Teleport to team home |
/team chat |
Toggle private team chat channel |
Administrative Commands (/newgenteam, /newgen)
| Command |
Permission |
Description |
/newgen status |
newgenteam.status |
Real-time diagnostic monitor (JVM CPU/RAM, plugin disk, active objects, task cost) |
/newgen info |
None |
Public summary of server teams, total members, and averages |
/team admin |
newgenteam.admin |
Open administrative team management GUI |
/team reload |
newgenteam.reload |
Hot-reload all configurations, themes, menus, and languages |
14. Permissions
| Permission |
Description |
newgenteam.use |
Access to player team commands |
newgenteam.status |
Access to /newgen status diagnostic command |
newgenteam.admin |
Access to admin panel and forced team actions |
newgenteam.reload |
Access to /team reload |
15. Installation
Requirements:
- Paper or Folia: 1.21.x – 26.3+
- Java 25+
- PacketEvents (Required dependency, load order
BEFORE)
Setup:
- Place PacketEvents into your
plugins/ directory.
- Place
NewGenTeam-1.2.0.jar into your plugins/ directory.
- Start the server to generate configuration files in
plugins/NewGenTeam/.
- Adjust settings as desired and run
/team reload.
16. Migration Guide
Switching between database types (SQLite, MySQL, MariaDB, PostgreSQL) is handled via database.yml. Drivers are pre-bundled. Backup your data before switching storage engines.
17. Configuration Examples
# settings.yml
gui:
# Input method: AUTO (Recommended) | DIALOG | SIGN
input-method: AUTO
team:
max-name-length: 16
min-name-length: 3
disband-on-owner-leave: false
# database.yml
type: MYSQL
host: 127.0.0.1
port: 3306
database: newgenteam
username: root
password: "password"
pool-size: 10
connection-timeout: 5000
18. FAQ
1. Does NewGen Team support Paper 26.3 and Java 25?
Yes. The plugin is built with Java 25 toolchains and native Paper 26.3 libraries.
2. Does it run on Folia?
Yes. All task scheduling and teleports run through Folia-safe regional schedulers.
3. What is the difference between AUTO, DIALOG, and SIGN input?
AUTO dynamically routes Paper Dialogs to Minecraft 1.21.6+ clients and virtual signs to older clients. DIALOG forces dialog boxes, and SIGN forces sign input.
4. Can players pay for tier upgrades using PlayerPoints?
Yes. Set the payment currency in levels.yml and enable PlayerPoints in hooks.yml.
5. How do I change colors?
Edit color tokens in theme.yml. Changes propagate across all messages and menus instantly after /team reload.
19. Roadmap
- Cross-server synchronization over Redis / RabbitMQ
- Claiming / Territory protection hook integrations
- Web dashboard companion
20. Compatibility
| Platform |
Supported Version |
Notes |
| Paper |
1.21 – 26.3+ |
Fully supported |
| Folia |
Supported |
Region-safe scheduling |
| Purpur |
Supported |
Compatible Paper fork |
| Java |
Java 25+ |
Required for modern Paper |
21. Screenshots
Main Team Dashboard (/team)
Central navigation dashboard displaying members, bank, chest, homes, settings, and team progression.
Granular Role Permissions
Over 20 customizable permissions per role, including bank management, invitations, chest access, and home teleports.
Tier Upgrades & Package Perks
Interactive progression tree detailing chest expansion, member caps, and home limits per tier.
Multi-Page Team Chest
Paginated virtual chest system with automatic transaction flushing and inventory protection.
Real-Time Resource Diagnostic (/newgen status)
Deep inspection tool reporting JVM CPU, RAM, disk footprint, active objects, and internal task duration.
Team Statistics & Performance
Track team kill/death ratios, creation dates, and balance in one centralized view.
Team Settings & Access Control
Toggle open invitations, friendly fire, and public joining direct from the GUI.
Server-Wide Team Statistics (/newgen info)
Public summary showing total active teams, total members, online counts, and averages.
22. Support
- Discord: discord.gg/P3NSwtJ2aw
- Bug Reports: Open an issue with your Paper/Folia build, Java version, and server logs.
23. License
All Rights Reserved.
Copyright © NewGen Team. This software and its associated documentation may not be copied, modified, redistributed, or sold without prior written permission from the copyright holder.
Built for servers that expect more from their team plugin.
Discord
评论 0
登录后参与评分
还没有评论,来抢沙发吧