> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/unity-plugin/pre-requisites.md).

# Pre-Requisites

Review the prerequisites for integrating Convai with Unity. Ensure seamless setup and functionality.

### Unity Version

{% hint style="warning" %}
The Convai Unity SDK supports a minimum of Unity 2022.3.x or later.
{% endhint %}

{% hint style="info" %}
You should have Git installed locally on your system.
{% endhint %}

## Skills and Knowledge

Before integrating the Convai SDK, you should be comfortable with the following:

1. **Importing Packages**: Know how to import external packages into a Unity project.
2. **Unity Editor**: Be proficient in navigating the Unity Editor interface.
3. **Animations**: Understand how to add and handle animations for assets.
4. **Programming in C#**: Have a basic experience programming Unity scripts in C#.
5. **Script Integration**: Be capable of adding scripts to a game object.
6. **Building and Deployment**: Know how to build and deploy an application to your chosen platform.

Having these skills will ensure a smooth integration and optimal use of the Convai Unity SDK in your projects.


---

# 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://docs.convai.com/api-docs/plugins-and-integrations/unity-plugin/pre-requisites.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.