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

Open
#3,508 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go, typescript

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
Go
Stars
97
Forks
61
Avg merge
4h 14m
Merged PRs (30d)
913

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from opensro-dev/opensro

All issues in opensro-dev/opensro

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.