Hm, so this issue hasn’t been widely reported and we’ve been unsuccessful in reproducing it so far.
If you could capture a video the next time you encounter this, and provide your console log from the session it happens that would be very useful for us to see.
After combing through the code and some testing we’ve still been unsuccessful in reproducing this bug
That said, we’ll be implementing some prints in our console logs with the Necromancer release that should hopefully help us track this down.
Post-Necromancer update, when anyone runs into this issue if you can please provide your console logs from the culprit sessions it would be much appreciated!
This thread will likely auto-lock again by then, but feel free to DM me directly, or post up a new thread at the time thanks!