This issue is so common that there are several things in the last 3 days of development that hit this.

– Autopilot … do we provide access to part of the AP or do I just email plugin authors the snippet of code they want access to? (My answer: copy…avoid dependencies on the internals of the AP.)

– Named lights … do we provide users a way to create their own named lights, or are light billboards accessed by reference e.g. "the name"? (My answer: reference…by keeping all light "data" in the sim we are in a position to substantially improve our light billboard art assets and shaders.)

– Airport terminal elements…this was discussed in France. (My answer: reference…LR has a policy of trying to retain very restricted IP licensing of art assets, but obviously we want people to be able to use them – the above thought on future optimization applies too.)

– New instruments…do we make more new default instruments or just provide art assets and let people use them? (My answer: copy…goes against IP policy for art assets above, so I may get push-back, but I tend to think that "owning" 600 instruments is proving to be annoying for LR…we'd be better off giving people some templates, maybe even on the web, and keeping the panel code simple.)

And that's just what I can think of right now…