Quote -
edited to add:
i emphasized user because it seems like you're trying to get around the developer issue of having 2 cr2 files.  it seems to me that this is something you could automate?  if you're just generating a new cr2 with a replacement of one obj reference with another.

Okay, I see it now.

Since pose files have some limitation, I'm actually thinking a lot about ways of generating cr2 files automatically. But notice that that's not only an issue for developers. If a developer makes a change to the cr2 and distributes that, and another developer makes a different change, the user would have to download four cr2s to cover all the combinations. Obviously that's an unsustainable strategy. So we'd really need a easy-to-use tool that allows users to generate those new cr2s.

With just pose files, you don't have that problem. A user can simply load all the pose files they want and save the result as a new cr2. So whatever works with pose files, I like to put into pose files (except of course for features that are so commonly used that they should really be in the default cr2).

-- I'm not mad at you, just Westphalian.