Hi odf,

that's a delta-file-concept every only half-good programmer can understand and agree, I guess. Will say it's a good idea.

What I don't understand fully is the need of the second rewritten pz2. I would combine the cr2 and the pz2 directly to one new cr2 which is complet. OK, if you intend to load only some of more morphs than you will need the channel dummies. But I found it mostly impossible to load only the one or other morph. So including all morphs from the pz2 into a new cr2 in one run should not been to worse.

But I think you will need some background mechanics in your scripting prog.
If I got the idea right you may have one original basic cr2 and more than one concurrent pz2's for the same actors by may be serveral creators.

So in this scenario the prog need something like a list to choose from (but please not in flex, could be done easier), something like a companion ini-file.

So it would be best to give the prog a information there the cr2 and all pz2's are located. Then the user can choose from the list which pz2's (multiple choice) should be included and the prog will generate a new cr2 including all choosen morphs.
This should also work if the morphs are in pmd's with one exception, duplicate internal names could not be resolved. But this would be the same problem as with rewriting a pz2 to a new version.

Optional you could give the user possibility to give the new cr2 a significant name and a save directory. And optional the chance to load it directly into poser.

This would be the difference for using the prog from poser or standalone. I think python should be fine to do all this, maybe with the help of some external modules which are not standard in poser environment.