When the parent GameObject is placed directly in the game scene, there is no issue. However, if the parent node is spawned from another Object using the “Spawn Object” action in Visual Scripting (VS), variables or switches of the child GameObject can no longer be modified.
Example: Attempting to change the variable hp of the child GameObject from 1 to 5 using the “Change Property” action in VS:
a) When placed directly, it changes to 5.
b) When spawned, it remains at 1.
Regarding this, we have encountered an issue where generating a game object that has another game object as a child node does not function correctly due to an unrelated matter. We plan to release a fix for this in the next update.
It may or may not be related to this issue. However, if the problem persists after reviewing the fixes in the next update, please report it to us again.
Additionally,
Although it requires some effort, we have confirmed that the system works by first generating a game object and then generating another game object as a child object from the initially generated game object.
