> For the complete documentation index, see [llms.txt](https://guide.strikepack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/tournament-studio-guide.md).

# Tournament Studio Guide

Guide Coming Soon. In the meantime take a look. Tournament Studio is very simple to use and almost needs no explanation. It *does not* contain any macros with the exception of some accessibility features like Hair Triggers, Adaptive Trigger Stops, Block Rumble, and even Sticky Buttons which can turn any controller button into a toggle button.

Like other GAMEPACKS and unlike the default Tournament Mode, you can make multiple profiles for different Action Button (Paddle) mapping configurations for your favorite games.

As part of the new Studio line of GAMEPACKS, you can optionally engage with the new and improved Stick and Trigger Tuning (e.g. drift correction, responsive curves, sensitivity, and more). As with other settings, this is per profile.

As a cool feature, exclusive to Tournament Studio, you can adjust the brightness and colors of the STRIKEPACK HORIZON front-LEDS, either together or independently.

**NOTE:** The LED sliders *do not* accurately represent any specific RGB values so you will have to play around to get it right, and the Gearhead Eyes will always **pulse white** in this particular GAMEPACK, so that others can see you are *not* currently using macros.

More unique features will likely come to Tournament Studio in the future!


---

# 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://guide.strikepack.com/horizon/strikepack-horizon-app-guide/tournament-studio-guide.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.
