ReducedDebugBackport
一个小型的 Spigot/Paper 1.16 插件,用于在使用 ViaVersion 连接至旧版服务器的情况下,从新版 Minecraft 客户端(1.21.x)的 visualize_entity_supporting_blocks 调试渲染器中隐藏隐形玩家。
⚠️ 重要提示: reducedDebugInfo 是全有或全无的设置。对于每个受影响的客户端,它还会隐藏 F3 坐标、碰撞箱(F3 + B) 和 区块边界(F3 + G) —— 而不仅仅是实体支撑方块渲染器。无法仅禁用该单一渲染器。请使用 min-protocol-version 和 reduceddebugbackport.bypass 权限来限制受影响范围。
问题所在
自 1.21.x 起,原版客户端在 UI 中暴露了其内部调试渲染器(F3 + F6 → 调试选项 → 调试渲染器)。其中一项名为 visualize_entity_supporting_blocks 的渲染器可设置为 始终启用,并在每个实体下方的方块上绘制标记 —— 包括被隐身效果隐藏的玩家。由于它使用客户端已有的数据进行渲染,服务器无法简单地“关闭此按钮”。
对抗此问题的原生手段是 reducedDebugInfo 标志(游戏规则 “限制调试屏幕内容”)。当激活时,客户端会禁用这些调试渲染器。该标志通过登录数据包发送给客户端,并通过针对玩家自身实体的 实体状态 / 实体事件 数据包(状态 22 = 启用,23 = 禁用)在运行时切换。
兼容性
适用于 1.16 及更高版本 的 Spigot/Paper 服务器。
reducedDebugInfo 游戏规则自 1.8 起就已存在,因此在你支持的任何服务器上,你可以直接运行:
/gamerule reducedDebugInfo true
即可实现相同的 全服生效 效果。仅当你需要 按玩家控制 时才使用此插件 —— 例如,仅对实际拥有 visualize_entity_supporting_blocks 渲染器的新版 ViaVersion 客户端隐藏 F3,同时保持原生玩家的 F3(坐标、碰撞箱)不受影响。reduceddebugbackport.bypass 权限提供了这种粒度控制;而单纯的游戏规则则不具备此功能。
要求
- 1.16 Spigot/Paper 服务器。
- ViaVersion(用于检测真实客户端协议版本)。
- PacketEvents 或 ProtocolLib(用于发送数据包)。
安装
- 将
ReducedDebugBackport-1.0.jar 放入与 ViaVersion 和 PacketEvents(或 ProtocolLib)同一目录下的 plugins/ 文件夹中。
- 启动服务器一次以生成
plugins/ReducedDebugBackport/config.yml。
- 如有需要调整
min-protocol-version,然后重启服务器。
配置
config.yml:
# 开始发送 reducedDebugInfo 的客户端协议版本起始值。
# 低于此值的客户端不受影响(保留 F3 坐标/碰撞箱)。
min-protocol-version: 774 # 774 = 1.21.11
# 将每次标志发送记录到控制台。
log-actions: false
# 详细日志:为 EACH 玩家打印检测到的协议版本以及决策结果(SKIP / SENT / BYPASS)。
debug: false
常见协议版本号:
| 协议号 |
版本 |
协议号 |
版本 |
| 754 |
1.16.5 |
767 |
1.21 / 1.21.1 |
| 763 |
1.20 / 1.20.1 |
768 |
1.21.2 / 1.21.3 |
| 764 |
1.20.2 |
769 |
1.21.4 |
| 765 |
1.20.3 / 1.20.4 |
770 |
1.21.5 |
| 766 |
1.20.5 / 1.20.6 |
772 |
1.21.7 / 1.21.8 |
| 773 |
1.21.9 |
774 |
1.21.11 |
命令
/rdb [off] —— 仅限操作员。诊断辅助工具:
- 打印检测到的协议版本、阈值、绕过状态以及“常规决策”(SEND / SKIP)。
- 强制发送数据包 忽略阈值:
/rdb 发送状态 22(启用),/rdb off 发送状态 23(禁用)。可用于确认数据包本身是否正常工作,无论版本检测结果如何。
权限
| 权限 |
默认值 |
效果 |
reduceddebugbackport.bypass |
false |
玩家被忽略 —— 不发送 reducedDebugInfo,保留完整 F3 显示。 |
绕过检查在应用时进行(加入游戏 / 重生 / 世界切换),因此对于在线玩家,更改其绕过权限后需等待下次重生或重新登录才会生效。
ReducedDebugBackport
A small Spigot/Paper 1.16 plugin that hides invisible players from the
visualize_entity_supporting_blocks debug renderer that newer Minecraft clients
(1.21.x) have, when they connect to a legacy server through ViaVersion.
⚠️ Important: reducedDebugInfo is all-or-nothing. For every affected client it
also hides F3 coordinates, hitboxes (F3 + B) and chunk borders (F3 + G) —
not just the entity-supporting-blocks renderer. There is no way to disable only that
one renderer. Limit who is affected with min-protocol-version and the
reduceddebugbackport.bypass permission.
The problem
Since 1.21.x the vanilla client exposes its internal debug renderers in a UI
(F3 + F6 → Debug Options → Debug Renderers). One of them,
visualize_entity_supporting_blocks, can be set to Always and draws a marker
on the block under every entity — including players hidden by invisibility.
It renders from data the client already has, so the server can't simply "turn the
button off".
The vanilla lever against it is the reducedDebugInfo flag
(gamerule "Limits contents of debug screen"). When active, the client disables
these debug renderers. The flag is delivered to the client in the login packet and
toggled at runtime via the Entity Status / Entity Event packet (status 22 =
enable, 23 = disable) targeting the player's own entity.
Compatibility
Works on Spigot/Paper servers 1.16 and newer.
The reducedDebugInfo game rule has existed since 1.8, so on any server this
plugin supports you can instead simply run:
/gamerule reducedDebugInfo true
for the same effect server-wide. Use this plugin only when you want
per-player control — e.g. hide F3 only for the newer ViaVersion clients that
actually have the visualize_entity_supporting_blocks renderer, while leaving
native players' F3 (coordinates, hitboxes) untouched. The
reduceddebugbackport.bypass permission gives you that granularity; the plain
game rule does not.
Requirements
- A 1.16 Spigot/Paper server.
- ViaVersion (used to detect the real client protocol version).
- PacketEvents or ProtocolLib (for sending the packet).
Installation
- Drop
ReducedDebugBackport-1.0.jar into plugins/ next to ViaVersion and
PacketEvents (or ProtocolLib).
- Start the server once to generate
plugins/ReducedDebugBackport/config.yml.
- Adjust
min-protocol-version if needed and restart.
Configuration
config.yml:
# Client protocol version FROM which to start sending reducedDebugInfo.
# Clients BELOW this value are left untouched (they keep F3 coordinates/hitboxes).
min-protocol-version: 774 # 774 = 1.21.11
# Log every flag send to the console.
log-actions: false
# Verbose log: for EACH player prints the detected protocol version and the
# decision (SKIP / SENT / BYPASS).
debug: false
Common protocol numbers:
| Protocol |
Version |
Protocol |
Version |
| 754 |
1.16.5 |
767 |
1.21 / 1.21.1 |
| 763 |
1.20 / 1.20.1 |
768 |
1.21.2 / 1.21.3 |
| 764 |
1.20.2 |
769 |
1.21.4 |
| 765 |
1.20.3 / 1.20.4 |
770 |
1.21.5 |
| 766 |
1.20.5 / 1.20.6 |
772 |
1.21.7 / 1.21.8 |
| 773 |
1.21.9 |
774 |
1.21.11 |
Command
/rdb [off] — operators only. Diagnostic helper:
- Prints the detected protocol version, the threshold, the bypass state and the
"normal decision" (SEND / SKIP).
- Force-sends the packet ignoring the threshold:
/rdb sends status 22
(enable), /rdb off sends status 23 (disable). Useful to confirm the packet
itself works regardless of version detection.
Permission
| Permission |
Default |
Effect |
reduceddebugbackport.bypass |
false |
Player is ignored — reducedDebugInfo is not sent, full F3 is kept. |
The bypass is checked at apply time (join / respawn / world change), so changing it
for an online player takes effect after their next respawn or relog.
评论 0
登录后参与评分
还没有评论,来抢沙发吧