You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BigWigs autologging breaks logs in M+ keys as it stops logging on ENCOUNTER_END which gets fired multiple times in a dungeon. Consider adopting the same approach MRT uses:
in Raid zones, keep the current behaviour
in Mythic 0 zones, start logging and stop once you zone out. this may catch some Mythic 0 trash but WCL separates these based on CHALLENGE_MODE_START/_END anyways
What steps will reproduce the problem?
Enable autologging in settings
Start a key
Upload the log after the key or use live logging
Observe how either:
the log records up until the end of the first boss of the dungeon and nothing after
the log records up until the end of the first boss of the dungeon and only bosses onwards
the log records exclusively bosses
What version of BigWigs are you using? (Stating 'latest' is not useful)
Latest, but this is a long outstanding issue for at least 6 months.
Do you have an error log of what happened?
No error thrown.
Any additional information? (example: WoW language if not English)
Suggestion: do not stop logging if CHALLENGE_MODE_START was observed, until CHALLENGE_MODE_END is seen OR another CHALLENGE_MODE_START (due to abandoning a key)
The text was updated successfully, but these errors were encountered:
Describe the problem
BigWigs autologging breaks logs in M+ keys as it stops logging on ENCOUNTER_END which gets fired multiple times in a dungeon. Consider adopting the same approach MRT uses:
What steps will reproduce the problem?
What version of BigWigs are you using? (Stating 'latest' is not useful)
Latest, but this is a long outstanding issue for at least 6 months.
Do you have an error log of what happened?
No error thrown.
Any additional information? (example: WoW language if not English)
Suggestion: do not stop logging if CHALLENGE_MODE_START was observed, until CHALLENGE_MODE_END is seen OR another CHALLENGE_MODE_START (due to abandoning a key)
The text was updated successfully, but these errors were encountered: