Bots4Velo v3.0.9

Bots4Velo v3.0.9

This release adds Minecraft 26.3 (protocol 777) support.

Changes

• Add a modern-26_3 transport adapter built on MCProtocolLib 26.3.
  protocol-version: "26.3" and AUTO detection of protocol 777 now select it.
• 26.3 replaced the serverbound swing packet with a hand-less punch packet
  and extended teleport acknowledgements with the resolved position. These
  packets now come from a per-version compatibility class, so the 1.21.11,
  26.1.2 and 26.2 adapters send exactly what they sent before.
• On 26.3 the bot follows every position packet (teleport acknowledgement or
  movement) with a client tick end. 26.3 servers kick clients that send two
  position packets in one client tick with "Invalid move player packet
  received".
• Relocate MCProtocolLib's NBT text serializer (org.geysermc.adventure)
  inside each modern adapter. It was previously unrelocated, so only one
  copy survived in the merged plugin JAR.

Requirements

Bots connect through the Velocity proxy itself, so 26.3 bots need a Velocity
build that supports 26.3. Velocity 3.x stops at 26.2 and rejects 26.3 clients
with outdated_client; Velocity 4.x supports 26.3 and requires Java 25.

Verification

CI covers 1.16.5, 1.21.11, 26.1.2, 26.2 and 26.3 protocol contracts and runs
the disposable network integration for each. 26.3 is tested against Paper
26.3 beta builds on Velocity 4.2.1-SNAPSHOT, because Paper has not published a
stable 26.3 build yet.

Bots4Velo v3.0.8

What's Changed

• fix: prevent rental AuthMe command race by @TypeThe0ry in #10

Full Changelog: v3.0.7...v3.0.8

Bots4Velo v3.0.7

Bots4Velo v3.0.7

This patch normalizes AuthMe authentication text from every modern Minecraft
chat channel supported by MCProtocolLib 26.2. AuthMe success and prompt text
can arrive as system chat, signed player chat, disguised chat, title,
subtitle, or action-bar text depending on server and chat decoration settings.

All variants now use the same plain-text matcher path, so a confirmed AuthMe
message can transition the bot to AUTHENTICATED and unblock the rental
server switch. Overlay system chat remains observable for authentication
matching; non-authentication behavior is unchanged.

Verification

./gradlew.bat clean test shadowJar verifyShadowJar writeArtifactChecksum '-PpluginVersion=3.0.7' --no-daemon --console=plain

Bots4Velo v3.0.6

What's Changed

• fix: recognize production AuthMe Chinese success messages by @TypeThe0ry in #8

Full Changelog: v3.0.5...v3.0.6

Bots4Velo v3.0.5

What's Changed

• fix: expose confirmed auth state to addons by @TypeThe0ry in #7

Full Changelog: v3.0.4...v3.0.5

Bots4Velo v3.0.4

Fix AuthMe session-restoration recognition and prevent AUTO login/register blind fallback. Rental server switches now receive explicit confirmed-auth lifecycle events.

v3.0.3 — AuthMe server-switch fix

Bots4Velo v3.0.3

修复 AuthMe 登录成功后，机器人已经位于目标服务器却不断请求切服、导致 Velocity 控制台刷屏的问题（#3，PR #4）。

• 切服前查询 Velocity 实际后端，已到目标则取消重试并继续登录后命令。
• 不再把其他后端的协议状态变化误判为到达目标；暂时查不到玩家时继续等待。
• 首次请求保留 INFO，重复请求降为 DEBUG，每 20 次未完成请求发出 WARN。
• 增加 11 项切服/日志回归测试，修正 Windows 换行符导致的工作流测试失败。

下载

• bots4velo-3.0.3.jar：Velocity 主插件。
• bots4velo-paper-3.0.3.jar：配套 Paper 插件；本修复不涉及 Paper 侧代码，现有兼容 companion 无需为此更新。
• 每个 JAR 均附 .sha256 校验文件。

更新与影响

备份旧 JAR 和插件数据目录，在维护窗口正常停止 Velocity 后替换主插件，确保 plugins 中只有一个 Bots4Velo 主插件 JAR，再启动代理。重启代理会断开所有经由该代理的玩家和机器人；无需重启宿主机或后端服。/vbot reload 不会加载新的 JAR 代码。

本版本从仓库公开 3.0.x 维护线发布。已观察到某部署使用源码来源尚未核对的 3.1.0；这类部署应先核对差异并移植修复，不能把 3.0.3 自动视为 3.1.0 的等价升级。

发布 GitHub Release 不会更新任何生产服务器。生产现场验收须在实际部署后进行。详细更新与回滚说明见 Issue #3 说明。

验证

• 干净构建 clean check shadowJar writeArtifactChecksum 成功，311 项测试全部通过。
• 四个内嵌协议适配器加载检查通过。
• 发布 PR #5 的 18 项 CI 检查全部通过，包含四版本真实网络集成。
• 发布源码：95f027b525fc0974c5019a501445996a84d76697。

v3.0.2

What's Changed

• Fix reconnect reliability and release 3.0.2 by @TypeThe0ry in #2

New Contributors

• @TypeThe0ry made their first contribution in #2

Full Changelog: v3.0.1...v3.0.2

v3.0.1

What's Changed

• feat: add isolated addon SPI by @CaesarGalahad in #1

New Contributors

• @CaesarGalahad made their first contribution in #1

Full Changelog: v3.0.0...v3.0.1

v3.0.0

Full Changelog: v2.9.0...v3.0.0