Timeline for Why does find_child not work during _ready, but looping over child nodes finds the child?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2023 at 21:51 | comment | added | liggiorgio |
@TomášZato Explicitly (un)setting a Node's owner is useful for certain operations, e.g. selectively serialising Nodes in a branch in a recursive fashion to save/load them in/from a file. In your case, just using additional arguments when calling the find_child() function should do the work.
|
|
| Oct 30, 2023 at 22:28 | comment | added | idbrii |
The Node docs say "[the owner property] keeps track of who instantiated what. This is mostly useful when writing editors and tools, though." So I don't think it matters unless you're writing @tool, code saving PackedScenes, or other editor code.
|
|
| Oct 28, 2023 at 13:40 | comment | added | Tomáš Zato | Should I set the owner for the clones, or does it matter at all? | |
| Oct 28, 2023 at 13:40 | vote | accept | Tomáš Zato | ||
| Oct 27, 2023 at 18:40 | history | answered | idbrii | CC BY-SA 4.0 |