unity-script-roles

To assign class responsibilities in Unity, transform your rough script list into explicit roles like MonoBehaviour, ScriptableObject, pure C# service, or installer. This prevents dumping everything into Unity components by aligning each class with its correct architectural responsibility.

Use ScriptableObject instead of MonoBehaviour when a class functions as a data or config container. MonoBehaviour should be reserved for runtime component bridges, while non-Unity domain logic moves to pure C# services to keep responsibilities clear.

The best way to plan Unity script roles for a refactor is to evaluate each script's main responsibility and dependencies. Assign MonoBehaviour, ScriptableObject, service, or installer roles based on architectural guardrails to ensure presenters and state machine nodes do not blur.

Yes, you can use pure C# services with Unity gameplay scripts without MonoBehaviour. Designating non-Unity domain services separates logic from components, using MonoBehaviours only as runtime bridges and installers for bootstrap helpers.

Unity architecture blurs responsibilities when scripts lack explicit role assignments. Without separating MonoBehaviours, ScriptableObjects, and pure C# services, presenters and state machine nodes absorb overlapping dependencies and logic.

Yes, this Unity script role planning works for bootstrap and installer helpers. It evaluates rough script lists and assigns explicit installer roles, ensuring bootstrap logic remains distinct from runtime component bridges and domain services.