State Designer

Atlas can explain attached State Designer state machines and generate GameObject or ECS Actions and Conditions. Use State Designer 1.3.0 or newer and open Tools > Opsive > State Designer > Atlas, or its docked panel.

Explain a state machine

Attach the state machine or its owning object. Ask about a specific transition, state, or execution result:

/ask Explain why this door remains in Open after the close request. Identify the transition and condition settings to check before changing code.

Atlas reads the corresponding authoring-layer graph, including topology and serialized node settings. Include the observed active state or a screenshot when diagnosing a runtime problem. A snapshot does not contain the full history of earlier transitions.

Example: a distance Condition

1. Create a small test state machine with two states and a transition between them.
2. Ask for one condition with explicit missing-reference behavior:

/gen Create a GameObject Condition that is true when an assigned target Transform is within a configurable distance of the owner. Return false if the target is missing. Use State Designer's supported Shared Variable fields.

1. Review whether the result is a Condition, with boolean evaluation, rather than an Action performing work over time.
2. Save the source under an Assets/... folder and wait for compilation.
3. Add the Condition to the test transition and assign its owner, target, and distance fields as required by the generated implementation.
4. Move the target inside and outside the threshold. Confirm the transition responds as intended, then remove the target reference and confirm it evaluates false.

Actions, Conditions, and ECS

An Action performs work as part of a state lifecycle. A Condition evaluates whether a requirement is satisfied. State the intended role instead of asking for an ambiguous “node.”

For an Action, test entry, update, completion, exit, interruption, and re-entry. For a Condition, test true, false, and missing-data cases. Avoid moving or mutating unrelated objects as a side effect of a condition check.

For ECS, explicitly request the ECS flavor and describe required component data and scheduling assumptions. One generated source artifact can include the associated authoring, buffer, flag, and system/job types; review the complete artifact.

Finish the integration

Generated source defines new types. Add them to states and transitions through the normal State Designer editor and assign the relevant Shared Variables. A generated package does not automatically assemble your state machine.

Continue with the State Designer manual, State Designer Atlas integration, or Generating and applying code.