结构边界
一个命令会勾勒出你周围所有已生成的结构及其内部每一部分的轮廓,让你清楚村庄在哪里结束、矿道延伸到哪里,以及世界生成器究竟放置了哪些部分。
重要提示: 仅扫描已经加载的区块,且当你跨越区块边界时,轮廓会重新构建。尚未有人加载过的结构不会绘制,而在你静止不动时加载的结构,只有在你移动后才会出现。
功能
- 查看结构形状: 结构本体周围显示白色方框,起始部分周围显示绿色方框,其余每个部分周围显示蓝色方框——这些颜色与原版调试视图所使用的颜色一致
- 命名部分: 每个绘制的部分上方都会显示其名称,即使被掩埋的部分也能透过地形清晰读取
- 隔离单个结构: 保留你当前所在的结构,移除其他所有结构,并为保留的结构添加发光效果,使其从外部依然可见
- 仅你自己可见: 方框通过数据包实现而非方块或实体,因此不会生成任何实体,重启后也不会持久存在,其他玩家不会收到这些数据
- 可调细节级别: 每位玩家可自行设定每个结构最多绘制多少个部分,或者完全取消限制;超出限制的部分始终是最远的那些
- 可配置上限: 管理员可设置扫描半径,以及单个玩家最多能接收到的方框数量上限
- 设置持久化: 每个开关状态都保存在玩家数据中,重连后依然生效
要求
该插件需要 Paper 或其分支版本,并深入调用服务器内部机制。每个 JAR 文件均针对特定 Minecraft 版本编译,文件名中也注明了对应版本,请为服务器提供与之匹配的 JAR。表格之外的版本支持尽最大努力兼容,并在启动时记录日志。
| JAR |
Minecraft |
Java |
structure-bounds-1.21.11-<version>.jar |
1.21.11 |
21 或更高 |
structure-bounds-26.1.2-<version>.jar |
26.1.2 |
25 或更高 |
structure-bounds-26.2-<version>.jar |
26.2 |
25 或更高 |
安装方法
将上表中与你服务器 Minecraft 版本对应的 JAR 文件放入服务器的 plugins/ 目录,然后重启服务器。
命令
| 命令 |
描述 |
权限 |
/bounds |
在你周围绘制轮廓,或再次隐藏它们 |
structure-bounds.use |
/bounds all-pieces |
无论 max-pieces 限制如何,都绘制每一个部分,或再次应用它 |
structure-bounds.use |
| /bounds isolate | 仅保留你当前所在的区块结构,或清除已加载的结构 | structure-bounds.use |
| /bounds max-pieces <count> | 设置单个结构最多可生成的区块数量,上限为 maxBoxesPerPlayer | structure-bounds.use |
| /bounds show-labels | 在每个区块上方显示标签,或隐藏它们 | structure-bounds.use |
| /bounds show-labels names | 在每个区块 ID 下方添加友好名称,或移除它 | structure-bounds.use |
重绘指令每两秒最多执行一次,在冷却期间会拒绝执行并提示等待。隐藏轮廓则永远不会被拒绝。
配置
plugins/structure-bounds/config.yml。插件会在首次启动时写入该文件,并在之后的每次启动时重写它,每个键上方都会附带注释:插件不再读取的旧键会被移除,新键会以默认值出现,而你自己添加的注释将不会被保留。
| 键 |
描述 |
默认值 |
最小值 |
最大值 |
debug |
启用调试功能。详见 Debug Mode |
false |
|
|
scanRadiusChunks |
围绕玩家搜索结构的范围(以区块为单位) |
6 |
1 |
16 |
maxBoxesPerPlayer |
一次可向单个玩家发送的结构框数量上限 |
256 |
1 |
1024 |
pieceNames |
显示在结构 ID 下方的友好名称,见下文 |
|
|
|
超出范围的数值将被钳制回其默认值,并在控制台输出警告。如果类型错误(例如应为数字的地方填入了文本),则会导致插件无法启动,并在控制台中指出问题所在的文件名。
当玩家收到的结构框数量超过上限时,系统会保留距离最近的框,丢弃其余部分,并仅提示一次视图被截断。
保留 version 不变:它记录了文件的结构,以便插件能够对其进行升级。
区块名称
pieceNames 将组件(piece)的 ID 映射为其下方显示的名称。条目可以使用完整的 ID,也可以仅使用其最后的路径段,因此 corner_01 会为所有基于该模板建造的小镇街道转角命名。插件自带了一些旧结构的名称,这些结构的 ID 是缩写形式,例如用 shcc 表示地牢宝箱走廊。
pieceNames:
shcc: Stronghold Chest Corridor
corner_01: Street Corner
btp: ''
一旦在文件中设置了 pieceNames,它将完全替换掉插件自带的名称,因此如果你删除了某个名称,它就不会再显示了。将名称设置为 '' 可以显式隐藏它。移除整个部分即可恢复插件自带的名称。
从 0.2.0 版本升级
首次启动时会自动转换旧配置文件:scan-radius-chunks 和 max-boxes-per-player 的值会在新名称下保留;piece-names.yml 的内容会被迁移到 pieceNames 中,并且 piece-names.yml 文件将被删除。旧的 config.yml 会与新的配置文件一起保留为 config.yml.v1.bak。
权限
| 节点 |
授予权限 |
默认值 |
structure-bounds.use |
/bounds 及其子命令 |
所有人 |
调试模式
此处所有内容均受 debug 配置标志控制,该标志默认处于关闭状态。
每次扫描、重绘、会话丢弃以及被拒绝的命令都会记录到控制台,并标明玩家名称及涉及的数量。玩家所见内容不会发生任何变化。
Structure Bounds
One command outlines every generated structure around you, and every piece inside it, so you can see where a village
ends, where a mineshaft runs, and exactly which pieces the world generator placed.
IMPORTANT: Only chunks that are already loaded are scanned, and the outlines are rebuilt when you cross a chunk boundary. A
structure nobody has loaded is not drawn, and one that loads while you stand still appears once you move.
Features
- See the shape of a structure: a white box around the structure itself, a green one around its start piece and a
blue one around every other piece, the colours vanilla's own debug view uses
- Named pieces: each drawn piece carries its name above it, readable through terrain so a buried piece still reads
- Isolate one structure: keep the structure you are standing in, drop every other, and give the one you kept a glow
so it stays visible from outside
- Nobody else sees them: the boxes are packets rather than blocks or entities, so nothing is spawned, nothing
persists a restart and no other player is sent them
- Tunable detail: each player picks how many pieces a structure may draw, or lifts the limit entirely, and what a
limit drops is always the furthest away
- Configurable limits: operators set the scan radius and a cap on how many boxes a single player can be sent
- Settings persist: every toggle is stored on the player, so it survives a relog
Requirements
The plugin needs Paper, or a fork of it, and reaches into the server's own internals. Each JAR is built against one
Minecraft version and named for it, so give the server the JAR that matches. Anything outside this table is best-effort
and logged on startup.
| JAR |
Minecraft |
Java |
structure-bounds-1.21.11-<version>.jar |
1.21.11 |
21 or newer |
structure-bounds-26.1.2-<version>.jar |
26.1.2 |
25 or newer |
structure-bounds-26.2-<version>.jar |
26.2 |
25 or newer |
Installation
Drop the JAR for your server's Minecraft version, from the table above, into the server's plugins/ directory and
restart.
Commands
| Command |
Description |
Permission |
/bounds |
Draws the outlines around you, or hides them again |
structure-bounds.use |
/bounds all-pieces |
Draws every piece whatever the max-pieces limit, or applies it again |
structure-bounds.use |
/bounds isolate |
Keeps only the structure you are standing in, or clears the hold |
structure-bounds.use |
/bounds max-pieces <count> |
Sets how many pieces one structure may draw, up to maxBoxesPerPlayer |
structure-bounds.use |
/bounds show-labels |
Draws the label above each piece, or hides them |
structure-bounds.use |
/bounds show-labels names |
Adds the friendly name under each piece's ID, or removes it |
structure-bounds.use |
A command that redraws is limited to one every two seconds, and refuses with a message until the wait is out. Hiding the
outlines is never refused.
Configuration
plugins/structure-bounds/config.yml. The plugin writes it on first start and rewrites it on every start after that,
with a comment above each key: keys it no longer reads are removed, new ones appear with their defaults, and comments
you add yourself are not kept.
| Key |
Description |
Default |
Minimum |
Maximum |
debug |
Enables debug functionality. See Debug Mode |
false |
|
|
scanRadiusChunks |
How far around a player to look for structures, in chunks |
6 |
1 |
16 |
maxBoxesPerPlayer |
How many boxes one player may be sent at once |
256 |
1 |
1024 |
pieceNames |
Friendly names shown under piece IDs, see below |
|
|
|
Out-of-range values are clamped back to their default, with a warning in the console. A value of the wrong type, such
as text where a number belongs, stops the plugin from starting and names the file in the console.
A player who is sent the cap keeps the boxes nearest them, loses the rest, and is told once that the view was cut short.
Leave version alone: it records the shape of the file so the plugin can upgrade it.
Piece names
pieceNames maps a piece's ID to the friendly name shown under it. An entry can use the full ID or just its last path
segment, so corner_01 names every village street corner built from that template. The plugin ships names for the older
structures whose IDs are abbreviations, such as shcc for a stronghold chest corridor.
pieceNames:
shcc: Stronghold Chest Corridor
corner_01: Street Corner
btp: ''
Once pieceNames is in the file it replaces the shipped names entirely, so a name you delete is no longer shown. Set a
name to '' to hide it explicitly. Remove the whole section to get the shipped names back.
Upgrading from 0.2.0
The first start converts the old file on its own: scan-radius-chunks and max-boxes-per-player keep their values
under their new names, the contents of piece-names.yml move into pieceNames, and piece-names.yml is deleted. The
old config.yml is kept beside the new one as config.yml.v1.bak.
Permissions
| Node |
Grants |
Default |
structure-bounds.use |
/bounds and its subcommands |
Everyone |
Debug Mode
Everything here is gated behind the debug configuration flag, which is off by default.
Every scan, redraw, dropped session and refused command is logged to the console, naming the player and the counts
involved. Nothing a player sees changes.
评论 0
登录后参与评分
还没有评论,来抢沙发吧