> For the complete documentation index, see [llms.txt](https://octanta-studio.gitbook.io/automatic-tutorial-maker-for-unity-in-game-tips/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://octanta-studio.gitbook.io/automatic-tutorial-maker-for-unity-in-game-tips/usage-guide/tutorial-creation.md). # Tutorial Creation {% hint style="info" %} **Do not reboot or leave the scene while recording.** {% endhint %} Here, the recording logic is handled within the Automatic Tutorial Maker (ATM) script. 1. **Run the scene** ▶**.** It is recommended to reset the progress back to the start (clear Player Prefs or JSON files) before. 2. **Click the Start Recording button** in the AutomaticTutorialMaker. Recording has started, and all your actions in the Game window are being tracked in real time now.

ATM button to record tutorial for this scene. Play Mode required

3. **Show what needs to be done.** Every interaction is recorded as a step in the Step Sequence list in ATM, allowing to later show the player what to do.

4. **Show the full sequence** the player needs to learn. For example, click an object, drag one object onto another, use WASD, swipe, scroll - everything required **to complete the active scene** from start to finish. 5. **Click the Stop Recording button** in the AutomaticTutorialMaker when ready. This will initiate the exit from PlayMode and save the generated tutorial. If the button isn't pressed and Play Mode is exited, nothing will be saved.

6. **Run the scene.** Now you see the basic visual tips that ATM has generated based on your actions. Try following the tutorial to test it.

7. **Click the Reset Tutor Progress button** in the StepSequencePlayer at runtime to reset the progress and check the tips from the very beginning.

SSP button to reset progress on the scene. Play Mode required

Now that the foundation of the tutorial is created, it can be customized in Edit Mode. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://octanta-studio.gitbook.io/automatic-tutorial-maker-for-unity-in-game-tips/usage-guide/tutorial-creation.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.