> 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/scope-and-limits.md).

# Scope and limits

This edition targets Zen Studio Live and the current 32-bit Zen compiler surface.

Use this page as a coverage audit and a quick target-limit reference. It explains how much of the compiler inventory is documented in this guide; it is not an API or constant lookup page.

### Guide coverage

The table compares the reader-facing guide with the complete compiler inventory:

* **Covered in this edition**: documented for readers in this guide.
* **Other inventory entries**: target-specific, legacy, validation-only, or non-reader-facing entries outside this edition's scope.
* **Compiler inventory total**: the sum of the preceding two count columns.

| Inventory category             | Covered in this edition | Other inventory entries | Compiler inventory total |
| ------------------------------ | ----------------------: | ----------------------: | -----------------------: |
| Compiler-recognized built-ins  |                      90 |                      12 |                      102 |
| Compiler constants             |                     909 |                     152 |                    1,061 |
| Validation-only constant names |                       0 |                       3 |                        3 |
| Compiler diagnostic codes      |                     166 |                       0 |                      166 |

***

### Current target limits

| Resource               |             Limit |
| ---------------------- | ----------------: |
| Runtime integer        |     signed 32-bit |
| Runtime variable slots |             1,020 |
| Stack slots            |             1,024 |
| Maximum bytecode       |      65,519 bytes |
| BVAR indexes           |         `0..1023` |
| OLED                   | `128 x 64` pixels |

The additional inventory counts keep the audit totals complete while the guide stays focused on current, reader-facing Zen Studio Live material.


---

# 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/reference/scope-and-limits.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.