> 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/manuals/app/appcontrols.md).
# App Controls
Common setting types & controls.
***
Various types of settings that you will encounter across the **STRIKEPACK CENTRAL**™ app:
{% tabs %}
{% tab title="Option Setting" %}
The **Option** setting can be changed quickly by 
tapping its 
arrow
icons. You can bring up its **Option Selector** by 
holding your finger on the setting until it fully traces itself. This will present you with a sub-menu of its options for you to swipe through & select from:
{% endtab %}
{% endtabs %}
{% tabs %}
{% tab title="Slider Setting" %}
The **Slider** setting can be precisely adjusted by tapping its 
minus or 
plus icons. It can be adjusted more quickly by holding & dragging its slider thumb:
{% endtab %}
{% endtabs %}
{% tabs %}
{% tab title="Toggle Setting" %}
The **Toggle** setting can be tapped to switch it 
**ON** / 
**OFF**.
{% endtab %}
{% endtabs %}
{% tabs %}
{% tab title="Controller Shortcuts" %}
Dashboard settings sometimes have **Controller Shortcuts** that depending on the GAMEPACK, may become visible when the 
***ACTIVATOR*** controller button is ***HELD**.*
{% endtab %}
{% endtabs %}
{% hint style="warning" %} Tap the 
**Information** icon on settings to learn more about them.
{% endhint %}
---
# 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/manuals/app/appcontrols.md?ask=&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.
