Scripts log errors: Could not deserialize data

Accipiter · April 11, 2025, 3:12pm

With Release v1.65.0 I introduced a bug that caused scripts to give errors such as:

Could not deserialize data {“id”:“xxx”, … } to type Char. Make sure to add the correct decorators to classes. at ~lib/json-as/assembly/index.ts:254:7

This only affected room scripts updated after the release. Thanks to Ace, @Shinyuu and @farcaller, I got to track it down with my sniffer, and eliminate it!

How to fix your code

Scripts created in game console

Make a tiny update to the script with:

set roomscript myBrokenScript : source = // Updated script

Scripts created with mucklet-script

Install the latest version (v1.65.2) of mucklet-script and deploy again. Example:

cd myBrokenProject
npm install mucklet-script@latest
npm run deploy

Bug issue

github.com/mucklet/mucklet-script

Could not deserialize data

opened 01:48PM - 11 Apr 25 UTC

anisus

## Issue When building or deploying with `mucklet-script` installed in a packag…e under `./node_modules`, an error occurs when deserializing data: >Could not deserialize data {"id":"xxx", ... } to type Char. Make sure to add the correct decorators to classes. at ~lib/json-as/assembly/index.ts:254:7 The compiled _wasm_ files are also smaller, seemingly not containing the json-as transformer's code for deserialization. The issue does not seem to occur when `mucklet-script` is installed globally or when linking to a local version of mucklet-script with: ```text npm link ../path/to/local/mucklet-script` ```

farcaller · April 11, 2025, 3:38pm

It’s ok, I already rewrote the code in blessed C, faked the assemblyscript memory management and used the resulting wasm.

</sarcasm>

(thanks for fixing this!)

Accipiter · April 12, 2025, 3:21pm

squinting eyes

… with you, I am not entire sure you actually wouldn’t try to do such a thing