Replies: 1 comment 1 reply
-
another use case is to expose nodes with signals that aren't the parent node. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, often when I am making a scene I need to put the most important script at the top, or use editable children that risks data loss.
I find myself wanting to adjust the data of a few specific nodes of the child scene without adding an export property to the parent, or using editable children to expose unnecessary nodes that I do not want to touch.
use cases:
Reusable area2d scene, that can change it's collision shape. or be part of a parent scene with a model or physics body, that does not need to be duplicated for each variant.
A scene that can modify it's visual look based on a random seed, parented by a script that does other things for the object.
Scenes with heavily parameterized components, so that I don't have to expose them to the parents nodes for level gimmicks and such, and instead edit the exports directly, like lower gravity
Beta Was this translation helpful? Give feedback.
All reactions