unity-script

Batch-first Unity C# script creation generates multiple MonoBehaviour or ScriptableObject files in a single call, minimizing Domain Reload churn. You provide multiple script definitions, and the operation processes them together to prevent sequential recompilation overhead.

Refactoring Unity scripts involves safe file operations that rename, move, or replace C# scripts across Assets folders. You specify the target path and new naming convention, and the process handles the file relocation while preserving the script structure.

Compile feedback visibility retrieves Unity compile diagnostics for a specific script after recompilation completes. It handles transient unavailability during Domain Reload by waiting for Unity to finish, then surfacing compile errors for the target script.

Unity script editing supports safe append operations on existing C# files. You provide the target script and the code block to append, and the operation inserts the new code while maintaining the MonoBehaviour class structure.

During Domain Reload, compile diagnostics are transiently unavailable while Unity recompiles. The compile feedback interface accounts for this state, waiting for Domain Reload to complete before retrieving accurate compile errors for the requested script.

Safe script CRUD operations support replacing Unity C# scripts through find-and-replace logic, as well as deleting them entirely. You define the search string and replacement code, and the operation safely modifies the existing script file.