# Simulation Assemble the experience and play it through. ## The user journey from a confirmed flow to a playable simulation Check the inputs, choose the primary language, select a build path, resolve missing resources, and preview the assembled simulation. 01 ### Check the build inputs 1. Select Simulation at the top of the same project and read Simulation Build Status. 2. On the first build, the script or assets may still be pending; AI Generate handles these next. 3. If asked to choose a workflow version, select the customer-service flow you reviewed and Confirm Selection. The panel tracks Workflow, script, assets, and assembled simulation separately. **Why this matters**Repeated generation does not necessarily repair incorrect or missing inputs. **Check the result**You can identify the intended flow and assets without knowingly skipping missing inputs. Not the expected result? Record the missing item before changing unrelated stages. 02 ### Choose the primary language 1. Open Primary Language and search for or select the language for this simulation. 2. Check that the selected value is displayed. 3. You do not need additional languages for a course delivered only in this language. Select the language from Primary Language; add other languages later in Publish. 03 ### Choose how to build 1. For your first build, select AI Generate and wait for the script, asset, and assembly statuses to update. 2. Use Direct Assemble only with an existing complete script and assets. 3. If an action is disabled, read its hint and the status panel before continuing. Resolve a blocked build 1. When new previews may replace existing assets, compare each pair, choose the current or new version, and Confirm & Build. 2. If asked for a style reference, choose an image and Confirm Style Reference & Build. 3. If style conflicts are detected, select one style for each type, then Confirm Style Selection. 4. If Some asset types have no style reference appears, choose Go to Asset Workshop to add references, or Build without references. 5. If Please select primary language first appears, choose a language under Primary Language. 6. If an Upload panel button with a panel ID appears beside a missing item, select it and finish uploading that panel before building. 7. If an error is unclear or keeps failing, select Report error beside it and describe what happened. 8. If the result asks you to select AI Generate again, do so. 9. If an assembled simulation shows Workflow updated, rebuild recommended or Assets updated, reassemble to apply, it does not include the latest changes yet; rebuild or reassemble as prompted, then play it again. 10. Resolve missing required assets before moving to publication. **Why this matters**Assembly completion and correct behavior are different checks. **Check the result**The assembled simulation opens and renders its text, options and assets. Not the expected result? Read assembly errors and correct their cause rather than treating repeated clicks as quality assurance. 04 ### Preview the learner experience 1. When Simulation assembled appears, select Preview Simulation. 2. First choose to check the facts and compare the ending and feedback with your plan; play again and promise a refund immediately to check the different consequence. 3. Check the choices, transitions, endings, feedback, and scores against the design. 4. Return to the project afterward. 5. Fix wording or paths in Workflow and images in Assets, then rebuild and replay before selecting Deploy. Save points when learners play 1. Save points (checkpoints) are chosen automatically from the simulation content and cannot be set in the editor; a screen leading straight into a timed or scored decision does not become a checkpoint. 2. When learners play, reaching a checkpoint saves automatically. Before the first checkpoint they cannot save, and the game shows “Saving becomes available once you reach a checkpoint.” 3. Loading a save later returns to the latest checkpoint, not the last screen before leaving. 4. In a simulation without any eligible checkpoint, learners can still save at any time. **Why this matters**Testing only success paths can miss incorrect choices that are accidentally rewarded. **Check the result**You have a choices → expected result → actual result record with no known blocking issue. Not the expected result? Fix unclear objectives or paths upstream and asset defects in Assets, rather than trying to patch them during publication. ## Finish testing before handing off to learners Record the choices and results of both playthroughs. After fixing known issues, select Deploy at the top of the project. ### See what is ready Read Workflow, script, assets, and assembly status separately before choosing an action. ### Select the right build path Use AI Generate for the full pipeline; use Direct Assemble only when no generation step is needed. ### Check the actual experience Open Preview Simulation after assembly and verify the learner can reach the intended decisions and endings. **What you will see when completed**The simulation is assembled and has been checked in the playable preview. [Publish a simulation and verify access](doc2sim-publish.md)