- Getting a "heartbeat timeout" or "script closed due to error" message when you come back to a game that was previously working fine (e.g. you played it on Thursday, it was fine, you come back Monday and you have to hit Save Scripts to get it to work again due to one of those errors). Note that you still may get the "heartbeat timeout" error today since we just fixed it, but you shouldn't see that happen again going forward.
- Getting a "script closed due to error" message without further explanation -- hopefully now you should get one of "heartbeat timeout", "too much CPU", or "too much memory" instead.
- Issues with previous sandbox instances not closing properly, leading to "double execution" of API scripts (e.g. you would run a PowerCards command and get the result back twice instead of once).
- Although not solely an API issue, we also fixed a bug yesterday that was causing some dice rolls not to work (including inside of API commands) on the Dev Server when 3D Dice were enabled, so that may have caused you to think your API scripts weren't running when in fact they were, and it was the dice engine that was having issues.
If you are still experiencing any of these after today, please post in this thread and let us know so that we can investigate further. Thanks!
Note that we had to reset the API server to roll out these changes, so you may have to go hit the "Save Scripts" button for your Campaign to get your API scripts to function again, so be sure to check that if you notice your scripts aren't responding.
