Looking into the size difference, it looks like the models were converted to cvox, which compresses the voxel models. Might be good to switch our official example to the same. Wonder if it impacts the load time…
Looks like Claude had to do a lot of Craft-hacks to get similar rendering appearance, but there is a lot for us to learn in this port. Thanks for doing it!
We’ll add model:copy() and model:assign() to make a voxel editor more efficient to write in Carbide (this allows something similar to Craft’s loadSnapshot / saveSnapshot for edits)
I couldn’t find documentation on the Modern implementation of voxels, and it looked like the terrain example was running the chunk-based voxels, so I didn’t know if voxel volumes were even a thing in Modern.
Wait is the froggy thing using voxels too? I just assumed it was regular craft models but if it’s using voxels that answers my question right there. D’oh!
Why can’t Claude read this link anymore? It claims “It builds its content with JavaScript after loading, so my page fetch only gets the empty “Loading chapter content…” shell.” But I’ve had it read it just fine in the past.
I can open only the Voxels page so far. My web tool only fetches links that appear in the conversation, and every other page on that site is a relative link. The Modern reference also isn’t in search results; searches only turn up the old Legacy pages.
