[BUG] Module Conflict with Automated Animations

[Brimcon]

Module Version: Conditional Visibilty: v0.5.6 Automated Animations version 2.5.6

Describe the bug With Automated Animations enabled Conditional Visibility prints an error and becomes non-functional.

module.js:44 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'API')
[Detected 1 package: conditional-visibility]
    at setupHooks (module.js:44:34)
    at conditional-visibility.js:41:5
    at Function._call (foundry.js:294:14)
    at Function.callAll (foundry.js:253:12)
    at Game.setupGame (foundry.js:5528:11)
    at Game._initializeGameView (foundry.js:6510:16)
    at Game._initializeView (foundry.js:6486:21)
    at Game.initialize (foundry.js:5433:16)

To Reproduce Steps to reproduce the behavior: Enable both Conditional Visibility and Automated Animations alongside their dependancies Refresh page. Observe Console Error.

Expected behavior No Console Error and functional Conditional Visibility.

Browser: Chrome

Foundry Version: Version 9.255

Game System: DnD5e 1.5.7

Additional context CVTest-1648142888547.log

[p4535992]

Can't replicate this issue, but other peolple show the same error in different use case, try out 0.5.7 and tell me if the error still show up.

[Brimcon]

Still occurs on my end. I am also running on a dedicated remote server, Lemme see if it happens on local server.

[Brimcon]

Confirmed it happens on my local server. I have an actor on a fresh scene (Human Fighter from Starter Heroes in DnD5e) After having that actor on the field and hitting refresh prints the error.

With the actor removed from the scene the error does not occur on Local, still occurs on Remote.

[Brimcon]

Update on Local server: Refreshing multiple times occasionally brings up the error. Its 100% Consistant on remote, but occurs every 6 or 7 refreshes on Local/Electron

[Brimcon]

Fixed!