unity-script-roles

To assign clean script roles in Unity, you provide a target script list to the planner, which evaluates responsibilities and assigns explicit roles like MonoBehaviour, ScriptableObject, or pure C# service. This ensures separation of concerns and clearer modular dependencies.

You should avoid MonoBehaviour usage when a script handles data storage or pure logic without lifecycle needs. The planner guides architecture decisions by recommending ScriptableObject for data or pure C# service classes for logic, enforcing separation of concerns.

The best way to plan Unity architecture for a batch of scripts is defining explicit responsibilities early. The planner categorizes each script into MonoBehaviour, ScriptableObject, or presenter and installer roles, preventing bloated components and guiding modular dependencies.

Yes, you can separate concerns by using ScriptableObject for data containers and pure C# service classes for independent logic. The planner assigns these roles to ensure not every script becomes a MonoBehaviour, enforcing modular dependencies and cleaner architecture.

You do not need a complete script list, but providing a rough list of target scripts allows the planner to assign explicit roles based on responsibilities and lifecycle. This is applicable during early-stage game architecture planning and batch script creation.