> 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/reference/additional-built-ins.md). # Additional built-ins These compiler-recognized functions expand the coverage available in older source pages. Each entry below is documented with its current Zen Studio Live behavior and usage context. The three category pages are nested beneath this page in the guide navigation, so readers can browse the complete set without leaving GitBook. * Bit and math functions — 13 functions * Device, timing, remapper, and BVAR functions — 12 functions * OLED display functions — 9 functions Together with the [main built-in reference](/gpcscripting/gpc-script-guide/reference/core-built-ins.md), these pages cover the built-ins in scope for this guide. For exact counts and what falls outside that scope, see Scope and limits. All ranges on these pages use the current Zen Studio Live 32-bit target. Compile and device-test behavior on the exact Live build, especially device remapping, EEPROM writes, BVAR persistence, OLED redraw timing, and VM timing changes. --- # 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/reference/additional-built-ins.md?ask=&goal= ``` `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.