Asking Questions
Export
Use Ask when you want an explanation, diagnosis, or recommendation before creating code. Start a request with /ask to make that intention explicit.
/ask Explain when this behavior tree returns to Patrol after the target is lost. Do not generate code.
Ask about an existing setup
- Open Atlas for the relevant product.
- Attach the object, graph, or script involved. See Providing context.
- State what you expect and what actually happens.
- Include the shortest steps that reproduce the difference.
- Ask Atlas to identify which setting or lifecycle step explains it.
A useful request is specific:
/ask This guard switches from Patrol to Chase when the player is visible, but never returns to Patrol. I expect it to return after losing sight for two seconds. Explain which transition or condition to inspect first.
An attached graph gives Atlas topology and serialized node settings. It does not prove what happened in every frame of a previous Play Mode session. Include the active state, task status, Console error, or screenshot that demonstrates the problem.
Refine the answer
Keep follow-ups in the same chat. If Atlas assumes the wrong component or lifecycle, name the exact type and attach the relevant source. Ask it to separate observations from assumptions and to propose one check at a time.
For a broad feature request, ask whether a built-in task, Action, Condition, or ability already satisfies it. Using the existing implementation can avoid unnecessary custom code.
Move from explanation to implementation
When the approach is clear, use /plan to define responsibilities and verification steps, or /gen for a small, concrete artifact. Ask mode itself is useful without creating or saving a script.
If the issue persists, share the installed versions, a minimal reproduction, and the exact error with Opsive support. Review Troubleshooting before sending a report.