> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/inputs-and-outputs/control-value-ranges.md).

# Control value ranges

Zen exposes normalized integer values rather than the controller's hardware-native counts:

| Standard report control  | Typical range | Meaning                                                             |
| ------------------------ | ------------: | ------------------------------------------------------------------- |
| Digital button           |  `0` or `100` | Released or fully pressed                                           |
| Analog trigger           |      `0..100` | Released through fully pressed                                      |
| Stick X/Y axis           |   `-100..100` | Center is `0`; opposite directions use negative and positive values |
| Touch-present identifier |  `0` or `100` | No finger or finger present                                         |
| Touch X/Y identifier     |   `-100..100` | Normalized position across the touch surface                        |

Not every function uses the standard report scale. Keep function-specific units with the feature that consumes them:

* Polar sticks: angle `0..359`, `set_polar` radius `0..32767`, and `set_polar2` radius `0..15000`.
* Touch and Wii IR: presence selectors and normalized X/Y positions.
* Rumble and haptics: actuator strength `0..100`.
* PS5 adaptive triggers: 11 positional bytes, each `0..255`.

The compiler enforces a built-in's constant argument range where possible. Dynamic calculations still need validation and clamping before they reach the function.


---

# 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.cronuszen.com/gpcscripting/gpc-script-guide/inputs-and-outputs/control-value-ranges.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.