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

[HELP] API Shutdown/TypeError when loading campaign

Hey, community, I have a question hopefully you guys can help me out with. Each time I load my campaign, the API fails to start and I get an error that says the following; Error setting up custom sheet: TypeError: Cannot read property 'split' of undefined I've disabled all of my scripts one by one - that didn't work. I made a copy of my campaign, with no scripts, but I still got the same error message. Only when I went in and changed the character sheet under Game Settings to "none" did the console not return with that error. However, when I try to set the character sheet to anything other than "custom" or "none", the error pops up again. Any ideas on how I might fix this issue? I'd be grateful for any help. Thanks.
1459888288

Edited 1459888402
Riley D.
Roll20 Team
What's the link to the game where this is happening? I just tried making a new game with a 5th Edition sheet, No Sheet, and a custom sheet and I didn't get that error message for them, so not sure what's going on...
Okay actually I figured it out. It was something to do specifically with the 3.5 Edition sheet. Should be fixed now (click on "Save Scripts" to reload your API sandbox). Thanks for letting us know!
1459889563
Diana P
Pro
Sheet Author
Riley, Is there an issue I need to fix with the D&D3.5e Sheet?  (so it gets propagated forward since I'm in the middle of updates for it.)
Fantastic! Thanks, Riley! I should add that it did that when I tested the Pathfinder sheet, as well. Might be worth checking out? 
1459924742
vÍnce
Pro
Sheet Author
Joshua R. said: Fantastic! Thanks, Riley! I should add that it did that when I tested the Pathfinder sheet, as well. Might be worth checking out?  It's always the Pathfinder sheet.  ;-)
It may have affected multiple sheets. It was nothing on the sheet author end it was something on our end.