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

"Pathfinder by Roll20" Character Sheets are broken and causes API errors

Is this a known issue? How to reproduce: 1. Create a new campaign 2. Pick the "Pathfinder by Roll20" option for Character Sheet setup for the new campaign 3. Go to the campaign's scripting and make a new script, it can be empty. 4. Start the game so that the API sandbox starts running. 5. You get this: Spinning up new sandbox... "Starting webworker script..." "Loading 676 translation strings to worker..." "Starting webworker script..." "SyntaxError: Unexpected token ..." "SyntaxError: Unexpected token ...\n    at eval (<anonymous>)\n    at messageHandler (evalmachine.<anonymous>:284:6)\n    at process.<anonymous> (/home/node/d20-api-server/node_modules/tiny-worker/lib/worker.js:60:55)\n    at emitTwo (events.js:106:13)\n    at process.emit (events.js:194:7)\n    at process.nextTick (internal/child_process.js:766:12)\n    at _combinedTickCallback (internal/process/next_tick.js:73:7)\n    at process._tickCallback (internal/process/next_tick.js:104:9)"
1547388050
Natha
KS Backer
Sheet Author
API Scripter
Hi Drakim. It should not prevent API scripts from running. For example, I'm using ChatSetAttr with the sheet without problems. Probable cause is use of ES6 syntax in sheet workers, and the version of Node running the API is behind the version of the one running the sheet workers, and not handling all ES6 syntaxes very well. But the ES6 syntax in the sheet's workers is encapsulated in a pattern module so should not break the API. But this will be investigated. Thanks for the feedback.
1547421266
Natha
KS Backer
Sheet Author
API Scripter
Source of the error found and should be fixed in the next update (should be available tuesday).