I'd need to... rearchitect some stuff, and I don't know how soon I'll have time to actually implement it, but... maybe I can do something like that, yes.
Especially given the imminent 5.7 release, which means I'm going to have to try and carve out time to dig into that anyway...
Some of the things you listed will probably still be gone tho, since they're basically stored with the mesh data (definitely the lightmap, maybe some material settings)
Thanks for considering it!
I don't know how your code works internally, but maybe read the existing mesh asset data and copy over certain properties? Though I can't think of a way to make that not confusing for the user if there are things they still want to be changed in Hammer. You could leave it as an option that's off by default.
And I understand that the actor and mesh asset names change if you remove objects in Hammer, so I get it if my request is unfeasible.
Quick update on this, since it's been a while:
I have a plan, but I didn't manage to get it done before the 5.7.0 update because of my ongoing health situation. I'm pushing the 'vanilla' 5.7.0 update without these changes first, but hopefully I'll manage to get something done for you by end of year.
