Templates are a way to create convenient and reusable packages in Core. They can be modified 3D objects, complex models, scripts, completely scripted objects, or collections of all of these. Templates can be identified in the Project Content window by this icon:
Once a group becomes a template, it will be blue in the Hierarchy. New templates can be found in Project Content > My Templates. From there you can drag out as many copies of the template as needed.
Hands-on: Create a template from the parent folder of your kitbashed bed.
Once a 3D model is made into a template, it will resist changes besides positioning and resizing all of its dimensions together to preserve its basic shape. To make changes to the materials, dimensions, or individual pieces of a template, it will need to be deinstanced.
What is an instance?
A template can be understood as a recipe. Each time the recipe is made, that product is an instance of the template. Deinstancing would be making a change in the final product of the recipe, so that it is now different from the exact copies of the recipe. Changing the recipe itself — updating the template — should change every single instance of the recipe.
To make changes to a template, you will need to first deinstance it. This can be done automatically by making a change to the template.
The first screenshot is a deinstanced template that has been modified. The other two templates at the back are not yet updated. The second screenshot was taken after right-clicking on the deinstanced template and selecting Update Template From This. The deinstanced template is now an instance of the template and all the other instances are updated.