I haven't considered this, but I see your point. I'd love to do a world with its own micro-economy, but you can't do that if it resets every time the world does. To Gino's question (if they read this), I think what CODEngineer is referencing is more "under the hood" talk. Usually in network connections involving JSON, we stringify objects for passing simple text and then the other end turns it back into an object (remember, objects, assets, etc. are all just text until the engine "interprets" them into 3D). From a user perspective, the code box would still have the same regular types and no concept of how they're being shared. I love the idea. I just saw that Horizon plans to move to WebGL, and when that happens this should absolutely be possible, even if I have to build/rent my own MongoDB server (since I would be blown away if a web version of Horizons was built on anything but a MERN stack, since Meta owns and writes ReactJS).

I agree this is critical for creating a network of worlds. However, I think would be cleaner to have all types available, rather than inferring from a string.

This is a really important concept that Meta needs to consider. A world-persistent variable is the first step toward creating a persistent but evolving world state--one of the key components of a true metaverse definition. In other words, a world shouldn't necessarily reset to its beginning state whenever a new session is instantiated.