| name | unity-tool-creation |
| description | Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context. [GENERATED BY MOTIF — review and customize] |
Unity Tool Creation
Workflow for creating Unity tools and features that can be tested in isolation. Prevents untestable features in a multiplayer context.
When to Use
- User describes a visual effect or camera angle needed
- User requests a new scene element or UI component for Unity
- Especially when: the feature involves multiplayer elements that are hard to test alone
Instructions
- Clarify the visual requirements if the description is ambiguous
- Create a C# script implementing the requested feature
- Add a debug/test button in the Unity Inspector so the feature can be tested without other players
- Integrate with the existing camera or scene system
- Provide clear instructions for testing in Unity Editor
- Note any dependencies on other systems (WebRTC, multiplayer state)
Best Practices
- Always add a debug button for isolated testing
- Keep new scripts focused on one feature
- Avoid: Don't modify existing camera systems without discussing first
Common Pitfalls
| Problem | Solution |
|---|
| Feature can't be tested without multiple players connected | Add mock/debug mode that simulates multiplayer input |
| New script breaks existing camera system | Test with existing features enabled before committing |
Key Constraints
- Every visual feature must have a debug/test button
- Don't modify existing camera systems without user approval