Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 [Bug] Detect Magic not stacking #1620

Closed
Daribon opened this issue Sep 10, 2022 · 0 comments · Fixed by #2609
Closed

🐛 [Bug] Detect Magic not stacking #1620

Daribon opened this issue Sep 10, 2022 · 0 comments · Fixed by #2609
Labels
bug Something isn't working

Comments

@Daribon
Copy link
Contributor

Daribon commented Sep 10, 2022

🐛 Bug report

If 2 mages both cast Detect Magic (spellID 2855) on the same target, then only 1 Detect Magic will appear on the target.
The most recently applied one replaces the first.

Expected behavior

It should be possible to apply multiple Detect Magic on a target. One for every mage.

https://youtu.be/9IMfIkC0dxg?t=40
Video from vanilla with Shazzrah having 3 Detect Magic debuffs on him

https://youtu.be/xchHtS9AG38?t=3m3s
Video from vanilla with Shazzrah having 2 Detect Magic debuffs on him

https://youtu.be/HWx1o7ECjI8?t=18m38s
Video from vanilla with a Rogue having 2 Detect Magic debuffs on him

Image from classic with two mages applying detect magic on a mob:
WowClassicT_kigMHTqEUw

Steps to reproduce

  1. Login to two wow clients
  2. .learn 2855 on both clients
  3. Target any enemy mob
  4. Cast Detect Magic on both mages
  5. Only one Detect Magic will be applied.

Version & Environment

Client Version: 1.12.1.5875

Commit Hash: 373fde4

OS Client: Microsoft Windows 11 Pro N 10.0.22000 Build 22000
OS Server: Microsoft Windows 11 Pro N 10.0.22000 Build 22000

Crashlog

  • None
@Daribon Daribon added the bug Something isn't working label Sep 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant