> 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/troubleshooting/optimization-order.md).

# Optimization order

### 1. Establish measurements

Record bytecode size, variable use, stack warning/result, VM load, and the behavior test matrix.

### 2. Remove unused const data

Strings, images, and tables consume bytes even if no live code references them.

### 3. Narrow const widths

Apply compiler suggestions when signedness/range remain correct.

### 4. Cache and dirty-gate

Stop full scans and feedback rendering every cycle.

### 5. Consolidate duplicate executable logic

Use a function when repeated body size is larger than call overhead and the boundary improves clarity.

### 6. Flatten stack-heavy expressions

```cpp
temp1 = a * b;
temp2 = c * d;
result = temp1 + temp2;
```

### 7. Recompile and regression-test

After every meaningful reduction, retest input layers, output order, persistence, menus/gates, and boundary values.


---

# 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/troubleshooting/optimization-order.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.
