unity-script-roles

Assigning Unity script roles involves mapping script lists to recommended class types like ScriptableObject config or pure C# service, avoiding unnecessary MonoBehaviour usage to preserve runtime and memory constraints.

Use ScriptableObject roles for config and data storage in Unity code organization, while pure C# domain services handle runtime logic. This distinction reduces component bloat and ensures better memory management across gameplay systems.

Planning class responsibilities for a Unity gameplay systems refactor requires analyzing script names to assign roles like presenter, state machine node, or installer. This identifies main responsibilities and primary dependencies for each script during architectural updates.

Yes, batch generating Unity code architecture works by providing a list of script names with brief context. The system outputs per-script role recommendations, identifying whether classes should be MonoBehaviour bridges, installers, or state nodes to guide generation.

The best way to reduce MonoBehaviour component bloat in Unity architecture is to assign explicit class roles such as ScriptableObject config, presenter, or pure C# service, ensuring classes only use MonoBehaviour when necessary for runtime constraints.