> 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/advanced-architecture/bytecode-aware-optimization.md).

# Bytecode-aware optimization

Zen Studio Live limits final bytecode to 65,519 bytes.

1. Compile and record exact size/load first.
2. Remove unused const strings/images/tables; they still occupy data bytes.
3. Narrow const element types when safe.
4. Factor genuinely repeated executable blocks into functions.
5. Simplify duplicate menu rendering/lookup logic.
6. Keep stack depth in view while flattening giant expressions.
7. Recompile and regression-test after each reduction.

Unused user functions and combos can be removed by optimization, but unused const data remains 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 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/advanced-architecture/bytecode-aware-optimization.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.