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

Nameplate Style Filters Threat transitioning #1326

Open
3 of 4 tasks
Trenchfoote opened this issue Aug 26, 2024 · 0 comments
Open
3 of 4 tasks

Nameplate Style Filters Threat transitioning #1326

Trenchfoote opened this issue Aug 26, 2024 · 0 comments

Comments

@Trenchfoote
Copy link

Troubleshooting Steps

Wow_56KYaC5rNu.mp4

Describe the expected behavior and what actually happened?

I set a style filter that will change the color of the health depending on whether the trigger has been met. In this case, at 5 stacks of Razerice (51714) (DK debuff), the health will change to a blue color. I would expect the Nameplate to go from "good" threat color to the trigger color (when the trigger conditions are met), then back to the "good" threat (after the stacks are consumed and the trigger is no longer met. Instead I'm seeing coloring go "good" > "trigger" > "bad" > "good".

With this particular playstyle, you'd stack the debuff, consume the debuff, then restack. Consuming the debuff is a damage increase. So, you're applying > stacking > consuming > stacking >consuming > etc.

Reproducing the issue.

  1. Use a DK and build the style filter, or use any class that you could have a trigger change the color and change.
  2. Be spec that would clearly indicate good vs. bad threat. (Likely would need a tank friend to assist)
  3. Apply the debuff then consume (see video of the issue, please pardon the lack of estatus)

Lua Errors

No Lua Errors populating with this "issue".

Verification Steps

  • I have read the Changelog and verified ElvUI is up to date by checking /estatus
  • I have verified my issue doesn't exist in the Default UI or the Issue Tracker.
  • I have not read any of these steps, please close my issue when you see it.
  • I have done the Troubleshooting Steps and included the requested screenshots, which show the issue and status panel.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant