Custom Sheet for Fire Emblem

I've been working with a friend to expand the roster of classes available and just generally clean up the sheet for the FE TTRPG, and it worked for a bit before this error began to crop up:  After this came up, the sheets haven't been working properly, even when restoring back to old code we used that had worked initially. This seems to be an internal issue with the Custom Sheet when linking up with the FETT Combat Script API. The reason I say this is because I've gone and made an entirely new Pro profile on Roll20, loaded multiple instances of code (including the one that previously worked), and this exact same issue has followed me like a ghost. We've seen forum posts that had issues similar to this, but none of the proposed fixes worked in our case. I've submitted a Help Request to Roll20 proper, but if anyone's got any idea on what's what, any help would be truly appreciated.

Does a new campaign with the sheet but no scripts work properly?

It can't operate properly without the scripts due to how the original coder set it all up.

That's not why I'm asking. There must be some things you can do with the sheet without the script installed. I'm not concerned about getting full functionality, I'm trying to find out if the error is being caused by the script or by something else. So try to install the sheet without the script, and so something, anything, and see if that error crops up.

Alright, I went ahead and removed the script. I'm not getting that error any more.

That means that somewhere in the script there's&nbsp; an error. See if you an install an earlier version of the script. If the script is here: <a href="https://github.com/Roll20/roll20-api-scripts" rel="nofollow">https://github.com/Roll20/roll20-api-scripts</a> the earlier versions will be there. It seems likely to me that the most recent update includes an error. I'd install an earlier version, and see if you still get the error. And repeat until you find a version that works. Then raise an issue on the github, pointing out there's a bug and link your screenshot (though that doesn't help much - it suggests there's a syntax error somehwere but doesn't say where it is).