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

Aperta
#3,508 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Go
Stelle
97
Fork
61
Merge medio
4h 14m
PR unite (30g)
913

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di opensro-dev/opensro

Tutte le issue di opensro-dev/opensro

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.