I don’t know what you had going on there in your _init() method.
But I would strongly recommend you not to use _init() for your nodes (if not only a specific case). The _ready() method is there for the purpose.
It’s because _init() is the constructor callback which may intervene with some internal stuff.
And _ready() is called right after the node is hooked up to the tree and ready to go.
This node will be created (instantiated) often by its parent. I thought this way I can set its parameters compactly during construction. I just started using this engie, so I didn’t know that it would break it.
hansolo | 2017-09-08 06:58
You shouldn’t have had broken it though. I’ve tried to get a similar setup in the test project with custom _init() callback on the child node, and everything went well, so don’t quiet get what is exactly wrong with your _init().
If you have nothing but simple params initialization, then _read() is a recommended and default way to go.