# Meet the editor Use the editor to change your simulation training: edit what characters say, replace a background, add answers learners can choose, and decide which response appears after each choice. ## Choose how you want to make changes ### ChatTell AI what you want changed For example: “Make the customer’s opening more polite.” Select Chat on the left and send your request. ### CodeEdit the workflow text directly The editor opens on the Code tab, where you edit the workflow syntax. Use this if you know the syntax; afterwards, select Validate to check it and update the graph. ### Graphical EditEdit dialogue, backgrounds and answers yourself Select Graphical Edit on the left, choose a box in the centre, then change its content on the right. No code is needed. Where do I open the editor? In your project: Flow → View Output → Edit / Details → Graphical Edit. The editor opens on the Code tab; node forms and Add Node appear after you switch to Graphical Edit. The refund example on this page is ready to use. [Explore the workflow first](doc2sim-flow.md) ## Choose one thing to practise [Add an answer and its response](doc2sim-editor-branches.md) [Check and save changes](doc2sim-editor-save.md) ## Practice: change the customer’s dialogue and background This refund example is ready to edit and works like the Graphical Edit tab. Change what the customer says, then see the scene with a different background. 1. ### Expand and find the step to change Select Expand and interact. Instructions and node tools are on the left, the graph is in the centre, and the selected node’s fields are on the right. Select V\_start and check the right-hand heading. **Check the result：**The right-hand heading says VIEW · V\_start, with stage settings and Dialogues below. V\_start names this box; VIEW means it presents a scene and dialogue. 2. ### Change the dialogue, not the node ID Scroll down the right panel to Dialogues. Keep Customer as the speaker and replace the text with “There is a problem with the item I bought yesterday. What can I do?” **Check the result：**The dialogue summary on V\_start changes. It is still the same node, with its connection to I\_response. 3. ### Add a line of narration Select Add Dialogue. Set the new line’s speaker to Narrator and enter “Check the condition of the item before deciding how to respond.” Use ▲ and ▼ beside a line to reorder it, or × to remove it. Above each line, + Character action places a character Left, Center or Right, or makes it Exit, before that line; After dialogue at the end of the list applies after all lines. This practice does not need a character action. **Check the result：**Dialogues contains two lines: the customer’s question, then the narration. Adding a line does not create another graph node. 4. ### Change the background and inspect each line Keep V\_start selected. Select Stage Preview (the stage icon) in the centre toolbar. Click Service counter beneath the stage and choose Back office. Use ▼ beside the dialogue to see the second line. **Check the result：**The background changes to the office. The first line is your customer’s question; the next is narration. This previews V\_start without running the learner choices. 5. ### Return to the graph and check the next step Select Back to Workflow, then I\_response. Check the two targets in Choice List. Select Back to manual at the very top, then Expand and interact to check that your edits remain. **Check the result：**I\_response still has its two original choices. Changing dialogue or a background does not change where those choices lead; that is the next lesson. Each chapter starts with its own example. Edits and saves stay on this page. The instructions remain on the left when you expand the editor. What do the box names mean? Each box is called a node. V\_start and I\_response are names identifying individual boxes: selecting a name in Target sends the flow to that box. VIEW contains a scene and dialogue; INTERACT asks the learner to respond. 1. ### V\_start · The customer speaks This VIEW shows “Can I get a refund?” Select it to read the line. Its next step is I\_response. 2. ### I\_response · The learner chooses This INTERACT sends “Check the policy” to V\_help and “Promise a refund” to V\_retry. Each choice has its own target. 3. ### V\_retry · Feedback, then another attempt This VIEW says “Check policy before making a promise,” then returns to I\_response. A route can visit the same node again. Other boxes: when do you need LOGIC and ROUTE? Start with VIEW and INTERACT to arrange a situation, choices and feedback. Add LOGIC and ROUTE when you need to track state or make automatic decisions. | Type | What this step does | Use in refund training | | --- | --- | --- | | `VIEW` | Presents a scene, characters and dialogue, then continues. | A customer explains a problem, or a supervisor explains the next step. Edit stage settings, Dialogues and Flow Control on the right. | | `INTERACT` | Waits for the learner to choose or enter input. | This example uses choice mode: checking the policy and promising a refund have their own targets. The next chapter explains the other response modes. | | `LOGIC` | Runs data or variable operations, then continues automatically. | Record that a policy check is complete or change a score. This is not an answer button; configure it using your project’s variable and command rules. | | `ROUTE` | Checks conditions from top to bottom and takes the first matching branch. | Choose a response based on whether the policy was checked. Configure if / elif / else and their targets; else handles cases that match none of the earlier conditions. | Want dialogue presented as large text over the scene? This is VIEW’s dialogue\_mode, separate from editor tabs and INTERACT response modes. The default uses character dialogue or narration. Under Properties on the right, add dialogue\_mode with the value parchment for large text over the background. Build and play in Simulation to see it; the practice Stage Preview still uses its usual dialogue box. Cannot find dialogue, the stage button or a background? Scroll inside the right panel to find Dialogues. Check that the heading says VIEW; INTERACT has no Stage Preview button. A VIEW without an explicit background may inherit one from an earlier scene. If incoming routes supply different backgrounds, the stage indicates that it depends on the route. After checking, you should be able to identify the dialogue step, the choice step, and your edited dialogue and background. Next, connect a new choice to its own response. [Go to the next lesson](doc2sim-editor-branches.md)