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

Aberta
#3,564 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
22/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go, typescript
Domínio
game-dev

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Go
Estrelas
97
Forks
61
Merge médio
4h 14min
PRs com merge (30d)
913

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de opensro-dev/opensro

Todas as issues de opensro-dev/opensro

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.