Self-cast buff: its visual stays on screen

Abierto
#3,609 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
game-dev

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Go
Estrellas
97
Forks
61
Merge medio
4 h 14 min
PR fusionados (30 d)
913

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de opensro-dev/opensro

Todos los issues de opensro-dev/opensro

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.