wave7-managed-singleton-pattern

To access shared managed configuration across ECS, use a one-time bootstrap system to create exactly one singleton entity with a managed component. Other non-Burst systems can then retrieve this shared Unity object via the SystemAPI.ManagedAPI lookup pattern without dependency injection.

No, you cannot read a managed singleton from a Burst-compiled system. Managed singleton access via SystemAPI.ManagedAPI is restricted to non-Burst contexts. The Skill includes safety guardrails to prevent invalid managed singleton access from Burst environments.

The best way to avoid static fields when sharing a ScriptableObject in hybrid ECS is to attach the asset as a managed component to a singleton entity. This approach provides safe system-wide retrieval without maintaining fragile global state or using static fallbacks.

To set up a managed singleton bootstrap, create a system that attaches a managed component to an entity once during world initialization. After creating the singleton entity, disable the bootstrap system to ensure exactly one instance exists for runtime configuration access.

You need a managed singleton pattern for Unity DOTS when your hybrid ECS project requires multiple systems to read shared tuning values or UnityEngine assets at runtime. It solves the challenge of making a single shared managed object accessible without wiring references through constructors.

Your ECS system may fail to find the shared configuration object if the bootstrap system did not create the singleton entity or if you are accessing the managed singleton from a Burst context. Ensure the bootstrap runs once and use SystemAPI.ManagedAPI for non-Burst retrieval.