Duplicating a node should result in either a true Instance or true unique copy, not a mix of both

<!-- Please fill in *all* the questions below and don't remove any of them. Proposals not following the template below will be closed immediately. --> **Describe the project you are working on:** In all my projects I'm duplicating and instancing nodes all the time. **Describe the problem or limitation you are having in your project:** When I duplicate nodes, they are neither unique (aka independent or disconnected from their original), nor are they completely connected: a pure instance where changing one thing in any one of the duplicates results in the same change happening to all of the duplicates.  **Describe how this feature / enhancement will help you overcome this problem or limitation:** Having either true Instances of nodes or true unique duplicates would prevent confusion, unintentional changes, self inflicted bugs. Ideally I would like to be able to do something like - rightclick on a node in the Scene Panel for the context menu and select "create Duplicate (Ctrl+D)" to create a unique duplicate - and "create Instance (Ctrl + I )" (or Ctrl+Shift+D) to create a true Instance of the Node I just created. If I would want a specific Resource to be shared, by multiple nodes, I would like to Save the resource as a .res for instance, and then load it into any another node (already possible). This would be intentional driven design for me. **Sho

Posted by golddotasksquestions on Dec 18, 2019, 11:51 AM

Tags

• github (Other)

Related issues

• struct's lifetime requirements can be bypassed via covariant field assignment
• Proposal to Reorganize the Moderation Team and Review Moderation Policies
• Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
• proposal: container/...: generic collection types
• Better Custom Endpoint BYOK
• A concrete policy for backward compatibility until Godot 5.0