BedwarsEventHoster
请确保已安装 Bedwars2023,否则此插件将无法运行!
这是一个 BedWars2023 的附加组件,可将两支队伍转换为 staged(分阶段)的对战模式——即先胜者或三局两胜制,玩家在游戏之间无需重新排队或重新选择队伍。你只需设置一次阵容,启动活动,插件便会将玩家移入和移出竞技场,记录比分,并在有人达到获胜条件时停止。
专为锦标赛之夜、训练赛和直播活动而设计,服务器每次只需运行一场比赛,并确保流程顺畅。
依赖要求
|
|
| Minecraft |
1.21.x |
| Java |
17+ |
| BedWars2023 |
5.0.0(必需) |
| PlaceholderAPI |
2.11.6+(可选) |
将 jar 文件放入 plugins/ 目录,启动一次服务器以生成配置文件,然后编辑 plugins/BedwarsEventHoster/config.yml 以自定义消息、倒计时或队伍颜色。
工作原理
- 创建你的队伍并填写阵容:
/bwevent team create team1
/bwevent team create team2
/bwevent team addplayer team1 aritive
/bwevent team addplayer team1 rukiamc
- 定义对战模式:
/bwevent match first-to 3 team1 vs team2
- 启动它:
/bwevent start
所有人都会收到公告,倒计时开始,两支队伍将被拉入竞技场,且阵容已锁定。当一场比赛结束时,会公布比分,玩家将返回等待下一场,如此循环直到有一支队伍达到获胜场次——届时将公布活动冠军及完整统计数据。
同一时间只能运行一个活动。当一个活动正在进行时,普通玩家无法加入该活动的竞技场,而活动参与者也无法在比赛中途退出。如果因有人离线导致比赛无法开始,插件会等待(并发送警告),若他们未上线则干净地中止活动。
命令
| 命令 |
说明 |
/bwevent team create <name> [players=p1,p2,...] [color] |
创建队伍,可选择性地添加在线玩家 |
/bwevent team delete <name> |
删除队伍 |
/bwevent team addplayer <team> <player> |
将玩家加入队伍 |
/bwevent team removeplayer <team> <player> |
将玩家移出队伍 |
/bwevent team list |
列出所有队伍及其成员名单 |
/bwevent match first-to/best-of <wins> <team1> vs <team2> |
设置对战阵容(胜场数 1–10) |
/bwevent match clear |
清除当前对战阵容 |
/bwevent start |
开始活动 |
/bwevent status |
显示对战阵容、比分和成员名单 |
/bwevent spec |
旁观正在进行的比赛 |
/bwevent stop |
强制停止活动并将所有人拉回大厅 |
/bwevent clear |
清除所有活动数据 |
/bwevent disable / enable |
阻止/允许所有人进行普通比赛 |
/bwevent alert |
向全服广播活动警报 |
/bwevent reload |
重载配置文件 |
别名:/bwe、/bwtournament。管理员命令需要权限 bwevent.admin(默认由 OP 拥有);bwevent.spec 和 bwevent.status 权限授予所有人。
断线处理
这部分通常是导致活动出错的地方,现已进行处理:
- 队伍中最后一名玩家在比赛中途断开连接 —— 比赛继续进行。如果他们的床仍然完好,他们可以重新加入并继续游戏;如果他们在离开期间床被摧毁了,他们将被移至旁观者模式,游戏按正常流程结算。
- 有人在等待大厅时离开 —— 游戏倒计时暂停,直到该玩家返回,以确保没有人以少打多。
- 玩家完全失联 —— 经过可配置的时间等待(
missing-player-wait,默认 300 秒),并在剩余 2 分钟、1 分钟和 30 秒时发出警告后,活动将停止,所有人返回大厅,避免无限期挂起。
- 自愿退出被阻止 —— 在活动进行中,退出物品、
/leave 命令以及退出 GUI 均不可用。
占位符
通过 PlaceholderAPI 注册(标识符为 bwevent):
| 占位符 |
值 |
%bwevent_current_score% |
当前比分,例如 2-1 |
%bwevent_game% |
当前比赛编号 |
%bwevent_status% |
对决类型,例如 first-to 3(先到三胜) |
%bwevent_team1% / %bwevent_team2% |
队伍名称 |
%bwevent_team1_score% / %bwevent_team2_score% |
各队得分 |
%bwevent_player_team% |
观看者所属的队伍 |
%bwevent_state% |
内部赛事状态 |
当没有正在进行的赛事时,所有占位符均显示为 None。将它们放置在你的计分板或玩家列表(Tab 界面)中,以便玩家跟踪系列赛进度。
配置
玩家看到的所有内容都存储在 config.yml 中——包括消息、倒计时、队伍颜色以及一个 missing-player-wait(缺失玩家等待)超时设置。此外,还有一个 after-game-start-commands 列表,用于在每场实际比赛开始时执行控制台或玩家命令:
after-game-start-commands:
- "<console-command>say Game %game_number%: %team1% vs %team2%"
- "<player-command>say gl!"
BedwarsEventHoster
Make sure Bedwars2023 is installed, or else this plugin wont work!
A BedWars2023 addon that turns two teams into a staged matchup — first-to or best-of — without anyone re-queuing or re-picking teams between games. You set the rosters once, start the event, and the plugin moves players in and out of arenas, keeps the score, and stops when someone hits the winning number.
Built for tournament nights, scrims, and stream events where the server only needs to run one match at a time and it needs to run cleanly.
Requirements
|
|
| Minecraft |
1.21.x |
| Java |
17+ |
| BedWars2023 |
5.0.0 (required) |
| PlaceholderAPI |
2.11.6+ (optional) |
Drop the jar in plugins/, start the server once so the config generates, then edit plugins/BedwarsEventHoster/config.yml if you want different messages, countdowns, or team colors.
How it works
- Create your teams and fill the rosters:
/bwevent team create team1
/bwevent team create team2
/bwevent team addplayer team1 aritive
/bwevent team addplayer team1 rukiamc
- Define the matchup:
/bwevent match first-to 3 team1 vs team2
- Start it:
/bwevent start
Everyone gets the announcement, a countdown runs, and both teams get pulled into an arena with their rosters already locked in. When a game ends the score is announced, players are sent back for the next one, and this repeats until a team reaches the winning number — then the event winner and full stats are posted.
Only one event runs at a time. While one is live, regular players can't join the event's arena and event players can't leave mid-game. If a match can't start because someone is offline, the plugin waits (with warnings) and aborts cleanly if they don't show.
Commands
| Command |
Description |
/bwevent team create <name> [players=p1,p2,...] [color] |
Create a team, optionally adding online players |
/bwevent team delete <name> |
Delete a team |
/bwevent team addplayer <team> <player> |
Add a player to a team |
/bwevent team removeplayer <team> <player> |
Remove a player from a team |
/bwevent team list |
List teams and their rosters |
/bwevent match first-to/best-of <wins> <team1> vs <team2> |
Set the matchup (wins 1–10) |
/bwevent match clear |
Remove the current matchup |
/bwevent start |
Start the event |
/bwevent status |
Show matchup, score, and rosters |
/bwevent spec |
Spectate the running event |
/bwevent stop |
Force-stop and pull everyone back to lobby |
/bwevent clear |
Wipe all event data |
/bwevent disable / enable |
Block/unblock normal matches for everyone |
/bwevent alert |
Broadcast an event alert to the whole server |
/bwevent reload |
Reload the config |
Aliases: /bwe, /bwtournament. Admin commands need bwevent.admin (op by default); bwevent.spec and bwevent.status are granted to everyone.
Disconnect handling
This is the part that usually breaks events, so it's handled:
- Last player on a team disconnects mid-game — the match keeps going. If their bed is still standing they can rejoin and keep playing; if it got destroyed while they were gone, they're moved to spectators and the game resolves normally.
- Someone leaves during a lobby wait — the game countdown pauses until they're back, so nobody starts a man down.
- Player goes missing entirely — after a configurable wait (
missing-player-wait, default 300s) with warnings at 2m/1m/30s, the event stops and everyone goes back to the lobby instead of hanging forever.
- Voluntary leaves are blocked — the leave item,
/leave, and the leave GUI don't work mid-event.
Placeholders
Register through PlaceholderAPI (identifier bwevent):
| Placeholder |
Value |
%bwevent_current_score% |
Current score, e.g. 2-1 |
%bwevent_game% |
Current game number |
%bwevent_status% |
Matchup type, e.g. first-to 3 |
%bwevent_team1% / %bwevent_team2% |
Team names |
%bwevent_team1_score% / %bwevent_team2_score% |
Individual scores |
%bwevent_player_team% |
The viewer's event team |
%bwevent_state% |
Internal event state |
All of them show None when no event is running. Throw them on your scoreboard or tab so players can follow the series.
Configuration
Everything players see lives in config.yml — messages, countdowns, team colors, and a missing-player-wait timeout. There's also an after-game-start-commands list that fires console or player commands each time a game actually starts:
after-game-start-commands:
- "<console-command>say Game %game_number%: %team1% vs %team2%"
- "<player-command>say gl!"
评论 0
登录后参与评分
还没有评论,来抢沙发吧