Meebit gets all dark on re-opening of the blender file.

Think the root cause may be that the base color reference meebit_16734_t_col is not persisted in the blender scene somehow

Add-on required
https://github.com/saturday06/VRM_Addon_for_Blender

Manual process:
https://youtu.be/H7NF_4hhlN4?t=264

Clues to Python API interfaces
https://github.com/saturday06/VRM_Addon_for_Blender/blob/ef1e21a21b0a5162e21694872eac6be470c9971d/io_scene_vrm/editor/mesh_from_bone_envelopes.py#L127
https://github.com/saturday06/VRM_Addon_for_Blender/blob/ef1e21a21b0a5162e21694872eac6be470c9971d/io_scene_vrm/editor/validation.py#L250
https://github.com/saturday06/VRM_Addon_for_Blender/blob/ef1e21a21b0a5162e21694872eac6be470c9971d/io_scene_vrm/exporter/glb_obj.py#L145
https://github.com/saturday06/VRM_Addon_for_Blender/blob/ef1e21a21b0a5162e21694872eac6be470c9971d/io_scene_vrm/importer/blend_model.py#L1249

https://discord.com/channels/841293272071929896/842452265296986134/844364941200457738
i tried the newest release with some of the meebits i had on hand and everything seems to work pretty nice. there is one meebit that gave me problems on import though. for some reason it doesnt snap to the floor (?)... this one:

Default position of 11067 is not as the other meebits.
Blue haired meebit is the default, black rimmed hat is 11067

VRM metadata specification
https://github.com/vrm-c/vrm-specification/blob/master/specification/VRMC_vrm-1.0_draft/meta.md
https://vrm.dev/en/docs/univrm/meta/univrm_meta/

No support for editing VRM metadata in saturday06/VRM_Addon_for_Blender
saturday06/VRM-Addon-for-Blender#38

But fields are put with a default value in the exported .vrm file
https://github.com/saturday06/VRM_Addon_for_Blender/blob/ef1e21a21b0a5162e21694872eac6be470c9971d/io_scene_vrm/vrm_types.py#L32

Hex editor on an exported VRM

Three options:

1. Enhance/fork saturday06/VRM_Addon_for_Blender to include input of metadata.
   Fork is complicated and can become outdated
2. Separate blender step to inject VRM metadata before or after calling saturday06/VRM_Addon_for_Blender
3. Separate step outside blender which does gltf2.0 editting

To me, step 3 seems easiest but relies on finding a gltf 2.0 parsing library

related to not possible to set object mode I believe.

VR add-on exporter class to call
https://github.com/saturday06/VRM_Addon_for_Blender/blob/release/io_scene_vrm/exporter/__init__.py

Useful information
https://blender.stackexchange.com/questions/78935/calling-an-addons-operator-from-python-wm-operator-invoke-invalid-operator-c

This might work

bpy.ops.object.export_scene.vrm('EXEC_DEFAULT')

https://b3d.interplanety.org/en/how-to-switch-between-flat-and-smooth-shading-through-the-blender-python-api/#:~:text=The%20flat%2Fsmooth%20shading%20mode,mesh%20polygon%20to%20%E2%80%9CTrue%E2%80%9D.&text=To%20enable%20flat%20shading%20%E2%80%93%20set,each%20polygon%20to%20%E2%80%9CFalse%E2%80%9D.

ob = bpy.data.objects.get('Terrain')
for poly in ob.data.polygons:
poly.use_smooth = True

See manual steps which are generally very hard to replicate with code
https://youtu.be/H7NF_4hhlN4?t=85

Want to delete these internal faces