unity-data-driven

ScriptableObjects and JSON pipelines prevent hardcoded values by externalizing configuration. This data-driven approach enables designers to modify game variables directly via the Unity Inspector or external spreadsheets without code changes.

Handle Unity ScriptableObject data migration by using explicit version fields and the `[FormerlySerializedAs]` attribute to manage breaking changes across game updates. This preserves data integrity when formats evolve.

The best way to load JSON configurations at runtime in Unity is by utilizing the StreamingAssets folder. This approach supports external data pipelines and allows dynamic data loading without recompiling the application.

Yes, Unity supports editor-based CSV imports to facilitate designer workflows. Designers can manage game data in external spreadsheets, which programmers can then import to populate ScriptableObject assets.

Use ScriptableObjects for Inspector-based designer handoff and embedded assets, while JSON suits runtime loading via StreamingAssets. Both data-driven approaches prevent hardcoded values but serve different pipeline needs.

Set up a designer handoff workflow by creating `EnemyConfig` ScriptableObject assets. Designers can then directly adjust health, speed, and damage values in the Unity Inspector without requiring a programmer to modify code.