Flying dress stops flying after the Wizard teleport skill, and the weapon is held wrongly for a moment

Abierto
#3,564 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
22/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go, typescript
Área
game-dev

Línea de trabajo

The issue is a two-part bug where the flying dress and weapon pose are lost after a Wizard teleport skill arrives. Start with the two replays and the diagnostics movement journal the reports attach, to see which state the blink resets. Then find where the teleport arrival path re-applies the flight pose and the weapon attach, and check their order. Done means a regression test on the arrival path passes after repeated teleports.

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

Descripción

area: client bug priority: medium

Two player reports from Discord (2026-11-13), each with a replay and a diagnostics archive attached:

  • After the Wizard's teleportation skill, the angel-wing dress's wings sometimes stop working: the character no longer flies and walks with a bugged gait.
  • For a couple of seconds after the teleport, the character holds the weapon wrongly.

To find out

  • Which state the teleport skill (the Wizard blink) resets on arrival: the dress's flight pose, the movement mode, or the weapon attachment. Read the two replays and the diagnostics' movement journal first.
  • Whether native re-applies the flight pose after a teleport skill's arrival (client), and in what order against the weapon re-attach.

Done when: after any number of Wizard teleports while wearing a flying dress, the character keeps flying and holds the weapon correctly from the first frame, with a regression test on the arrival path.

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.