[Bug]: Countdown timer freezes if enemy is engaged or if player moves before timer reaches zero

[sicmunkychamber]

What are you trying to do?

Moving or engaging an enemy while the countdown timer is active causes the timer to freeze and remain on the screen. Restarting another timer and letting it reach zero without moving or engaging an enemy will allow the timer to remove itself from the screen.

What is the expected behaviour?

Timer should continue to count down until it reaches zero and then disappear.

What actually happened?

The timer freezes and remains on the screen indefinitely unless another timer is started and allowed to complete fully.

Suggested solution

Timer should continue to count down until it reaches zero and then disappear

Logs

[5/24/2023 8:32:08 PM] Info: ZeffUI: BrowserConsole: Uncaught TypeError: Cannot read properties of undefined (reading 'type') (Source: https://zeffuro.github.io/ZeffUI/scripts/index.js, Line: 2703)
[5/24/2023 8:32:08 PM] Info: ZeffUI: BrowserConsole: Uncaught TypeError: Cannot read properties of undefined (reading 'type') (Source: https://zeffuro.github.io/ZeffUI/scripts/index.js, Line: 2703)
[5/24/2023 8:32:08 PM] Info: ZeffUI: BrowserConsole: Uncaught TypeError: Cannot read properties of undefined (reading 'type') (Source: https://zeffuro.github.io/ZeffUI/scripts/index.js, Line: 2703)
[5/24/2023 8:32:08 PM] Info: ZeffUI: BrowserConsole: Uncaught TypeError: Cannot read properties of undefined (reading 'type') (Source: https://zeffuro.github.io/ZeffUI/scripts/index.js, Line: 2703)
[5/24/2023 8:32:08 PM] Info: ZeffUI: BrowserConsole: Uncaught TypeError: Cannot read properties of undefined (reading 'type') (Source: https://zeffuro.github.io/ZeffUI/scripts/index.js, Line: 2703)
[5/24/2023 8:32:08 PM] Info: ZeffUI: BrowserConsole: Uncaught TypeError: Cannot read properties of undefined (reading 'type') (Source: https://zeffuro.github.io/ZeffUI/scripts/index.js, Line: 2703)

FFXIV Update

• [X] I have confirmed that I have the latest version of Ravahn's FFXIV_ACT_Plugin, ngld's OverlayPlugin and cactbot (for the memory reading) are up to date.

[sicmunkychamber]

There was an update to one of the ACT components that seems to have resolved this issue.