躲藏或猎杀
隐藏你的信标。猎杀其他人的。最后存活的队伍获胜。
Hide Or Hunt 是一款基于团队的 Spigot 小游戏,核心围绕一个物品展开:你所在队伍的信标。
在宽限期开始时,每支队伍都会获得一个信标,并需要将其藏在地图上的某个位置。
只要你的信标未被破坏,你的队伍就可以无限重生。一旦有人找到并破坏了它,
下一次死亡将是永久性的——类似于 Bedwars 的最终击杀。最后一名存活玩家或信标仍矗立的队伍将获得胜利。
无需大厅设置、无需世界模板、无需竞技场结构图。直接指向你正在游玩的任何世界,设置一个散布区域,即可开始。
比赛流程
等待中 → (宽限前 PvP) → 宽限期 → 狩猎阶段 → 已结束 → 自动重置
| 阶段 |
发生的事件 |
| 等待中 |
管理员组建队伍,分配玩家,领取初始装备并设置出生点。 |
| 宽限前 PvP (可选,默认关闭) |
开局抢攻。队伍被分散,PVP 已开启——但此时信标尚不存在,因此无法拾取任何战利品,此阶段的死亡也不是最终的。纯粹为了早期装备而战斗。 |
| 宽限期 |
每支队伍的一名随机成员会获得该队的信标并负责隐藏它。无论设置如何,PVP 强制关闭,指南针失效。 |
| 狩猎阶段 |
指南针激活并开始指向敌方信标。PVP 遵循你的开关设置。信标开始接连被破坏。 |
| 已结束 |
宣布获胜者(或平局),然后插件会在十秒后重置回“等待中”状态——团队和出生点保持不变,准备下一轮比赛。 |
胜利条件在每次信标被破坏和每次死亡后重新检查,而非基于计时器,因此比赛一旦真正结束便会立即终止。
功能特性
? 无法作弊的队伍信标
每个队伍的信标是一个在其持久化数据容器中标记的真实物品——玩家挖掘或制作的普通信标完全不受影响,行为与原版一致。队伍永远不能破坏、移动或重新放置自己的信标,并且该方块受到保护,防止通过其他漏洞悄悄删除它:
- 爆炸——从 TNT 和方块爆炸的爆炸列表中移除。
- 活塞——如果会移动注册过的信标,则取消延伸和收缩动作。
- 无掉落——被摧毁的信标不会留下任何物品,因此无法被拾取并再次隐藏。
破坏一个信标,整个服务器都会听到动静。
? 最终击杀
| 信标状态 |
死亡时效果 |
| 矗立 |
在队伍起点正常重生。背包清空——除非开启了重生携带装备。 |
| 已销毁 |
最终击杀。 不掉落任何物品,你在坠落的确切位置以旁观者模式重生,可以观看比赛的剩余部分。 |
登出游戏不算淘汰。没有人会因为愤怒退游而将比赛拱手让人。
? 指南针追踪
右键点击任何原版指南针即可切换敌方信标目标——无需分发自定义物品,也无需制作。它仅锁定已放置且仍矗立的敌方队伍信标,在动作栏报告 (Tracking - Team Cyan - 142, 68, -391),且在狩猎阶段之前完全无效,这样没人能监视你隐藏信标。
? 实时记分板
一个无闪烁的侧边栏,显示当前阶段、倒计时或已过时间,以及每支队伍的实时状态——Alive(存活)、Not Placed(未放置)、No Respawns(无重生机会,信标已毁但仍在战斗)和 Eliminated(已淘汰)。每秒更新一次,并在任何状态变化时立即更新。所有玩家共享同一个记分板,这也是按队伍为名称、名字标签和标签页列表着色的原因。
⚙️ 游戏内管理员 GUI
/hoh gui 打开设置面板——可切换 PvP、自动熔炼、仅限信标合成、队伍聊天、全局冻结和重生携带装备,以及用于设置宽限期长度、宽限前 PvP 长度和队伍大小的铁砧输入字段。输入错误值时,它会重新打开铁砧界面而不是静默丢弃;退出则无任何更改。无需重载配置文件,无需重启服务器。
? 自动熔炼
可选。矿石掉落和怪物食物掉落已经是熔炼后的状态——生铁/金/铜、远古残骸、所有肉类和鱼类、土豆。转换发生在源头,因此一个方块永远不会同时掉落两种形态,并且优先请求原版掉落:效率魔咒仍然有效,精准采集依然可用。
? 冻结
三种叠加的作用范围——全局、按队伍、按玩家。被冻结的玩家无法移动、无法造成伤害也无法受到伤害,但保留头部旋转功能,以免他们卡住盯着墙壁看。
OP 在所有范围内始终豁免。
? 仅限信标合成
可选的硬核玩法:真正的工作台完全停止工作,游戏中唯一的 3×3 合成网格是你通过右键点击自己放置的队伍信标打开的那个。想合成?回家去。
⚔️ 宽限前 PvP 抢攻
可选的开局阶段,队伍带着初始装备被分散,PVP 已经开启,在此之前无人安全——争夺中心区域的装备确实需要付出代价。两条规则防止其独自决定比赛结果:信标尚未存在(没有战利品可抢),且抢攻导致的死亡并非最终击杀。
命令
所有内容都在 /hoh 下(别名 /hideorhunt)。运行 /hoh 或 /hoh help 列出你拥有权限的所有子命令——子命令、队伍编号和玩家名称均支持 Tab 补全。
| 指令 |
效果 |
/hoh team create |
创建下一个编号的队伍,并自动分配下一个颜色。 |
/hoh team invite <player> <team> |
直接将一名玩家加入指定队伍。 |
/hoh team list |
列出所有队伍、其颜色、状态和成员名单。 |
/hoh team clear |
清除所有队伍。 |
/hoh setKit |
将你当前的整个物品栏(快捷栏、主手、护甲、副手)保存为起始装备包。 |
/hoh setSpawn <team> [clear] |
将你所在的位置固定为该队伍的出生点,或执行 clear 以清除固定点(使队伍随机分散)。 |
/hoh setRegion <radius> |
设置以你为中心的分散区域半径(1–100000)。 |
/hoh gui |
打开管理员设置面板。 |
/hoh start |
开始比赛。 |
/hoh stop (别名 /hoh end) |
中止比赛并重置回“等待中”状态。 |
/hoh freeze global|team <n>|player <name> |
在任何范围内冻结游戏。使用 /hoh unfreeze 进行反向操作(解冻)。 |
/hoh tc <message> (别名 /hoh teamchat) |
仅限队伍内使用的聊天频道。 |
/hoh start 会预先验证所有条件,并明确指出错误所在——例如:拥有玩家的队伍少于两个、拥有在线玩家的队伍少于两个,或者需要分散但尚未设置区域的队伍。当命令拒绝执行时,任何状态都不会发生改变。
权限
| 节点 |
默认值 |
授予权限 |
hideorhunt.admin |
op |
除队伍聊天外的所有指令。 |
hideorhunt.play |
everyone |
/hoh tc。 |
快速入门
/hoh team create # 每个队伍执行一次
/hoh team invite Steve 1
/hoh team invite Alex 2
/hoh setKit # 手持你想要的初始装备时执行
/hoh setRegion 1500 # 分散区域,以你为中心
/hoh setSpawn 1 # 可选:将某支队伍固定在特定位置
/hoh start
安装方法
- 将 jar 文件放入服务器的
plugins/ 文件夹中。
- 启动服务器 ——
plugins/HideOrHunt/config.yml 会自动生成。
- 赋予管理员
hideorhunt.admin 权限(OP 已默认拥有该权限)。
队伍出生点、起始装备包以及所有设置都会在重启后保留。队伍名单按设计为会话级(session-level)——只需通过 /hoh team create 和 /hoh team invite 即可在数秒内重建。
支持最多 九支队伍,每支队伍拥有独立的颜色(灰色、红色、绿色、青色、白色、紫色、黄色、浅蓝色、蓝色)。如果尝试添加第十支队伍,系统会给出明确提示予以拒绝,而不会静默地让两支队伍共享同一颜色。
兼容性
|
|
| 平台 |
Spigot 1.21.11 —— Paper 及其分支也可用,但未使用仅 Paper 可用的 API |
| Java |
21 |
| 依赖项 |
无 |
基于当前 API 构建,无任何弃用警告 —— 没有遗留的 openWorkbench,没有 fromLegacyText,并且铁砧输入使用的是真正的 AnvilView,因此其行为与真实铁砧完全一致。
灵感来源于 Hide or Hunt 游戏模式。
Hide Or Hunt
Hide your beacon. Hunt everyone else's. Last team standing wins.
Hide Or Hunt is a team-based Spigot minigame built around one object: your team's beacon.
Every team gets one at the start of the grace period and has to hide it somewhere on the map.
While your beacon stands, your team respawns forever. Once someone finds it and breaks it,
the next death is permanent — Bedwars-style final kills. The last team with a surviving
player or a standing beacon takes the win.
No lobby setup, no world templates, no arena schematics. Point it at whatever world you're
already playing on, set a scatter region, and start.
How a match plays
WAITING → (PRE-GRACE PVP) → GRACE PERIOD → HUNTING → ENDED → auto-reset
| Phase |
What happens |
| Waiting |
Admins build teams, assign players, capture the starter kit and set spawns. |
| Pre-Grace PVP (optional, off by default) |
An opening rush. Teams are scattered and PVP is already live — but no beacon exists yet, so nothing can be looted, and no death here is final. Pure fight for early gear. |
| Grace Period |
One random member of each team is handed that team's beacon and has to hide it. PVP is forced off and compasses are dead, no matter what the settings say. |
| Hunting |
Compasses go live and start pointing at enemy beacons. PVP follows your toggle. Beacons start falling. |
| Ended |
Winner (or draw) announced, then the plugin resets itself back to Waiting after ten seconds — ready for the next round with teams and spawns intact. |
The win condition is re-checked after every beacon break and every death, never on a
timer, so a match ends the instant it's actually over.
Features
? Team beacons that can't be cheesed
Each team's beacon is a real item tagged in its persistent data container — plain beacons players
mine or craft are completely untouched and behave exactly like vanilla. A team can never break,
move, or re-place its own beacon, and the block is protected from the loopholes that would
otherwise let them delete it quietly:
- Explosions — pulled out of the blast list for both TNT and block explosions.
- Pistons — extend and retract are cancelled if they'd shift a registered beacon.
- No drops — a destroyed beacon leaves nothing behind, so it can't be picked up and hidden again.
Break one and the whole server hears about it.
? Final kills
| Beacon |
On death |
| Standing |
Normal respawn at your team's start point. Inventory wiped — unless Respawn With Kit is on. |
| Destroyed |
Final kill. Nothing drops, and you respawn locked in spectator mode exactly where you fell, free to watch the rest of the match. |
Logging out is not an elimination. Nobody hands their team the match by rage-quitting.
? Compass tracking
Right-click any vanilla compass to cycle through enemy beacons — no custom item to hand out,
nothing to craft. It only targets enemy teams whose beacon is placed and still standing, reports
on the action bar (Tracking - Team Cyan - 142, 68, -391), and does absolutely nothing before the
hunting phase, so nobody can watch you hide.
? Live scoreboard
A flicker-free sidebar with the phase, the countdown or elapsed time, and every team's live status —
Alive, Not Placed, No Respawns (beacon gone but still fighting) and Eliminated. Updates once
a second and immediately on any state change. Everyone shares one scoreboard, which is what colours
names, nametags and the tab list per team.
⚙️ In-game admin GUI
/hoh gui opens a settings panel — toggles for PVP, autosmelt, beacon-only crafting, team chat,
global freeze and respawn-with-kit, plus anvil-input fields for grace period length, pre-grace PVP
length and team size. Type a bad value and it reopens the anvil instead of silently dropping it;
escape out and nothing changes. No config reloads, no server restarts.
? Autosmelt
Optional. Ore drops and mob food arrive already smelted — raw iron/gold/copper, ancient debris,
every meat and fish, potatoes. Conversion happens at the source, so a block can never drop both
forms, and vanilla drops are asked for first: Fortune still counts and Silk Touch still works.
? Freeze
Three stacking scopes — global, per-team, per-player. A frozen player can't move, can't deal damage
and can't take damage, but keeps head rotation so they aren't stuck staring at a wall.
OP is always exempt, at every scope.
? Beacon-only crafting
Optional hardcore twist: real crafting tables stop working entirely, and the only 3×3 grid in the
game is the one you open by right-clicking your own placed team beacon. Want to craft? Go home.
⚔️ Pre-grace PVP rush
Optional opening phase where teams are scattered with kits and PVP already live, before anyone is
safe — so contesting the middle for gear actually costs something. Two rules keep it from deciding
the match on its own: beacons don't exist yet (nothing to loot), and rush deaths are never final.
Commands
Everything lives under /hoh (alias /hideorhunt). Run /hoh or /hoh help to list every
subcommand you have permission for — subcommands, team numbers and player names all tab-complete.
| Command |
Effect |
/hoh team create |
Create the next numbered team, auto-assigned the next colour. |
/hoh team invite <player> <team> |
Drop a player straight onto a team. |
/hoh team list |
Every team, its colour, status and roster. |
/hoh team clear |
Wipe all teams. |
/hoh setKit |
Snapshot your whole inventory — hotbar, main, armour, offhand — as the starter kit. |
/hoh setSpawn <team> [clear] |
Pin a team's start point where you stand, or clear it to scatter them instead. |
/hoh setRegion <radius> |
Set the scatter region, centred on you (1–100000). |
/hoh gui |
Open the admin settings panel. |
/hoh start |
Begin the match. |
/hoh stop (alias /hoh end) |
Abort and reset to Waiting. |
/hoh freeze global|team <n>|player <name> |
Freeze, at any scope. /hoh unfreeze for the inverse. |
/hoh tc <message> (alias /hoh teamchat) |
Team-only chat. |
/hoh start validates everything up front and tells you exactly what's wrong — fewer than two
teams with players, fewer than two with online players, or a team that needs scattering with no
region set. When it refuses, nothing has changed.
Permissions
| Node |
Default |
Grants |
hideorhunt.admin |
op |
Every command except team chat. |
hideorhunt.play |
everyone |
/hoh tc. |
Quick start
/hoh team create # once per team
/hoh team invite Steve 1
/hoh team invite Alex 2
/hoh setKit # while holding the loadout you want
/hoh setRegion 1500 # scatter area, centred on you
/hoh setSpawn 1 # optional: pin a team to a fixed point
/hoh start
Installation
- Drop the jar into your server's
plugins/ folder.
- Start the server —
plugins/HideOrHunt/config.yml is generated for you.
- Give your admins
hideorhunt.admin (OPs already have it).
Team spawns, the starter kit and every setting persist across restarts. Team rosters are
per-session by design — rebuild them in seconds with /hoh team create and /hoh team invite.
Supports up to nine teams, each with its own colour (gray, red, green, cyan, white, purple,
yellow, light blue, blue). A tenth is rejected with a clear message rather than quietly giving two
teams the same colour.
Compatibility
|
|
| Platform |
Spigot 1.21.11 — Paper and its forks work too, but no Paper-only APIs are used |
| Java |
21 |
| Dependencies |
None |
Built against the current API with zero deprecation warnings — no legacy openWorkbench, no
fromLegacyText, and the anvil input uses a genuine AnvilView so it behaves exactly like a real
anvil.
Inspired by the Hide or Hunt gamemode.
评论 0
登录后参与评分
还没有评论,来抢沙发吧