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

# Compiling Errors

In the recently released Zen Studio Live (ZSL), the vast majority of scripts should work 1:1 as-is, provided they were actually functional in the previous compiler.

The ZSL compiler fully checks for errors ahead of time. If you are experiencing errors compiling, it should be noted that the ZSL compiler is stricter, but it mainly boils down to the following that you will need to check:

* All keywords are now fully reserved; you **cannot** use them for a function name or a variable/parameter/constant, etc.
* Subtle changes, such as the order of "++x" or "x++", now matter — previously, both were treated the same as "++x".

***

**Dead Code Is Now Checked Too**

This isn't a strictness change like the two points above — it's a change in how the compiler behaves. Previously, if you had a function that was never called or referenced anywhere in your script, the old compiler would ignore it completely, even if it contained errors. The ZSL compiler now checks everything ahead of time, including unused code.

If you're getting compile errors in a function you never touched, this is likely why. The fix is simple: use the **Prune** function, which strips away dead functions, combos, and const arrays before compiling — so unused code never gets checked in the first place.


---

# 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/compilingerrors.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.