unity-component

To add and configure a Rigidbody component programmatically, you can target the GameObject by name, instanceId, or path, add the Rigidbody, and set properties like mass in a single batch schema operation.

Yes, you can batch copy components between Unity GameObjects by specifying source and target objects through name, instanceId, or path, applying the copy operation across multiple objects to ensure scene consistency.

The best way to list components and read properties is by targeting the Unity GameObject via name or instanceId, retrieving all attached components, and accessing their specific property values like mass or enabled state.

Yes, Unity component scripting supports enabling and disabling components during runtime by targeting the specific GameObject and component, toggling the enabled property to control behavior dynamically without removing the component.

Batch schemas minimize API calls and improve consistency when managing Unity GameObject components across multiple objects, allowing you to add, remove, or modify properties like mass and transforms simultaneously rather than scripting each individually.

To remove a component from a Unity GameObject without deleting the object, target the specific object by name or path and issue a remove command for the attached component, such as a Collider or AudioSource, leaving the GameObject intact.