# Editor: check, save and play After editing, check that each choice leads to the intended response, then save. Finally, choose answers in Simulation to check what learners see. ## Complete these three steps in your project 1. ### Validate the current changes Select Validate (the triangle icon). Read the errors, warnings and suggestions; fix the relevant node or code and validate again. Error rows have Report error; if a machine panel is missing, the row has an Upload panel button with the panel name. Select it to upload the panel; see the assets chapter. An earlier result no longer describes content changed afterwards. This practice displays guidance instead of running backend validation. [Prepare usable, consistent assets](doc2sim-assets.md) 2. ### Save graph.txt Select Save; the content is saved only when Save successful appears. If saving fails, Report error appears beside the message. A draft with errors can still be saved, so a successful save does not mean the workflow is error-free. If closing shows Unsaved Changes, select Cancel to return to the editor and save; Discard Changes drops those edits. 3. ### Try different answers in Simulation Leave the editor, then build and play in Simulation. Try the successful response, retry and new routes. Check that dialogue, choices, feedback and stopping points match your training goal. ## Practice: keep a copy of your page edits Use the example below if you want to try saving first. It keeps a practice copy on this page without writing to your project. 1. ### Make a recognisable change Select Expand and interact, then V\_start. In Dialogues on the right, change the first line to “First, check the item and purchase details.” **Check the result：**The V\_start dialogue summary shows your new line. It is a page edit, with no practice snapshot saved yet. 2. ### Check both choices separately Select I\_response and check its two targets. Select V\_help and V\_retry to read their replies. For V\_retry, check that Flow Control on the right is I\_response. **Check the result：**Checking the policy leads to V\_help; promising a refund leads to V\_retry; V\_retry returns to I\_response. 3. ### Save this version, then change it Select Save (the disk icon) in the centre toolbar. After the practice save message appears, select V\_start and replace the first line with “This line is not in the snapshot.” **Check the result：**Restore saved practice remains available above. V\_start now shows “This line is not in the snapshot,” which differs from the saved sentence. 4. ### Restore the snapshot and inspect the download Select Restore saved practice and check the first line of V\_start. Select Download practice data (JSON) to keep a file. Use Reset practice to start over. **Check the result：**The line returns to “First, check the item and purchase details.” The download contains the nodes and connections. Refreshing or resetting clears the page snapshot; JSON does not replace project graph.txt. 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. How do Code, Graphical Edit and validation work together? Both tabs edit the same workflow. Switching from Graphical Edit to Code first converts your graph changes into text. After editing Code, Validate updates the graph. Switching back to Graphical Edit validates the text first; if the text cannot be turned into a graph or validation cannot complete, you stay on the Code tab. If errors appear, fix them before relying on the old graph. This page practises form editing; use your project for code and backend validation. Restoring the saved sentence completes the page’s save exercise. In your project, check validation, saving and gameplay separately; none of these results proves the other two are complete. [Go to the next lesson](doc2sim-simulation.md)