Wake
查看 AI Usage
Wake
一个轻量级且高度可配置的 Minecraft 赛船框架
功能模块
Wake 是一个拥有独立模块的框架,你可以按需关闭某些模块
Core Module
- 添加管理和实用命令
- 唯一不可关闭的模块
- 请参阅 文档
OBU Module
- 通过 OpenBoatUtils 客户端添加用于配置船只物理属性的命令
- 添加自定义命令界面以及 OBU 原生未提供的功能
- 保存/加载预配置的船只模式(上下文)
- 不可变的上下文,你可以对其进行分层并添加临时覆盖
- 实体上下文(每艘船的设置)通过命令使用更方便,并与其他玩家同步
- 沙盒提供隔离环境来构建上下文,而不是使用松散的命令方块链
- 显示已应用的设置/上下文/覆盖的仪表盘,涵盖船只和玩家
- 列出 OBU 设置的默认值
- 清除上下文中的特定设置,而不是重置或写入默认值
- 在重新登录时保留上下文,并修复碰撞时的船只卡顿问题(可配置)
- 等等。
- 支持 OBU
0.5.0+
- 请参阅 文档
Drydock Module
- 为 Drydock 赛船服务器添加内容
- 请参阅 文档
Axiom Module
- 允许管理员在 Axiom 的创建物品显示菜单中注册命名空间物品模型
- 请参阅 文档
展示
OBU 上下文分层
OBU 设置和上下文的仪表盘状态
共享服务器上下文和你自己的沙盒
沙盒
两个示例工作流: 创建、分叉、切换并发布沙盒。添加、缩小范围或移除单个设置,而不是重置所有内容。
查找和分享沙盒
更多自定义 OBU 功能
OBU 模块的服务端设置
自动补全和用于查找 OBU 默认值的命令
所有命令均在自定义帮助菜单中列出并解释
更多
OBU 客户端处理: 过时的客户端会收到通知,并在不可用的设置上显示徽章。不支持的客户端将被拒绝。
加速垫和耐久度: 如果出现数据库中断,Wake 会对每次更改进行排队,并在恢复时重放这些更改。
重载仪表盘中的当前模块
文档
AI 使用
代码库的大部分是由大型语言模型(LLM)编写或在其帮助下完成的。它们被用于代码生成、审查、训练和单元测试。
虽然我大量使用它们来生成样板代码,但架构/实现决策、创意构思以及代码审查完全由我负责。对于每次发布,我都会在迭代审查和自动化测试之后, dedicated 数天进行手动测试。参见 PR #10:为了 2.0.0 版本的发布,我花费了整整 12 天时间审查代码、修复发现的问题,并在自动化测试之上运行了约 350 个手动测试用例。
我知道使用 LLM 对某些人来说可能是不可接受的。但我可以保证 Wake 经过了妥善的测试,并且我清楚使用 LLM 所带来的责任。我开发和分享 Wake 是一个出于热爱的项目,旨在让像我这样的小型私人服务器也能从中受益。不属于关键基础设施。
开发者与管理员
Wake 主要在 Paper 1.21.11 上进行开发和测试。
它会在 Wake 声明支持的所有版本上进行编译。虽然也会在最低和最高支持版本上进行不定期测试,但大部分自动化和手动测试将在 OBU 支持的最新版 Minecraft 上进行。
数据库
默认情况下,Wake 使用 SQLite 数据库。
你可以设置一个 MariaDB 数据库,并通过 配置文件 指向它。Wake 会在数据库中断后自动恢复,并为你处理游戏内通知和缓存重载。
Wake 会将与 gameplay 相关的数据缓存在内存中以实现即时访问。因此,在多服务器设置中,各个服务器的缓存可能会与共享的 MariaDB 数据库产生偏差。请设置一个 Valkey 实例,并通过 配置文件 指向它。后端通过 pub/sub 向彼此的缓存广播更改,而 Wake 会处理失效/重载逻辑,以便如果你选择使用该功能,你的后端能保持同步。
你应该知道的事项
请确保在你的 spigot.yml 中增加 moved-wrongly-threshold 和 moved-too-quickly-multiplier 的值。
⚠ 警告
Wake 的 OBU 模块会取消 OBU 客户端在船中的车辆修正数据包(VEHICLE_MOVE),以避免在进行空中踏步(airstepping)或高速移动时出现“橡皮筋”效应(rubber banding)。或者任何未被上述配置处理且触发原版移动检查的情况。
请确保你使用专用的反作弊插件来处理此情况,或通过 /wakeobu -settings boat-lag-fix false 将其关闭。
私人服务器可以忽略此警告。
1.21-1.21.3 版本会记录关于 EntityRemoveEvent 的警告,你可以忽略它(或在 bukkit.yml 中将 deprecated-verbose 设置为 false 以抑制该警告)。
鸣谢
Wake
See AI Usage
Wake
A lightweight and highly configurable framework for Minecraft boatracing
- Supports: Paper
1.21.x, 26.x
Feature Modules
Wake is a framework with isolated modules that can be toggled off
Core Module
- Adds administration and utility commands
- The only module that cannot be toggled off
- see the docs
OBU Module
- Adds commands to configure boat physics via an OpenBoatUtils client
- Adds a custom command interface and features that OBU doesn't provide natively
- Saving/loading preconfigured boat modes (contexts)
- Immutable contexts you can layer and add temporary overrides to
- Entity contexts (per boat settings) are easier to use via commands and sync to other players
- Sandboxes that provide isolated environments to build contexts instead of using loose command block chains
- A dashboard showing applied settings/contexts/overrides of boats and players
- Listing default values for OBU settings
- Clearing specific settings in your context rather than resetting or writing the default value
- Keeping contexts across relogs and fixing boat lag on collisions (configurable)
- etc.
- Supports OBU
0.5.0+
- see the docs
Drydock Module
- Adds content for the Drydock boatracing server
- see the docs
Axiom Module
- Lets admins register namespaced item models in the create item display menu of Axiom
- see the docs
Showcase
OBU context layering
The status dashboard for OBU settings and contexts
Shared server contexts and your own sandboxes
Sandboxes
Two sample workflows: Create, fork, switch and publish a sandbox. Add, narrow or remove single settings instead of resetting everything.
Look up and share sandboxes
More custom OBU features
Server-side settings for the OBU module
Autocompletion and a command to look up OBU defaults
All commands are listed and explained in custom help menus
More
OBU Client handling: Outdated clients are notified and see badges on unavailable settings. Unsupported ones are refused.
Boostpads and durability: Wake queues every change in case of database outages and replays them on recovery.
Current modules in the reload dashboard
Documentation
AI Usage
Large parts of the codebase are written by or with the help of LLMs. They were used for code generation, reviews, drills and unit tests.
While I use them heavily to generate boilerplate, the architectural/implementation decisions, ideas and code reviews are entirely my responsibility. For releases, I dedicate days to manual testing following iterative reviews and automated tests. See PR #10: I spent 12 full days to review code, fix findings and run ~350 manual testcases on top of the automated ones for the 2.0.0 release.
I'm aware that using LLMs is a dealbreaker for some. But I can ensure you that Wake is properly tested and that I'm aware of my responsibilities using LLMs. I'm developing and sharing Wake as a passion project that smaller private servers like mine might benefit from as well. Not critical infrastructure.
Developer & Admins
Wake is primarily developed and tested on Paper 1.21.11.
It is compiled on all versions Wake claims to support. It is also sporadically tested on the lowest and highest supported versions but the majority of automated and manual testing will happen on the latest Minecraft version OBU supports.
Database
By default Wake uses a SQLite database.
You can set up a MariaDB database and point Wake to it via the config. Wake automatically recovers after database outages and handles ingame notifications and cache reloading for you.
Wake caches gameplay related data in memory for instant access. Therefore the caches of individual servers can drift from the shared MariaDB database in a multi-server setup. Set up a Valkey instance and point Wake to it via the config. Backends announce changes to their cache via pub/sub and Wake handles the invalidation/reloads so your backends stay synced if you choose to use that feature.
Things you should know
Make sure to increase moved-wrongly-threshold and moved-too-quickly-multiplier in your spigot.yml
⚠ Warning
Wake's OBU module cancels vehicle correction packets (VEHICLE_MOVE) for OBU clients in boats to avoid rubber banding when airstepping or at speed. Or anything that trips vanilla movement checks that isn't handled by the configs above.
Make sure you account for that with a dedicated anti-cheat plugin or toggle it off via /wakeobu -settings boat-lag-fix false.
Private servers can ignore this warning.
1.21-1.21.3 will log a warning about EntityRemoveEvent which you can ignore (or suppress via deprecated-verbose: false in bukkit.yml)
Credits
评论 0
登录后参与评分
还没有评论,来抢沙发吧