> For the complete documentation index, see [llms.txt](https://owo-game.gitbook.io/owo-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://owo-game.gitbook.io/owo-api/welcome/configure-your-project.md).

# Configure your project

We previously explained what a [baked sensation ](/owo-api/welcome/what-is-a-sensation.md#baked-sensations)is; sensations that have an identifier and whose parameters cannot be changed, allowing you to send them with only their ID after you have configured your project.

To configure your project, you need to define a Game Auth. This object contains all the baked sensations of your project, and must be configured **before** **the** [**connection**](https://owo-game.gitbook.io/unreal-engine/connection) is established.

{% hint style="danger" %}
Trying to send a baked sensation that has not been declared in your game auth will not work, so make sure that any baked sensation that you send was properly declared.
{% endhint %}

The Game Auth also contains the ID of your project, this unique identifier gives you the following benefits:

* **Identity:** The name of your project will appear in the MyOWO app during the connection process.
* **Calibration:** Your game will have its own calibration menu in the MyOWO app.
* **Quick Connection:** Once a user has connected to your game once, they will be able to quickly connect to it from the MyOWO app.

### Game ID Request

To obtain your own game ID, contact us via email (<devs@owogame.com>) with the following information:&#x20;

* Developer name.
* Your project name.
* Brief explanation of the sensation that your project includes.
* An executable of your project/mod.

### Creating the Game Auth

You may create a game auth in two different ways, using the exported **.owoauth** that the [sensations creator](/owo-api/tools.md) provides:

{% tabs %}
{% tab title="C#" %}

```csharp
var auth = GameAuth.Parse("0~Ball~100,1,100,0,0,0,Impact|0%100,1%100,2%100,3%100,4%100,5%100~impact-0~#\n1~Dart~12,1,100,0,0,0,Impact|5%100~impact-1~");
```

{% endtab %}

{% tab title="C++" %}

```cpp
auto auth = GameAuth::Parse("0~Ball~100,1,100,0,0,0,Impact|0%100,1%100,2%100,3%100,4%100,5%100~impact-0~#\n1~Dart~12,1,100,0,0,0,Impact|5%100~impact-1~", "4321");
```

{% endtab %}
{% endtabs %}

Baking the sensations yourself and passing them over to the Game Auth.

{% tabs %}
{% tab title="C#" %}

```csharp
var ball = BakedSensation.Parse("0~Ball~100,1,100,0,0,0,Impact|5%100~impact-0~");
var dart = BakedSensation.Parse("1~Dart~12,1,100,0,0,0,Impact|5%100~impact-1~");

var auth = GameAuth.Create(ball, dart).WithId("4321");
```

{% endtab %}

{% tab title="C++" %}

```cpp
auto ball = "0~Ball~100,1,100,0,0,0,Impact|5%100~impact-0~";
auto dart = "1~Dart~12,1,100,0,0,0,Impact|5%100~impact-1~";

auto auth = GameAuth::Create({ ball, dart }, "4321");
```

{% endtab %}
{% endtabs %}

Lastly, pass the game auth you just created to the `Configure` method.

{% tabs %}
{% tab title="C#" %}

```csharp
OWO.Configure(auth);
```

{% endtab %}

{% tab title="C++" %}

```cpp
owo->Configure(auth);
```

{% endtab %}
{% endtabs %}


---

# 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://owo-game.gitbook.io/owo-api/welcome/configure-your-project.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.