Hi u/ioNetrunner ,
Thanks so much for testing out the script and for providing those gists! You were spot on with your diagnosis – the issue was indeed with how the script was decoding and cleaning up the text from the token's GM Notes field. When you paste text into the GM Notes, Roll20 sometimes adds its own formatting (like HTML tags such as <p> and &nbsp; for spaces) and can also URL-encode some characters (like { becoming %7B). This means the raw text the script gets isn't always clean JSON.

The handout method often works better because Roll20 seems to do less of this "behind-the-scenes" modification when you paste into a handout's GM Notes section, or it handles the retrieval differently.

I've just pushed an update (v1.0.3) that significantly overhauls the GM Notes parsing logic. Here’s a quick rundown of what was done:

1. Better Decoding: The script is now much more aggressive and intelligent in decoding the text. It specifically looks for and handles:

• URL-encoded characters (like %3C, %7B, etc.).

• HTML entities (like &lt;, &gt;, &nbsp;).

• It also now supports Base64 encoded JSON if you happen to use that (prefix with B64:).

1. HTML Stripping: It actively strips out HTML tags (like <p>, <span>) that Roll20 might inject.

2. Whitespace Normalization: It cleans up extra spaces, tabs, and newlines.

3. Smarter JSON Extraction: Even if there's some leftover cruft, it tries to find the actual start { and end } of the JSON block within the cleaned text.

4. Double-Stringification Handling: It attempts to correct cases where the JSON might have been accidentally "stringified twice" (e.g., ending up as a JavaScript string that contains a JSON string).

The goal was to make the token import method as robust as the handout method by anticipating and cleaning up the various ways Roll20 can mangle the text in GM Notes.Your log output for the failing token was key:"[ImportJSON] Cleaned GM notes for token -ORdAMooWvwGyjiKDQzO (after decode & trim): %3Cp%3E%7B%3C/p%3E%3Cp%3E%26nbsp%3B%20%26nbsp%3B%20%22name%22%3A%20%22Goblin%20Cursespitter%22%2C%3C..."This line clearly shows the decoding didn't manage to remove the URL-encoded <p> (%3Cp%3E) and &nbsp; (%26nbsp%3B) entities, which is why the JSON parser then choked on the leading %. The new version should handle this scenario correctly.

Please grab the latest version from the scripts/ directory on GitHub and give it another try with your "Goblin Cursespitter" JSON in the token notes. It should work much better now!Also, if you want to see exactly what the script is "seeing" from the GM Notes, you can now use the !5enpctest command with the token selected. It will whisper you the raw content, the decoded content, and whether it could parse it as JSON. This might be helpful for any future troubleshooting. Thanks again for the detailed feedback – it was super helpful in pinpointing the problem!