Originally Posted by SDPhantom
For anyone interested, I ran a few tests using an infinite loop to measure the time we have before this error comes up. The error does not trigger at all when out of combat as indicated by all tests completely freezing the game in this case. However, when in combat, we have about 200ms to do everything we need to do and return execution back to the game engine before this error triggers.
|
Is it limited for one function? Lets say if you break things down to multiple functions maybe you could dodge this bullet?