Bug-report bundle: record buffs, speed frames and mount routing so a speed desync can be root-caused

オープン
#3,508 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
18/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go, typescript

調査の方向性

The bundle is produced by the diagnostics code that writes state.json, movement.json and the network journal; start there and find where movementDiagnostics and the 0x376F speed frames are recorded. The request asks for buff slots, speed-frame history with mount routing via mountedOn, mount state, and a session-long effect add/remove log for 0xB419 and 0xB072-family frames. Done when a bundle captured during a desync shows the last applied speed frame, its routing, and the held buffs next to the server's values. Expect to need protocol knowledge, and check #3506 first.

索引モデルが issue の本文から書いたものです。

説明

area: client enhancement priority: high

Problem

Bug report BR-261114-1716-2195 (the speed scroll rubber-bands: the icon is gone, the VFX stays, the character goes fast then slow) cannot be root-caused from its diagnostics bundle.

What the bundle shows:

  • state.json movementDiagnostics.recent[].after: the client ran at walk 40 / run 100 from 32 s into the session to the end, about 86 minutes.
  • movement.json receipts: the server timed paths at 50/s. Request 194 covered 131.9 units in 2638 ms.

What it does not show, and the root cause needs:

  1. Active effects on the client: the buff slots (skill id, token, state, remaining time) at capture.
  2. Speed history: every 0x376F the client applied, with its time, target gid, the entity it was applied to (player, or the mount it resolved through mountedOn), and the walk/run values.
  3. Mount state: the local player's mountedOn at capture and when it last changed.
  4. Effect add and remove history: 0xB419 / 0xB072-family frames with skill id and token, kept for the whole session rather than the 2-minute network window. The network journal covers only the last ~118 s, so a desync that started an hour earlier leaves no trace.

The server side of the same question is #3506 (the operator view now shows movementSpeeds and effects).

Done when

A report filed during a speed desync shows, from the bundle alone, the last speed frame the client applied, where it was routed, and which buffs the client held, compared with the server's speeds and effects.

主要言語
Go
スター
97
フォーク
61
平均マージ
4時間 14分
マージ済み PR(30日)
913

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

opensro-dev/opensro のほかの issue

opensro-dev/opensro の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。