SequenceController

​

When to use

• Training scenarios — the controller drives child Step components one-by-one, advancing on completion events.
• Onboarding flows — sequential UI or tutorial steps where each must complete before the next begins.
• For VR training, ScenarioActivity owns a SequenceController per activity — you rarely create one directly unless building custom flows.

​

Behaviour

• Owns ordered child Step components.
• State: SequenceState — Idle, Running, Paused, Completed.
• While Running, calls UpdateStep() on the active step each frame.
• Listens on EventDispatcher for Step.Completed / Step.FullyCompleted to advance.

​

Unity events

​

Dependencies

​

Editor tooling

​

Code

using Molca.Sequence;
using UnityEngine;

public class RunOnKey : MonoBehaviour
{
    [SerializeField] private SequenceController sequence;

    private void Update()
    {
        if (Input.GetKeyDown(KeyCode.Space))
            sequence.StartSequence();
    }
}

​

Troubleshooting

• Sequence never starts: call StartSequence() only after RuntimeManager.WaitForInitialization() — the controller uses [Inject] for EventDispatcher and ReferenceManager.
• Step never advances: SequenceController listens for Step.Completed / Step.FullyCompleted events via EventDispatcher. Verify the step calls Complete() and that the dispatcher is injected.
• Steps run out of order: child Step components are executed in hierarchy order (top to bottom). Reorder in the Hierarchy or use the Sequence Visualizer.
• Pause doesn’t freeze step logic: PauseSequence() stops advancement but does not pause Time.deltaTime. Steps with timer logic must check SequenceState themselves.

​

Related

• Step (base class) — child step components
• Core step types — ParallelStep, etc.
• Sequence Visualizer — editor window for browsing/editing step trees
• Scenario activity — VR wrapper around SequenceController

​

Unity Editor

Hierarchy: SequenceController parent with Step children collapsed/expanded; Inspector: SequenceController.