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