> 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.md). # GPC Script Guide Your complete companion for writing scripts on the Cronus Zen.

No matter your experience level, this guide takes you from your first script to advanced techniques. Everything here is written specifically for **Zen Studio Live** and the current **32-bit Zen target**. *** ### Where do you want to go?

		Cover image
Start Coding	A guided first-script path. Compile, program, and test your Zen safely — step by step.	card-start-here.svg
Learn GPC	Variables, conditions, functions, arrays, combos, input layers, and output order — the full toolkit.	card-learn-gpc.svg
Examples and Recipes	Real, working scripts from beginner-friendly to expert-level. Copy, modify, learn.	card-device-features.svg
Reference	Every built-in, every constant, every diagnostic. Debugging workflows included.	card-reference.svg
Troubleshooting	Compiler errors, warnings, tracing, and bisection. Find the real cause, not the first symptom.	card-troubleshooting (1).svg

{% hint style="info" %} **Never coded before?** Start with [What is GPC?](/gpcscripting/gpc-script-guide/what-is-gpc.md) to understand the language, then [Start Here](/gpcscripting/gpc-script-guide/start-here.md) to write your first script. {% endhint %} --- # 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.md?ask=&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.