Self-cast buff: its visual stays on screen

Aperta
#3,609 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
25/100
Tipo di issue
Bug
Chiarezza
Da chiarire
Stato di attività
Attiva
Ambito
game-dev

Direzione di ricerca

Start from the replay and diagnostics attached to the in-game report to identify which visual persists (buff character effect, cast effect, or a HUD buff icon/bar). Then trace where buff effect lifetimes are created and expired in the Go server and the WebGPU client, and compare against the earlier report of a cast VFX surviving a resurrection to see whether the expiry event (cast end, buff expiry, or removal packet) is missed. Done means the visual ends when the native client ends it, with cited native evidence and a test covering that lifetime; expect reverse-engineering work before any code edit is obvious.

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

Descrizione

area: client bug priority: medium

Player report from Discord (2026-11-14, skills/effects): after casting a buff on themselves, the buff's visual stays on screen ("it stays on the screen like this"; the in-game report carries a replay and diagnostics).

To find out

  • What stays: the buff's character effect, its cast effect, or a HUD element (buff icon or bar), from the report's replay.
  • When it should end natively: on the cast's end, the buff's expiry, or its removal packet. Then whether our effect lifetime follows that event or misses it (compare the earlier report of a cast VFX that stayed after a resurrection).

Done when: the buff's visuals end when the native client ends them, with the native evidence cited and a test of that lifetime.

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.