Template sets

Add a second template in the Templates pane to create a set from the open project. New template… creates one using the setup window; Add existing template… opens an editable source. In a set, Add .ogs Template… adds another source. File → Save writes one portable .ogs containing template sources, shared controls and dependencies. Compact saves store identical font/resource bytes and set component sources once. Opening restores complete editable templates with the same IDs, bindings, animation and overrides. Extracted compact member files require the set's shared data. Use Save Template Copy… for a standalone editable document or choose Current template in File → Export… for a standalone playout export. Saving shows template/resource/compression progress and runs archive generation in a worker, so the editor and its bridge can keep responding. Edits made during saving remain in the open document.

A new set starts as Untitled Template Set. Double-click its root in Scene Outliner, or select it and press F2, to rename the set. Saving the set .ogs under a different filename updates the set name and the archive's root. Saving a child .ogs updates that template's name; the container keeps its own name. Scene Outliner labels roots as Template Set or Template to show the document type.

Studio saves sets using compact archive schema 6. Earlier versions that read schema 5 require a compatible archive, which can be created through MCP; that copy retains the older archive layout and can be larger. Newer features are not down-converted. Current Studio still opens older schema 1–5 sets and legacy .ogp sets. Older Studio versions that expect JSON .ogs cannot read any multi-template .ogs archive. Add .ogs Template… accepts a single template only; open a multi-template document as a set to retain all members.