小游戏框架
适用于 Paper Minecraft 1.21.x 的可扩展小游戏框架插件
一个功能强大且可扩展的小游戏框架,专为 Paper 服务器设计,具备基于队列的匹配、竞技场管理以及两个内置小游戏:Sumo Arena 和 Pillars of Fortune。该框架旨在通过 Minigame 接口轻松扩展自定义小游戏。
功能特性
- 队列系统:加入/离开队列,支持按竞技场类型区分(
type1、type2 等)
- 比赛生命周期:可配置倒计时(默认 3 秒)、比赛状态以及胜负处理逻辑
- 竞技场管理:通过游戏内命令创建和配置竞技场;YAML 配置文件位于
plugins/MinigameFramework/arenas/ 下
- 出生点/大厅配置:灵活的出生世界设置及可选的胜利奖励指令
- 小游戏开关:在
config.yml 中启用或禁用小游戏并自定义计时设置
小游戏
Sumo Arena
将对手击落平台!最后幸存的玩家获胜。平台会随时间自动缩小以保持比赛的紧张感。
- 模式:
type1 - 1v1(2 名玩家)
type2 - 4 人自由混战(FFA,4 名玩家)
- 配置:查看
config.yml 中的 sumo 部分以获取缩小计时设置
- 竞技场设置:竞技场文件存储在
arenas/sumo/*.yml 中。有关详细的竞技场格式说明,请参阅 arenas/sumo/README.md
Pillars of Fortune
在柱子上建造并生存!玩家若掉落到淘汰线以下(dq_y)或受到致命伤害将被淘汰。提供来自可配置物品池的物品分配功能,并在竞技场周围设有世界边界。
- 模式:
type1 - 1v1(2 名玩家)
type2 - 4 人自由混战(FFA,4 名玩家)
type3 - 8 人自由混战(FFA,8 名玩家)
type4 - 16 人自由混战(FFA,16 名玩家)
- 回合模式(随机权重生成):
- 普通模式:标准的带有物品分配的游戏玩法
- 上升岩浆:岩浆定期上升,迫使玩家向上移动
- 低重力:降低重力效果以提供独特的游戏体验
- 洗牌模式:定期重置玩家背包内容而非分配物品
- 配置:
config.yml 中的 pillars 部分用于设置模式权重和计时
itempools/pillars.yml 用于物品池配置
arenas/pillars/ 下的每个竞技场的 YAML 文件。有关竞技场格式说明,请参阅 arenas/pillars/README.md
配置
主配置
编辑 plugins/MinigameFramework/config.yml 进行以下配置:
- 出生点/大厅的世界设置
- 比赛倒计时时长
- 胜利奖励指令(可选,使用
{player} 占位符)
- 启用或禁用小游戏
- 小游戏的特定计时和选项
有关带注释的默认配置,请参阅 config.yml。
竞技场配置
竞技场按小游戏分别配置:
- Sumo:使用
/mg sumo create <name> <type> 创建竞技场,然后使用诸如 setworld、setspawn、addcorner、setdqlevel 和 setfloorlevel 等命令进行配置
- Pillars:使用
/mg pillars create <name> <type> 创建竞技场,然后使用 setworld、setspawn 和 setdqlevel 进行配置
有关详细的竞技场文件格式,请参阅:
arenas/sumo/README.md
arenas/pillars/README.md
编辑完竞技场文件后,请使用 /mg reload 加载更改。
命令
命令别名:/minigame、/mg、/game
玩家命令
| 命令 |
描述 |
/mg list |
列出所有可用小游戏及队列状态 |
/mg leave |
离开当前队列或比赛 |
/mg sumo join <type> |
加入 Sumo 队列(type1 或 type2) |
/mg sumo leave |
离开 Sumo 队列 |
/mg pillars join <type> |
加入 Pillars 队列(type1、type2、type3 或 type4) |
/mg pillars leave |
离开 Pillars 队列 |
管理员命令
| 命令 |
描述 |
权限 |
/mg reload |
重新加载所有配置文件和竞技场 |
minigames.reload |
/mg win <player> |
强制指定玩家赢得其当前比赛 |
minigames.admin |
Sumo 管理员命令
| 命令 |
描述 |
/mg sumo create <name> <type> |
创建新的 Sumo 竞技场配置 |
/mg sumo setworld <arenaName> |
设置竞技场的所在世界(站在世界中执行) |
/mg sumo setspawn <arenaName> <spawnIndex> |
设置出生点位置(站在该位置执行) |
/mg sumo addcorner <arenaName> <corner1|corner2> |
设置平台角落坐标 |
/mg sumo setdqlevel <arenaName> |
设置淘汰 Y 轴高度(站在该高度执行) |
/mg sumo setfloorlevel <arenaName> |
设置平台地板 Y 轴高度(站在该高度执行) |
Pillars 管理员命令
| 命令 |
描述 |
/mg pillars create <name> <type> |
创建新的 Pillars 竞技场配置 |
/mg pillars setworld <arenaName> |
设置竞技场的所在世界(站在世界中执行) |
/mg pillars setspawn <arenaName> <spawnIndex> |
设置出生点位置(站在该位置执行) |
/mg pillars setdqlevel <arenaName> |
设置淘汰 Y 轴高度(站在该高度执行) |
/mg pillars reload |
重新加载物品池配置 |
注意:所有管理员命令需要 minigames.admin 权限或 OP 状态。
权限
| 权限 |
说明 |
minigames.reload |
允许使用 /mg reload 命令 |
minigames.admin |
允许使用 /mg win 以及所有小游戏管理命令(如 create、setworld、setspawn 等) |
注意:服务器操作员(OP)无需显式权限即可访问所有命令。
PlaceholderAPI 集成
该插件与 PlaceholderAPI 集成,为玩家统计数据和竞技场可用性提供占位符。这对于使用 FancyHolograms 或其他记分板/全息图插件创建记分板非常有用。
安装
- 在服务器上安装 PlaceholderAPI
- Minigame Framework 将在启动时自动检测并注册其扩展
- 安装插件后,使用
/papi reload 重新加载占位符
玩家统计数据占位符
胜利次数:
%minigames_<minigame>_wins% - 特定小游戏的胜利次数
- 示例:
%minigames_pillars_wins% → "5"
- 示例:
%minigames_sumo_wins% → "3"
%minigames_total_wins% - 所有小游戏的总胜利次数
- 示例:
%minigames_total_wins% → "8"
击杀次数:
%minigames_<minigame>_kills% - 特定小游戏的击杀次数(目前仅追踪 Pillars)
- 示例:
%minigames_pillars_kills% → "12"
顶级玩家(排行榜):
%minigames_<minigame>_top_<rank>_name% - 指定排名(1-20)的玩家名称
- 按胜利次数降序排列,返回指定排名的玩家名称
- 如果该排名没有玩家,则返回空字符串
- 示例:
%minigames_pillars_top_1_name% → "PlayerName"
- 示例:
%minigames_sumo_top_5_name% → "AnotherPlayer"
- 示例:
%minigames_pillars_top_20_name% → "LastPlacePlayer"
%minigames_<minigame>_top_<rank>_wins% - 指定排名(1-20)的胜利次数
- 返回指定排名玩家的胜利次数
- 如果该排名没有玩家,则返回空字符串
- 示例:
%minigames_pillars_top_1_wins% → "25"
- 示例:
%minigames_sumo_top_5_wins% → "12"
- 示例:
%minigames_pillars_top_20_wins% → "3"
排行榜详情:
- 排行榜按胜利次数降序排列(胜利次数最高者排在前面)
- 平局时通过 UUID 进行排序以确保顺序一致
- 只有至少获得 1 次胜利的玩家才会被纳入排行榜
- 支持所有小游戏的 1-20 名排名
- 对所有当前和未来存在的小游戏均自动生效
竞技场可用性占位符
跟踪特定小游戏类型的可用或正在使用的竞技场数量:
%minigames_<minigame>_<arenaType>_arenas_available% - 可用竞技场数量
- 示例:
%minigames_pillars_type1_arenas_available% → "2"
%minigames_<minigame>_<arenaType>_arenas_in_use% - 当前正在使用的竞技场数量
- 示例:
%minigames_pillars_type1_arenas_in_use% → "1"
%minigames_<minigame>_<arenaType>_arenas_total% - 竞技场总数
- 示例:
%minigames_pillars_type1_arenas_total% → "3"
竞技场类型示例:
- 对于 Pillars:
type1, type2, type3, type4
- 对于 Sumo:
type1, type2
使用示例
FancyHolograms 记分板示例:
Top Pillars Players:
1. %player_name% - %minigames_pillars_wins% wins, %minigames_pillars_kills% kills
2. ...
全局统计记分板:
Your Stats:
Wins: %minigames_total_wins%
Pillars: %minigames_pillars_wins% wins, %minigames_pillars_kills% kills
Sumo: %minigames_sumo_wins% wins
竞技场状态显示:
Pillars Type1 Arenas:
Available: %minigames_pillars_type1_arenas_available%
In Use: %minigames_pillars_type1_arenas_in_use%
Total: %minigames_pillars_type1_arenas_total%
顶级玩家排行榜示例:
完整的 Pillars 前 20 名排行榜:
Top Pillars Players:
1. %minigames_pillars_top_1_name% - %minigames_pillars_top_1_wins% wins
2. %minigames_pillars_top_2_name% - %minigames_pillars_top_2_wins% wins
3. %minigames_pillars_top_3_name% - %minigames_pillars_top_3_wins% wins
4. %minigames_pillars_top_4_name% - %minigames_pillars_top_4_wins% wins
5. %minigames_pillars_top_5_name% - %minigames_pillars_top_5_wins% wins
6. %minigames_pillars_top_6_name% - %minigames_pillars_top_6_wins% wins
7. %minigames_pillars_top_7_name% - %minigames_pillars_top_7_wins% wins
8. %minigames_pillars_top_8_name% - %minigames_pillars_top_8_wins% wins
9. %minigames_pillars_top_9_name% - %minigames_pillars_top_9_wins% wins
10. %minigames_pillars_top_10_name% - %minigames_pillars_top_10_wins% wins
11. %minigames_pillars_top_11_name% - %minigames_pillars_top_11_wins% wins
12. %minigames_pillars_top_12_name% - %minigames_pillars_top_12_wins% wins
13. %minigames_pillars_top_13_name% - %minigames_pillars_top_13_wins% wins
14. %minigames_pillars_top_14_name% - %minigames_pillars_top_14_wins% wins
15. %minigames_pillars_top_15_name% - %minigames_pillars_top_15_wins% wins
16. %minigames_pillars_top_16_name% - %minigames_pillars_top_16_wins% wins
17. %minigames_pillars_top_17_name% - %minigames_pillars_top_17_wins% wins
18. %minigames_pillars_top_18_name% - %minigames_pillars_top_18_wins% wins
19. %minigames_pillars_top_19_name% - %minigames_pillars_top_19_wins% wins
20. %minigames_pillars_top_20_name% - %minigames_pillars_top_20_wins% wins
完整相扑前 20 名排行榜:
顶级相扑玩家:
1. %minigames_sumo_top_1_name% - %minigames_sumo_top_1_wins% 胜场
2. %minigames_sumo_top_2_name% - %minigames_sumo_top_2_wins% 胜场
3. %minigames_sumo_top_3_name% - %minigames_sumo_top_3_wins% 胜场
4. %minigames_sumo_top_4_name% - %minigames_sumo_top_4_wins% 胜场
5. %minigames_sumo_top_5_name% - %minigames_sumo_top_5_wins% 胜场
6. %minigames_sumo_top_6_name% - %minigames_sumo_top_6_wins% 胜场
7. %minigames_sumo_top_7_name% - %minigames_sumo_top_7_wins% 胜场
8. %minigames_sumo_top_8_name% - %minigames_sumo_top_8_wins% 胜场
9. %minigames_sumo_top_9_name% - %minigames_sumo_top_9_wins% 胜场
10. %minigames_sumo_top_10_name% - %minigames_sumo_top_10_wins% 胜场
11. %minigames_sumo_top_11_name% - %minigames_sumo_top_11_wins% 胜场
12. %minigames_sumo_top_12_name% - %minigames_sumo_top_12_wins% 胜场
13. %minigames_sumo_top_13_name% - %minigames_sumo_top_13_wins% 胜场
14. %minigames_sumo_top_14_name% - %minigames_sumo_top_14_wins% 胜场
15. %minigames_sumo_top_15_name% - %minigames_sumo_top_15_wins% 胜场
16. %minigames_sumo_top_16_name% - %minigames_sumo_top_16_wins% 胜场
17. %minigames_sumo_top_17_name% - %minigames_sumo_top_17_wins% 胜场
18. %minigames_sumo_top_18_name% - %minigames_sumo_top_18_wins% 胜场
19. %minigames_sumo_top_19_name% - %minigames_sumo_top_19_wins% 胜场
20. %minigames_sumo_top_20_name% - %minigames_sumo_top_20_wins% 胜场
自定义格式示例:
您可以在 FancyHolograms 或其他插件中自定义显示格式:
§6§l顶级方块塔玩家
§7排名 §e名称 §7- §a胜场
1. §e%minigames_pillars_top_1_name% §7- §a%minigames_pillars_top_1_wins%
2. §e%minigames_pillars_top_2_name% §7- §a%minigames_pillars_top_2_wins%
...
面向未来的设计
占位符系统自动支持新增的小游戏,无需修改代码。当您添加新的小游戏时:
- 胜场占位符自动生效:
%minigames_<newgame>_wins%
- 击杀占位符自动生效:
%minigames_<newgame>_kills%
- 竞技场占位符自动生效:
%minigames_<newgame>_<arenaType>_arenas_available%
- 顶级玩家排行榜占位符自动生效:
%minigames_<newgame>_top_<rank>_name% 和 %minigames_<newgame>_top_<rank>_wins%
只需在您的占位符中使用小游戏的名称(来自 Minigame.getName())和竞技场类型即可。排行榜将自动跟踪并按胜场对新添加的任何小游戏进行玩家排序。
统计数据存储
玩家统计数据存储在 plugins/MinigameFramework/stats.yml 中,并会自动保存:
- 定期保存(每 5 分钟)
- 服务器关闭时
- 每次获胜/击杀后(异步保存)
统计数据在服务器重启后保持不变,并按玩家 UUID 进行追踪。
Minigame Framework
Extensible minigame framework plugin for Paper Minecraft 1.21.x
A powerful, extensible minigame framework for Paper servers featuring queue-based matchmaking, arena management, and two built-in minigames: Sumo Arena and Pillars of Fortune. The framework is designed to be easily extended with custom minigames via the Minigame interface.
Features
- Queue System: Join/leave queues with per-arena-type support (
type1, type2, etc.)
- Match Lifecycle: Configurable countdown (default 3 seconds), match states, and win/loss handling
- Arena Management: Create and configure arenas via in-game commands; YAML configuration files under
plugins/MinigameFramework/arenas/
- Spawn/Lobby Configuration: Flexible spawn world settings and optional winner reward commands
- Minigame Toggles: Enable/disable minigames and customize timings in
config.yml
Minigames
Sumo Arena
Knock your opponents off the platform! The last player standing wins. The platform automatically shrinks over time to keep matches intense.
- Modes:
type1 - 1v1 (2 players)
type2 - 4 FFA (4 players)
- Configuration: See
config.yml sumo section for shrink timing settings
- Arena Setup: Arenas stored in
arenas/sumo/*.yml. See arenas/sumo/README.md for detailed arena format
Pillars of Fortune
Build and survive on pillars! Players are eliminated by falling below the disqualification level (dq_y) or taking lethal damage. Features item distribution from a configurable pool and a world border around the arena.
- Modes:
type1 - 1v1 (2 players)
type2 - 4 FFA (4 players)
type3 - 8 FFA (8 players)
type4 - 16 FFA (16 players)
- Round Modes (randomly weighted):
- Normal: Standard gameplay with item distribution
- Rising Lava: Lava rises periodically, forcing players upward
- Low Gravity: Reduced gravity effect for unique gameplay
- Shuffle: Inventory shuffles periodically instead of item distribution
- Configuration:
config.yml pillars section for mode weights and timing
itempools/pillars.yml for item pool configuration
- Per-arena YAML files in
arenas/pillars/. See arenas/pillars/README.md for arena format
Configuration
Main Configuration
Edit plugins/MinigameFramework/config.yml to configure:
- Spawn/lobby world settings
- Match countdown duration
- Winner reward command (optional, uses
{player} placeholder)
- Enable/disable minigames
- Minigame-specific timing and options
See config.yml for the default configuration with comments.
Arena Configuration
Arenas are configured per-minigame:
- Sumo: Create arenas with
/mg sumo create <name> <type>, then configure using commands like setworld, setspawn, addcorner, setdqlevel, and setfloorlevel
- Pillars: Create arenas with
/mg pillars create <name> <type>, then configure using setworld, setspawn, and setdqlevel
For detailed arena file formats, see:
arenas/sumo/README.md
arenas/pillars/README.md
After editing arena files, use /mg reload to load changes.
Commands
Command Aliases: /minigame, /mg, /game
Player Commands
| Command |
Description |
/mg list |
List all available minigames and queue status |
/mg leave |
Leave your current queue or match |
/mg sumo join <type> |
Join a Sumo queue (type1 or type2) |
/mg sumo leave |
Leave the Sumo queue |
/mg pillars join <type> |
Join a Pillars queue (type1, type2, type3, or type4) |
/mg pillars leave |
Leave the Pillars queue |
Admin Commands
| Command |
Description |
Permission |
/mg reload |
Reload all configuration files and arenas |
minigames.reload |
/mg win <player> |
Force a player to win their current match |
minigames.admin |
Sumo Admin Commands
| Command |
Description |
/mg sumo create <name> <type> |
Create a new Sumo arena configuration |
/mg sumo setworld <arenaName> |
Set the world for an arena (stand in the world) |
/mg sumo setspawn <arenaName> <spawnIndex> |
Set a spawn location (stand at the location) |
/mg sumo addcorner <arenaName> <corner1|corner2> |
Set platform corner coordinates |
/mg sumo setdqlevel <arenaName> |
Set disqualification Y level (stand at the level) |
/mg sumo setfloorlevel <arenaName> |
Set platform floor Y level (stand at the level) |
Pillars Admin Commands
| Command |
Description |
/mg pillars create <name> <type> |
Create a new Pillars arena configuration |
/mg pillars setworld <arenaName> |
Set the world for an arena (stand in the world) |
/mg pillars setspawn <arenaName> <spawnIndex> |
Set a spawn location (stand at the location) |
/mg pillars setdqlevel <arenaName> |
Set disqualification Y level (stand at the level) |
/mg pillars reload |
Reload the item pool configuration |
Note: All admin commands require the minigames.admin permission or OP status.
Permissions
| Permission |
Description |
minigames.reload |
Allows use of /mg reload command |
minigames.admin |
Allows use of /mg win and all minigame admin commands (create, setworld, setspawn, etc.) |
Note: Server operators (OPs) have access to all commands without explicit permissions.
PlaceholderAPI Integration
The plugin integrates with PlaceholderAPI to provide placeholders for player statistics and arena availability. This is perfect for creating scoreboards with plugins like FancyHolograms or other scoreboard/hologram plugins.
Installation
- Install PlaceholderAPI on your server
- The Minigame Framework will automatically detect and register its expansion on startup
- Use
/papi reload to reload placeholders after installing the plugin
Player Statistics Placeholders
Wins:
%minigames_<minigame>_wins% - Wins for a specific minigame
- Example:
%minigames_pillars_wins% → "5"
- Example:
%minigames_sumo_wins% → "3"
%minigames_total_wins% - Total wins across all minigames
- Example:
%minigames_total_wins% → "8"
Kills:
%minigames_<minigame>_kills% - Kills for a specific minigame (currently tracked for Pillars)
- Example:
%minigames_pillars_kills% → "12"
Top Players (Leaderboards):
%minigames_<minigame>_top_<rank>_name% - Player name at rank (1-20)
- Returns the player's name at the specified rank, sorted by wins (descending)
- Returns empty string if no player exists at that rank
- Example:
%minigames_pillars_top_1_name% → "PlayerName"
- Example:
%minigames_sumo_top_5_name% → "AnotherPlayer"
- Example:
%minigames_pillars_top_20_name% → "LastPlacePlayer"
%minigames_<minigame>_top_<rank>_wins% - Win count at rank (1-20)
- Returns the number of wins for the player at the specified rank
- Returns empty string if no player exists at that rank
- Example:
%minigames_pillars_top_1_wins% → "25"
- Example:
%minigames_sumo_top_5_wins% → "12"
- Example:
%minigames_pillars_top_20_wins% → "3"
Leaderboard Details:
- Leaderboards are sorted by wins in descending order (highest wins first)
- Ties are broken by UUID for consistent ordering
- Only players with at least 1 win are included in the leaderboard
- Supports ranks 1-20 for all minigames
- Works automatically for all current and future minigames
Arena Availability Placeholders
Track how many arenas are available or in use for specific minigame types:
%minigames_<minigame>_<arenaType>_arenas_available% - Count of available arenas
- Example:
%minigames_pillars_type1_arenas_available% → "2"
%minigames_<minigame>_<arenaType>_arenas_in_use% - Count of arenas currently in use
- Example:
%minigames_pillars_type1_arenas_in_use% → "1"
%minigames_<minigame>_<arenaType>_arenas_total% - Total count of arenas
- Example:
%minigames_pillars_type1_arenas_total% → "3"
Arena Type Examples:
- For Pillars:
type1, type2, type3, type4
- For Sumo:
type1, type2
Usage Examples
FancyHolograms Scoreboard Example:
Top Pillars Players:
1. %player_name% - %minigames_pillars_wins% wins, %minigames_pillars_kills% kills
2. ...
Global Stats Scoreboard:
Your Stats:
Wins: %minigames_total_wins%
Pillars: %minigames_pillars_wins% wins, %minigames_pillars_kills% kills
Sumo: %minigames_sumo_wins% wins
Arena Status Display:
Pillars Type1 Arenas:
Available: %minigames_pillars_type1_arenas_available%
In Use: %minigames_pillars_type1_arenas_in_use%
Total: %minigames_pillars_type1_arenas_total%
Top Players Leaderboard Examples:
Complete Pillars Top 20 Leaderboard:
Top Pillars Players:
1. %minigames_pillars_top_1_name% - %minigames_pillars_top_1_wins% wins
2. %minigames_pillars_top_2_name% - %minigames_pillars_top_2_wins% wins
3. %minigames_pillars_top_3_name% - %minigames_pillars_top_3_wins% wins
4. %minigames_pillars_top_4_name% - %minigames_pillars_top_4_wins% wins
5. %minigames_pillars_top_5_name% - %minigames_pillars_top_5_wins% wins
6. %minigames_pillars_top_6_name% - %minigames_pillars_top_6_wins% wins
7. %minigames_pillars_top_7_name% - %minigames_pillars_top_7_wins% wins
8. %minigames_pillars_top_8_name% - %minigames_pillars_top_8_wins% wins
9. %minigames_pillars_top_9_name% - %minigames_pillars_top_9_wins% wins
10. %minigames_pillars_top_10_name% - %minigames_pillars_top_10_wins% wins
11. %minigames_pillars_top_11_name% - %minigames_pillars_top_11_wins% wins
12. %minigames_pillars_top_12_name% - %minigames_pillars_top_12_wins% wins
13. %minigames_pillars_top_13_name% - %minigames_pillars_top_13_wins% wins
14. %minigames_pillars_top_14_name% - %minigames_pillars_top_14_wins% wins
15. %minigames_pillars_top_15_name% - %minigames_pillars_top_15_wins% wins
16. %minigames_pillars_top_16_name% - %minigames_pillars_top_16_wins% wins
17. %minigames_pillars_top_17_name% - %minigames_pillars_top_17_wins% wins
18. %minigames_pillars_top_18_name% - %minigames_pillars_top_18_wins% wins
19. %minigames_pillars_top_19_name% - %minigames_pillars_top_19_wins% wins
20. %minigames_pillars_top_20_name% - %minigames_pillars_top_20_wins% wins
Complete Sumo Top 20 Leaderboard:
Top Sumo Players:
1. %minigames_sumo_top_1_name% - %minigames_sumo_top_1_wins% wins
2. %minigames_sumo_top_2_name% - %minigames_sumo_top_2_wins% wins
3. %minigames_sumo_top_3_name% - %minigames_sumo_top_3_wins% wins
4. %minigames_sumo_top_4_name% - %minigames_sumo_top_4_wins% wins
5. %minigames_sumo_top_5_name% - %minigames_sumo_top_5_wins% wins
6. %minigames_sumo_top_6_name% - %minigames_sumo_top_6_wins% wins
7. %minigames_sumo_top_7_name% - %minigames_sumo_top_7_wins% wins
8. %minigames_sumo_top_8_name% - %minigames_sumo_top_8_wins% wins
9. %minigames_sumo_top_9_name% - %minigames_sumo_top_9_wins% wins
10. %minigames_sumo_top_10_name% - %minigames_sumo_top_10_wins% wins
11. %minigames_sumo_top_11_name% - %minigames_sumo_top_11_wins% wins
12. %minigames_sumo_top_12_name% - %minigames_sumo_top_12_wins% wins
13. %minigames_sumo_top_13_name% - %minigames_sumo_top_13_wins% wins
14. %minigames_sumo_top_14_name% - %minigames_sumo_top_14_wins% wins
15. %minigames_sumo_top_15_name% - %minigames_sumo_top_15_wins% wins
16. %minigames_sumo_top_16_name% - %minigames_sumo_top_16_wins% wins
17. %minigames_sumo_top_17_name% - %minigames_sumo_top_17_wins% wins
18. %minigames_sumo_top_18_name% - %minigames_sumo_top_18_wins% wins
19. %minigames_sumo_top_19_name% - %minigames_sumo_top_19_wins% wins
20. %minigames_sumo_top_20_name% - %minigames_sumo_top_20_wins% wins
Custom Formatting Example:
You can customize the display format in FancyHolograms or other plugins:
§6§lTop Pillars Players
§7Rank §eName §7- §aWins
1. §e%minigames_pillars_top_1_name% §7- §a%minigames_pillars_top_1_wins%
2. §e%minigames_pillars_top_2_name% §7- §a%minigames_pillars_top_2_wins%
...
Future-Proof Design
The placeholder system automatically supports new minigames without code changes. When you add a new minigame:
- Wins placeholders automatically work:
%minigames_<newgame>_wins%
- Kills placeholders automatically work:
%minigames_<newgame>_kills%
- Arena placeholders automatically work:
%minigames_<newgame>_<arenaType>_arenas_available%
- Top player leaderboard placeholders automatically work:
%minigames_<newgame>_top_<rank>_name% and %minigames_<newgame>_top_<rank>_wins%
Simply use the minigame's name (from Minigame.getName()) and arena types in your placeholders. The leaderboard will automatically track and sort players by wins for any new minigame you add.
Statistics Storage
Player statistics are stored in plugins/MinigameFramework/stats.yml and are automatically saved:
- Periodically (every 5 minutes)
- On server shutdown
- After each win/kill (async save)
Stats persist across server restarts and are tracked per player UUID.
评论 0
登录后参与评分
还没有评论,来抢沙发吧