Get Objects In Prefab Node Returns Only Parent Object

In Custom Games, retrieving objects via the Get Objects In Prefab node may only affect the parent object instead of all constituent parts. A simple fix is available.

When using the Get Objects In Prefab node in Custom Games, object transformation nodes may only successfully move or rotate the parent object of the prefab. While the node correctly identifies and returns all constituent objects within the prefab, subsequent transformation commands often fail to apply to the child objects.

Observed Behavior

The issue appears to be a discrepancy in how object transformations are handled between Forge mode and Custom Games. In Forge mode, transformations applied to objects retrieved via a prefab function as expected, affecting all objects in the list. However, in Custom Games, these same transformations may only affect the parent object.

Discrepancy Between Forge and Custom Games

It is important to note that the Get Objects In Prefab node itself continues to return the correct list of objects. This has been observed in instances where other properties, such as spawn order, are set on the retrieved objects; the system correctly identifies and applies these changes to the full list of children.

Testing has revealed several nuances regarding this behavior in Custom Games:

• List Integrity: The returned list size is accurate (verifiable via Get List Size), and objects can be successfully cast to the object type.

• Validity Discrepancies: Some objects within the returned list may return FALSE when checked with the Get Is Valid Object node, even if they are present in the list and can be cast to objects.

• Direct Access Failure: Attempting to move a specific child object directly using the Get Object At Index node also fails to move the child in Custom Games, mirroring the failure of the loop-based approach.

The failure is specific to the interaction between the retrieved child objects and object transformation nodes (such as Move Object to Point) when running in a Custom Game environment. This behavior has been reported as occurring following the May update.

This behavior may not be present when testing in Forge mode. Always verify script behavior in a Custom Game environment to ensure transformations are applying to all intended objects.

Workarounds

Several methods can be used to ensure that all objects within a prefab are correctly transformed in Custom Games.

Label Swapping

The most effective way to resolve this issue is to "refresh" the prefab by temporarily changing its User Labels. This process appears to force the constituent objects to properly subscribe to the systems responsible for transformations and translations in Custom Games.

To perform this:

• Select the prefab in Forge.

• Change a User Label slot from None to any other available label.

• Immediately change that same slot back to None.

Once the label has been swapped back to None, the Get Objects In Prefab node should function correctly, allowing transformation nodes to affect all constituent parts of the prefab.

Manual Reference Methods

If label swapping is not suitable for a specific implementation, other more manual methods can be used to ensure children are transformed:

• Explicit Object Lists: Manually declaring an object list to hold the specific objects intended for transformation. While this ensures the transformations work, it can increase the complexity and "bulk" of the script.

• Script Brain References: Assigning an object reference within the script brain to every individual object inside the prefab. This ensures the script has a direct connection to each child, though it is considered a more cumbersome implementation.

---

Source Data

• Discord thread: Get Objects In Prefab Node Returns Only Parent Object

Contributors

Riveringston Artifice green Okom AddiCt3d 2CHa0s Cookies