unity-script-roles

To decide if a script should be a MonoBehaviour or ScriptableObject, evaluate its architectural role and data ownership. MonoBehaviour handles GameObject interactions, while ScriptableObject manages shared data, preventing tight coupling and clarifying lifetime ownership for better separation of concerns.

The best way to assign architectural roles to Unity C# scripts is evaluating main responsibilities and dependencies. This categorizes scripts into MonoBehaviour, ScriptableObject, pure C# services, presenters, state machines, or installers, producing per-script recommendations for a clean design plan.

Defaulting every new class to MonoBehaviour causes Unity architecture issues by creating tight coupling, unnecessary GameObject attachments, and unclear responsibilities. Assigning specific roles like pure C# services or presenters improves separation of concerns and code maintainability.

Yes, you can get a rationale for choosing a pure C# service over a MonoBehaviour. The role assignment process provides per-script recommendations including main responsibility, core dependencies, and a short justification explaining why the chosen role fits better than alternatives.

You need to separate concerns using presenters or installers in Unity C# when feature scoping requires a clean design plan. Assigning these architectural roles prevents MonoBehaviour overuse, clarifies data ownership, and provides structured guidance suitable for automated code generation.