Reference system

​

When to use

• Cross-scene references — link a step in one scene to an interaction in another without hard SerializeField references.
• Addressable/dynamic content — resolve references after objects are loaded at runtime.
• VR step → interaction wiring — ValveStep finds its ValveInteraction via SceneObjectReference rather than a direct drag-and-drop link.

​

Typical pattern

1. Target: add ReferenceableComponent, set unique Ref Id.
2. Consumer: SceneObjectReference field in Inspector, then Resolve<T>() after RuntimeManager.WaitForInitialization().

​

Code

using Molca;
using Molca.ReferenceSystem;
using Molca.Sequence;
using UnityEngine;

public class ValveTask : MonoBehaviour
{
    [SerializeField] private SceneObjectReference targetStep;

    private async void Start()
    {
        await RuntimeManager.WaitForInitialization();
        var step = await targetStep.ResolveAsync<Step>();
        if (step != null)
            Debug.Log($"Linked step: {step.DisplayName}");
    }
}

​

Troubleshooting

• Resolve<T>() returns null: the target ReferenceableComponent may not be registered yet. Use ResolveAsync<T>() after RuntimeManager.WaitForInitialization() instead.
• Duplicate Ref Ids: each ReferenceableComponent must have a unique RefId within its RefType. Duplicates cause the first registration to win; later ones are silently ignored.
• Reference breaks after scene reload: ReferenceManager clears registrations on scene changes. Re-resolve references in OnEnable or Start of the new scene.

​

Related

• Step (base class) — implements IReferenceable<Step>
• Dependency injection — ReferenceManager is injected via [Inject]
• Valve step — uses SceneObjectReference to find its interaction

​

Unity Editor