Details! Damage Meter

Details! Damage Meter

243M Downloads

One Segment Battleground setting not respected in Battlegrounds

hazzal opened this issue ยท 3 comments

commented

Before Start!

Make sure the bug also happen when Details! is the only addon enabled.

Game and Details! version
Use /details to grab these two.
R8501 v9.0.5

Describe the bug

  • Steps to Reproduce (what did you do to make the bug happen):
    Enable One Segment Battleground option in settings. Enter a rated BG, enter combat multiple times and check your segments.
  • Result (what happens when you follow the steps above):
    You get multiple segments, one for for each fight inside the battleground.
  • Expected (what you think the expected behavior would be when following the steps):
    That you get one segment for one battleground when you have the setting enabled.
  • When the bug started (a date, wow path release, details update, etc)?
    Started happening with one the latest update, had a friend with the same problem too.
  • Additional information:
    I haven't tested this in Random BGs yet but I expect the same behavior happens there. Will update with a comment if I test in an unrated BG.

Lua Error
Post here lua errors, if you aren't getting any, use /console scriptErrors 1

Screenshots
Post images of the bug if necessary.

Combat Log
Include a link to a combatlog file if the error is about not detecting a skill, usable item or item proc.
The log can be as simple as hitting a mob with white damage and using the item/skill.

Other Information
If necessary, add more info here.

commented

Just tested this in a random BG and I get same result as in rated BGs. According to a friend the issue doesn't appear to happen in R8406.

commented

I'm also seeing this issue. Been happening for the past day or so.

[00:33:58] Details!: DETAILS! VERSION: R8501
[00:33:58] Details!: GAME VERSION: v9.0.5

I can also confirm that downgrading to this resolves the issue:

[01:11:06] Details!: DETAILS! VERSION: R8406
[01:11:06] Details!: GAME VERSION: v9.0.5
commented

Latest commit seems to have fixed this issue e8a0380