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

Open
#3,564 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
22/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, typescript
Domain
game-dev

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

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.