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
This post has been closed. You can still view previous posts, but you can't post any new replies.

5e OGL Sheet API Failure

1530047197

Edited 1530047212
I have several scripts running using the 5e OGL sheet. An hour ago I fired up my game and noticed the API was failing to run. I receive the following error message.  "Starting webworker script..." "Error setting up custom sheet: TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object." Based on some previous threads, I unloaded the 5e OGL, changed it to None, saved it. The API ran perfectly in the game. I changed the sheets back to 5e OGL and I get the exact same error again. I also tried changing to 5e Shaped, which also loaded the API just fine. Switching back to 5e OGL caused the issue again.  Anyone know how I can fix this? Im not saying it is related, but this coincides with the push for charactermancer perhaps?
Hi Grant, I have submitted a ticket to the devs about this issue so they can take a closer look.
I am having the exact same issue. I'm thinking scripts need to update to support the new character sheets, but either way not a single one of my scripts is working anymore.
I was just just checking the forums because I am suddenly experiencing the exact same issue. 
1530054911

Edited 1530055015
Finds
API Scripter
Same, I've disabled all and tested one script at a time from the script library. It makes no difference still seeing the same error.
Having the exact same issue :(
1530059652
Stephen Koontz
Forum Champion
Marketplace Creator
Sheet Author
API Scripter
Compendium Curator
This issue should now be resolved. Please let us know if you're still experiencing API issues.
The issue has been resolved for me, thank you guys for your quick response!