unity-component

You can add and configure Unity components by targeting a specific GameObject identifier and applying property handling rules through MCP operations. This skill manages physics, rendering, audio, and custom script components safely without unsafe scene modifications.

Yes, batch operations allow you to apply Unity component changes across multiple GameObjects efficiently. This reduces unnecessary API calls while adding, removing, or configuring components like Rigidbody and Collider on several objects at once.

Removing or inspecting Unity components safely requires accurate component type names and object targeting identifiers. This skill uses MCP operations to manage component data reliably, preventing incorrect API assumptions that could break your scene.

Yes, Unity component property configuration supports updating values, scene references, and project asset references. You can modify component properties by providing accurate property handling rules during the MCP operation.

Unity component modifications often fail due to incorrect API assumptions or inaccurate component type names. Reliable scene modification requires precise object targeting identifiers and strict property handling rules to avoid errors.

Yes, this skill manages both built-in Unity components like Rigidbody, Collider, and AudioSource, as well as custom script components. It handles adding, removing, enabling, disabling, and inspecting them through MCP operations.