It was hard for me to find out how to instance a meshpart and set its MeshId with code in studio. Tucked away in InsertService was CreateMeshPartAsync! Since meshpart’s MeshId is read-only, even in studio command line, it should mention the alternative to setting it with insert service.
Page URL: https://create.roblox.com/docs/reference/engine/classes/MeshPart
I definitely agree that it would be good to mention this in MeshPart’s documentation. I think this better fits in https://devforum.roblox.com/c/feature-requests/170 instead of here.
That’s valid. Specifically we should add a note to MeshPart.MeshId along with the note on why we don’t allow it to be directly updated from Lua.
We’re planning to move some of these around and make them accessible at runtime too as part of the larger effort around DynamicMeshes etc. We’ll make a note to update this along with those changes.