We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Energy Feedback does not stack from different sources.
Energy Feedback should stack from different sources.
Wotlk Classic Heroic Starting from 3:06 , the paladin start killing Pure Energy and each kill will add stack on the same debuff.
TBC Classic Normal at 7:59 and 8:05 , the warrior kill 2 Pure Energy and each adds stack of Energy Feedback and refresh it.
TBC Classic Heroic at 13:21 , the warrior kill Pure Energy and he gets 2nd stack of Energy Feedback.
Killing Vexallus should remove Energy Feedback debuff on the players.
AzerothCore rev. 7725610 2025-01-21 10:44:39 +0100 (master branch) (Win64, RelWithDebInfo, Static)
Windows 11 x64
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Current Behaviour
Energy Feedback does not stack from different sources.
Expected Blizzlike Behaviour
Energy Feedback should stack from different sources.
Source
Wotlk Classic Heroic Starting from 3:06 , the paladin start killing Pure Energy and each kill will add stack on the same debuff.
TBC Classic Normal at 7:59 and 8:05 , the warrior kill 2 Pure Energy and each adds stack of Energy Feedback and refresh it.
TBC Classic Heroic at 13:21 , the warrior kill Pure Energy and he gets 2nd stack of Energy Feedback.
Steps to reproduce the problem
Extra Notes
Killing Vexallus should remove Energy Feedback debuff on the players.
AC rev. hash/commit
AzerothCore rev. 7725610 2025-01-21 10:44:39 +0100 (master branch) (Win64, RelWithDebInfo, Static)
Operating system
Windows 11 x64
Custom changes or Modules
No response
The text was updated successfully, but these errors were encountered: