Skip to content

Commit

Permalink
hide dynFrame if combat starts with living threads
Browse files Browse the repository at this point in the history
nothing that we put into dynFrame threads is meant for in-combat execution anyways, so to avoid random unexpectedly short timeouts, pause execution if combat starts, and resume after combat ends.

There's potential for WeakAuras to be 'broken' during that combat session (due to dynamic groups being Pause()'d), but we probably couldn't have unbroken it given that ResumeAllDynamicGroups is too costly to call during combat lockdown without risking a timeout.

Fixes WeakAuras#4967 (or at least, reduces its likelihood)
  • Loading branch information
emptyrivers committed May 15, 2024
1 parent f80977b commit 986fa11
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions WeakAuras/WeakAuras.lua
Original file line number Diff line number Diff line change
Expand Up @@ -1668,8 +1668,8 @@ local function scanForLoadsImpl(toCheck, event, arg1, ...)
local encounter_id = WeakAuras.CurrentEncounter and WeakAuras.CurrentEncounter.id or 0

if (event == "ENCOUNTER_START") then
encounter_id = tonumber(arg1)
CreateEncounterTable(encounter_id)
encounter_id = tonumber (arg1)
CreateEncounterTable (encounter_id)
elseif (event == "ENCOUNTER_END") then
encounter_id = 0
DestroyEncounterTable()
Expand Down

0 comments on commit 986fa11

Please sign in to comment.