> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/dev-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/dev-guide/readme/using-unity.md).

# Using Unity

## Downloading Unity

You will need the correct Unity version to run the project. There are two ways you can acquire it:

#### Method 1:

Check what our [current Unity version](#current-version) is, then find that specific version in the Unity download archives below.

{% embed url="<https://unity3d.com/get-unity/download/archive>" %}
Unity download archives.
{% endembed %}

#### Method 2:

Download [Unity Hub](https://unity3d.com/get-unity/download), then open our project using the hub and it should auto-detect our Unity version and prompt a download for that version.

{% embed url="<https://unity.com/unity-hub>" %}
Unity Hub downloads.
{% endembed %}

## **Current Version**

To avoid having to update the current version in this document every time it's updated, we will just point you to the version file instead.

{% embed url="<https://raw.githubusercontent.com/RE-SS3D/SS3D/develop/ProjectSettings/ProjectVersion.txt>" %}
ProjectVersion.txt
{% endembed %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ss3d.gitbook.io/dev-guide/readme/using-unity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
