TrinityCore / TrinityCore/TrinityCore

Core/Spells: AURA_INTERRUPT_FLAG_MELEE_ATTACK (Attacking) 0x00001000

Open
#27,200 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Branch-3.3.5a Comp-Core Sub-Spells
Dominant language
C++
Stars
10.8k
Forks
6.4k
Avg merge
3d 16m
Merged PRs (30d)
6

Description

Description

AURA_INTERRUPT_FLAG_MELEE_ATTACK (Attacking) 0x00001000 should be responsible for any type of damage, not only for melee, I guess

Looks a bit weird
https://user-images.githubusercontent.com/24683355/139015418-255c9690-8a80-4298-b5d4-98e7de03ec75.mp4

Maybe it's fixed in master, didn't checked

Expected behaviour

above

Steps to reproduce the problem

.go c id 12856
change your level to 25
aggro creature from range, don't damage it

Branch

3.3.5

TC rev. hash/commit

222164a

Operating system

Win 8.1

Custom changes

none

Contributor guide

Open the contributing guide

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.

Research direction

Start in the 3.3.5 branch by tracing where AURA_INTERRUPT_FLAG_MELEE_ATTACK (0x00001000) is handled, then reproduce the case with creature 12856 using the listed .go c id and level commands. Compare the behavior with master, since the report is unsure whether it is already fixed. Done means the intended interruption behavior is confirmed and verified against the ranged-aggro reproduction.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.