Speed desync: the client runs at 40/100 while the server times paths at 50 (scroll speed, rubber-banding)

未关闭
#3,540 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
12/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
go

调研方向

Start with the probe in worktrees/operator-speed, speeddesync_probe_test.go, which already rules out the scroll expiry, relog and mount cases. The remaining paths to test are death/revive, teleport re-entry, transform, pet tailwind, mounted speed changes and duplicate admission, and the 0x376F frame is the place to compare server and client speed. Done means a failing test that reproduces a server speed change without a matching frame, a fix, and that test passing.

由索引模型根据 Issue 内容生成。

描述

area: server bug priority: high

Player report BR-261114-1716-2195 (2026-11-14): with a speed scroll the character rubber-banded for about 86 minutes.

Proven from the report

  • The client ran at 40/100 (walk/run) from 32 s into the session; the server timed paths at 50/s (131.9 units in 2638 ms). The client's speed comes only from 0x376F, so a speed change reached the server's movement without a 0x376F to the client (or the reverse).

Ruled out by test (probe in worktrees/operator-speed, speeddesync_probe_test.go)

  • Tick expiry of the scroll, the scroll reused, another haste before/after the scroll, relog mid-scroll (re-entry sends 100), horse dismount order, client-side speed.
  • Icon/catalogue (skill 31107 exists with its icon); Premium Plus (no haste).

Still to test

  • Death/revive, teleport re-entry, transform, pet tailwind, a speed change while mounted (0x376F routed to the mount), a duplicate admission.

Related

  • #3506 (operator view shows live speeds and effects; next release) and #3508 (the bug-report bundle records buffs, speed frames and mount routing).

Done when

  • The path that changes server speed without a frame is found by a failing test, fixed, and the test passes.
主要语言
Go
星标
97
派生
61
平均合并
4 小时 14 分钟
30 天内合并 PR
913

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

opensro-dev/opensro 的其他 Issue

查看 opensro-dev/opensro 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。