Chroniques Oubliees official sheet crash

Could someone help with this bug : "adding" the sheet from roll20 generates errors in sandbox, while copy/pasting the code from Github works fine. Error is : "Starting webworker script..." "Loading 0 translation strings to worker..." "SyntaxError: Invalid or unexpected token" "SyntaxError: Invalid or unexpected token\n at eval (&lt;anonymous&gt;)\n at messageHandler (evalmachine.&lt;anonymous&gt;:284:6)\n at process.&lt;anonymous&gt; (/home/node/d20-api-server/node_modules/tiny-worker/lib/worker.js:65: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)" Has anybody encountered such a problem already ? Is that an encoding / special character problem ? Also reported here :&nbsp; <a href="https://app.roll20.net/forum/post/7871317/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/7871317/slug%7D</a>

We still need help for this. Using the sheet directly from roll20 generates an error all the time. When importing the same code in a sandbox manually, there is no problem. Please, help ? Anyone ?

After one week where the error disappeared, it came back after yesterday's release. Help !

Does the error stop scripts from working?

No, it does not. Which is even weirder ...

We're looking for the help of anyone that could help us understand what's going on with that official sheet error.

Far2Casual said: We're looking for the help of anyone that could help us understand what's going on with that official sheet error. Is there a reason you call it an "official" sheet? That's certainly not an Official Roll20 sheet, and it doesn't seem to be explicitly labelled to be created the publisher either. The absolute majority of character sheets on Roll20 are community created, so there is nothing official about them.

It's very likely that one of the sheet's sheet workers is constructed a little badly. But if the sheet is working fine, and the scripts are working fine, you should be able to safely ignore it. Is it causing any problems?

Andreas J. &nbsp;said: Is there a reason you call it an "official" sheet? That's certainly not an Official Roll20 sheet, and it doesn't seem to be explicitly labelled to be created the publisher either. The absolute majority of character sheets on Roll20 are community created, so there is nothing official about them. Official might not be the appropriate term, my apologies. What I meant by "official" is that both the sheet and the script can be imported directly from roll20, but both generate errors that we would like to fix. GiGs said: It's very likely that one of the sheet's sheet workers is constructed a little badly. But if the sheet is working fine, and the scripts are working fine, you should be able to safely ignore it. Is it causing any problems? Thank you for the reply. We could definitely ignore it, as the sheet seems fully functional when we use it. As we have a community using that sheet (and the API script COFantasy linked to it), we're just looking at making sure everything meets a certain standard. One of the ideas behind us trying to figure out the problem is that it seems there is a similar problem with the COFantasy API script. While the script is working fine when we "import" it, roll20 generates an error when we try to use the standard "Add" function (that allows a user to automatically get the updates of that script in his game). We are currently doing a lot of development on both the sheet and the script at the moment. If we could figure out what the "invalid token" is in the sheet, this could maybe also guide us in figuring out why the COFantasy script is currently bugged with the "Add script" functionality.

Invalid token usually means a typo somewhere in the script (in this case, the sheet workers in the sheet), or the wrong sort of variable is being assigned. But the sheet worker sandbox is set up so that crashes there don't propagate, you should be able to safely ignore it. If you could edit the sheet, you could try removing various sheet workers till you find the culprit, but since the the error doesnt happen with the custom sheet, only the roll20 install, you cant do that. (And that is weird behaviour.)&nbsp; Errors in the API script are another matter.&nbsp; There have been issues with roll20s oneclick install before, where it does something to the installed file that creates errors. If this is happening with both the sheet and the API script, it might be worth checking out with <a href="mailto:team@roll20.net" rel="nofollow">team@roll20.net</a> to see if there is an issue at their end.&nbsp;

To be perfectly clear : For the sheet, when I add it to a game, the above error message will appear in the Sandbox, but the sheet is working fine. If I launch a Sandbox with a Custom sheet and C/P all elements from the Github, I get no error message. Your suggestion for the debugging is clever, but I can't do it because if I do it via a Custom sheet everything works suddenly. For the script, the oneclick install via "Add" crashes the sandbox immediately. Via "Import" everything runs fine, the same if you add a Custom script and you just C/P the script code from the Github. There's definitely something happening on roll20's side, both with the script and sheet. Unfortunately, we're unable to figure out what exactly. Unfortunately, none of our tentatives to take contact with roll20's team, over multiple months (including the email, the Help center) got any response :(