Minecraft 服务器不会在每个刻(tick)向其他玩家发送其位置。原版游戏中,实体追踪器(entity tracker)以 updateInterval = 2 注册玩家,因此移动数据包最多每隔两个刻发送一次——即每秒 10 次。中间的所有数据都由客户端进行插值处理。
FastPlayerUpdates 将该间隔设置为 1。结果是每秒最多发送 20 次位置更新,而不是原来的 10 次。在 PvP、快速移动期间以及客户端插值延迟到达的场景中,这种变化最为明显。
实测数据来自一个统计传入位置数据包的客户端:
|
位置更新/秒 |
| Vanilla / Paper 未安装插件 |
8–10 |
| 使用 FastPlayerUpdates |
16–20 |
工作原理
该插件通过反射机制修改实体追踪器中的 ServerEntity.updateInterval。它不改变任何移动逻辑、位置数据或数据包内容——仅更改追踪器被允许发送数据的频率。
服务器自身的阈值过滤器保持完整:如果玩家没有移动(距离上次数据包小于 0.0028 格),则不会发送任何数据,与之前完全一致。不会产生冗余数据包——额外的流量仅在真实移动时发生。
带宽
每个可见且移动的玩家预计会产生多达两倍的移动数据包。单个移动数据包很小(约 10 字节),但在大量玩家同屏的服务器上会累积成显著的流量。对于大型网络:建议先用 update-interval: 1 测试,如有需要再回退到 2,或者将其限制用于竞技场场景。
include-non-player-entities(生物、物品、箭矢)默认关闭是有意为之——这才是真正消耗带宽的开关。
命令与权限
| 命令 |
效果 |
/fpu status |
显示配置信息以及从服务器读取到的实时间隔 |
/fpu reload |
重新读取 config.yml |
/fpu on / /fpu off |
运行时切换开启/关闭;off 恢复原始值 |
权限:fastplayerupdates.admin(默认:OP)。别名:/fastplayerupdates。
配置
enabled: true # 总开关
update-interval: 1 # 刻数;1 = 每刻,2 = 原版行为
include-non-player-entities: false # 同时加速生物/物品/箭矢的移动更新
reapply-interval-ticks: 200 # 安全网扫描间隔
兼容性
- Paper 1.21.11, 26.1.2, 26.2 — 一个 jar 包兼容这三个版本。
- 服务端插件,无需客户端模组。玩家无需安装任何东西。
- 无需 ProtocolLib,无其他依赖项。
- 已与 GrimAC 和 ViaVersion 一起测试。该插件仅更改出站实体数据包,不影响对入站移动数据的验证。
不兼容 Spigot/CraftBukkit 或 Folia。
诚实的测试状态
- 1.21.11 — 已在运行中的服务器上验证(上述数据即来源于此)。
- 26.1.2 / 26.2 — 静态验证:所有反射目标和服务端发送逻辑均已对照实际服务器 jar 包检查,确认完全一致。在这些版本上的实时测试仍在进行中。
- 26.2 在 Paper 官方仍处于 beta 阶段。
如果未来的 Paper 构建重命名了内部类,插件将在启动时禁用自身并输出清晰的日志消息,而不是静默失效。每次写入操作都会立即读回验证,若未生效则会报错。
Minecraft servers do not send other players' positions every tick. Vanilla registers
players in the entity tracker with updateInterval = 2, so a movement packet leaves at most
every second tick — 10 times per second. Everything in between is interpolated by your client.
FastPlayerUpdates sets that interval to 1. The result is up to 20 position updates per second
instead of 10. Most noticeable in PvP, during fast movement, and anywhere client-side
interpolation arrives too late.
Measured with a client that counts incoming position packets:
|
position updates/s |
| Vanilla / Paper without the plugin |
8–10 |
| with FastPlayerUpdates |
16–20 |
How it works
The plugin reflectively sets ServerEntity.updateInterval in the entity tracker. It changes
no movement logic, no positions and no packet contents — only how often the tracker is
allowed to send.
The server's own threshold filter stays fully intact: if a player has not moved (less than
0.0028 blocks since the last packet), nothing is sent, exactly as before. No redundant
packets are produced — extra traffic only occurs on actual movement.
Bandwidth
Expect up to twice the number of movement packets per visible, moving player. A movement
packet is small (~10 bytes), but it adds up on servers with many players in view. For large
networks: test with update-interval: 1, fall back to 2 if needed, or limit it to arenas.
include-non-player-entities (mobs, items, arrows) is off by default on purpose — that is
the switch that actually costs bandwidth.
Commands & permissions
| Command |
Effect |
/fpu status |
configuration and the live interval read back from the server |
/fpu reload |
re-read config.yml |
/fpu on / /fpu off |
toggle at runtime; off restores the original values |
Permission: fastplayerupdates.admin (default: OP). Alias: /fastplayerupdates.
Configuration
enabled: true # master switch
update-interval: 1 # ticks; 1 = every tick, 2 = vanilla
include-non-player-entities: false # also speed up mobs/items/arrows
reapply-interval-ticks: 200 # safety-net sweep
Compatibility
- Paper 1.21.11, 26.1.2, 26.2 — one jar for all three.
- Server-side, no client mod required. Players install nothing.
- No ProtocolLib, no other dependencies.
- Tested alongside GrimAC and ViaVersion. The plugin only changes outgoing entity packets,
not the validation of incoming movement.
Not compatible with Spigot/CraftBukkit or Folia.
Honest testing status
- 1.21.11 — verified on a running server (the numbers above).
- 26.1.2 / 26.2 — verified statically: every reflection target and the server's send logic
were checked against the real server jars and are identical. A live test on those versions
is still outstanding.
- 26.2 is still in beta at Paper itself.
If a future Paper build renames the internals, the plugin disables itself at startup with a
clear log message instead of silently doing nothing. Every write is read back and fails
loudly if it does not stick.
评论 0
登录后参与评分
还没有评论,来抢沙发吧