> 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/reference/constants.md).

# Constants

This public appendix contains **909 Zen-supported compiler constants** across **29 non-empty public categories** from the current Live compiler definition. Names are case-sensitive. The remaining inventory consists of 136 owner-excluded constants, 16 older-device selectors, and three validation-only names; none are presented as supported Zen constants.

Every public category is nested beneath this index in the guide navigation. Use the table or the sidebar to open a native GitBook reference page.

<table data-search="false"><thead><tr><th>Category</th><th align="right">Count</th><th>Reference</th></tr></thead><tbody><tr><td><code>ANALOGS</code></td><td align="right">15</td><td>Polar and extended analog selectors</td></tr><tr><td><code>ASCII</code></td><td align="right">126</td><td>ASCII and OLED glyph codes</td></tr><tr><td><code>BITMASKS</code></td><td align="right">32</td><td>32-bit masks</td></tr><tr><td><code>DF</code></td><td align="right">20</td><td>Driving Force identifiers</td></tr><tr><td><code>DFGT</code></td><td align="right">25</td><td>Driving Force GT identifiers</td></tr><tr><td><code>DFPRO</code></td><td align="right">20</td><td>Driving Force Pro identifiers</td></tr><tr><td><code>G25</code></td><td align="right">22</td><td>Logitech G25 identifiers</td></tr><tr><td><code>G27</code></td><td align="right">26</td><td>Logitech G27 identifiers</td></tr><tr><td><code>G29</code></td><td align="right">27</td><td>Logitech G29 identifiers</td></tr><tr><td><code>KEYBOARD</code></td><td align="right">178</td><td>Keyboard usage constants</td></tr><tr><td><code>LED</code></td><td align="right">48</td><td>LED constants</td></tr><tr><td><code>MISC</code></td><td align="right">16</td><td>Miscellaneous constants</td></tr><tr><td><code>MODIFIERS</code></td><td align="right">8</td><td>Keyboard modifier masks</td></tr><tr><td><code>OLED</code></td><td align="right">23</td><td>OLED constants</td></tr><tr><td><code>PIO</code></td><td align="right">9</td><td>Protocol identifiers</td></tr><tr><td><code>PRODUCTS</code></td><td align="right">7</td><td>Product identifiers</td></tr><tr><td><code>PS3</code></td><td align="right">25</td><td>PlayStation 3 identifiers</td></tr><tr><td><code>PS4</code></td><td align="right">34</td><td>PlayStation 4 identifiers</td></tr><tr><td><code>PS4_TOUCH</code></td><td align="right">6</td><td>DualShock 4 touch selectors</td></tr><tr><td><code>PS5</code></td><td align="right">35</td><td>PlayStation 5 identifiers</td></tr><tr><td><code>PS5_ADT</code></td><td align="right">11</td><td>Adaptive-trigger field selectors</td></tr><tr><td><code>PS5_ADT_MODE</code></td><td align="right">10</td><td>Adaptive-trigger mode values</td></tr><tr><td><code>SPVAR</code></td><td align="right">64</td><td>SPVAR selectors</td></tr><tr><td><code>RUMBLE</code></td><td align="right">6</td><td>Rumble and haptic identifiers</td></tr><tr><td><code>SWITCH</code></td><td align="right">28</td><td>Nintendo Switch identifiers</td></tr><tr><td><code>TRACE</code></td><td align="right">6</td><td>Trace identifiers</td></tr><tr><td><code>WII</code></td><td align="right">33</td><td>Nintendo Wii identifiers</td></tr><tr><td><code>XB1</code></td><td align="right">28</td><td>Xbox One/Series identifiers</td></tr><tr><td><code>XB360</code></td><td align="right">21</td><td>Xbox 360 identifiers</td></tr></tbody></table>

### Identifier range reminder

Several platforms intentionally use the same numeric report slots for equivalent controls. Write the named constant for the platform and meaning intended by the script. Touch, motion, mute, paddles, and adaptive-trigger identifiers are platform-specific.


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/reference/constants.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.