domains / families / software-engineering / scenario-unity-architecture

scenario-unity-architecture

separate

Use when structuring Unity 6.3 C# code: ScriptableObject data vs runtime state, events and services, inventory, health, save and load, Input System actions and key rebinding, async with Awaitable, assembly definitions, Enter Play Mode and domain reload, .meta files, Git, Smart Merge and LFS. Also when 'my save works in the Editor but not in the build', statics keep values on the second Play, events fire twice or never, an await runs after its object died, rebinds are lost on relaunch, a renamed class loses its data, a scene merge breaks.

When to use

• ScriptableObject data vs runtime state
• events and services
• inventory, health, save and load
• Input System actions and key rebinding
• async with Awaitable
• assembly definitions
• Enter Play Mode and domain reload
• .meta files, Git, Smart Merge and LFS

Skill page

Source