> 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/setup-less-than-1-min.md).

# Setup (< 1 min)

1. Import the asset package into your Unity project.
2. Add the TutorialSystem prefab to your scene.

{% hint style="success" %}
Starting from version ATM 3.0.1 the rest of the **setup is performed automatically**, when the prefab is added to the scene. It includes reference lookup and unpacking. You only need to check for the following points.
{% endhint %}

3. Unpack the prefab.
4. **Assign the Main Camera (required).** In the Tutorial Scene References, assign your Camera to the Main Camera field.
5. **Assign the Target Canvas (required).** In the Tutorial Scene References, assign your Canvas for UI to the Target Canvas field.
6. Check the Target World Holder. In the Tutorial Scene References, use referenced object or assign your own as the holder for 2D/3D hints.
7. Check the Current Device ATM. In the Tutorial Scene References, give this TutorialSystem a unique name to avoid conflicts with other ATMs on the scene in the future.
8. **Check the Input Controller (required).** In the Input Controller set the current project Input System (Old/New).
9. **Check the Event System (required).** There must be one enabled Event System in the scene. If an Event System already exists in the scene, delete the backup one inside the object. If it is needed, make sure it is properly configured for the Input System.

<figure><img src="/files/SvIiuMoqv83uzfBqnPn0" alt=""><figcaption><p>Fields required to fill</p></figcaption></figure>

The asset is ready to use immediately after these steps.


---

# 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/setup-less-than-1-min.md?ask=<question>&goal=<endgoal>
```

`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.