Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

API script error

1585060990

Edited 1585061039
Hi there folks, I'm currently running into an issue where I'm getting an error on my API output console that seems to break a script I've been using fine for many months now - HealthColors being the script in question. The error I'm seeing is this: These are the scripts I've been using. I disabled some that I haven't been using much in the hopes that it would solve the problem. The main offender is the 'HealthColors' script . It seems to right itself for twenty minutes or so after I've disabled another script and then the same error crops up again. I've next to no skill in debugging/solving these problems myself so any help would be appreciated! Happy to provide more info if the above isn't clear enough. Thanks in advance!
1585062296
The Aaron
Roll20 Production Team
API Scripter
That's super strange. I wouldn't think HealthColors has any path code in it. 
1585064113

Edited 1585064323
DXWarlock
Sheet Author
API Scripter
I don't think it could be HealthColors. I'm not doing any path/child calls in it. And none of the offenders in the red text error message is any names I used for my functions. What is being done when the API crashes? HealthColors on has 3 event handlers it looks for to trigger it: The !aura command, a token out on the playfield having its health bar changed, or a new token being made on the desktop to add the aura to. Is it crashing during one of those?
Thanks for the replies. It may not be HealthColors thats causing the problem - I'm really not savvy with this stuff - but I do notice that HealthColors has stopped functioning correctly. I wasn't able to find anything repeatable regarding what causes the script to stop working sadly!