> 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/32-bit-support.md).

# 32-bit support

## **Expanded Value Range**

***

32-bit scripts increase numeric range drastically compared to 16-bit:

* 16-bit: –32,768 to +32,767
* **32-bit: –2,147,483,648 to +2,147,483,647**

This allows more complex calculations with far greater precision.

## **Increased Memory Space**

***

32-bit scripting supports a much larger addressable memory space, enabling more data and more sophisticated logic to be used inside GPC scripts.

**New Functions Added**

***

Three new GPC functions were introduced to leverage 32-bit capability:

* `get_ipolar()` — Retrieves analog stick input *before modification*
* `get_polar()` — Retrieves current stick angle or radius
* `get_info()` — Retrieves the active MK (Mouse/Keyboard) profile state

These functions provide more raw input data and programmatic control inside scripts.

## **Use of `int32` Variables**

***

A new 32-bit variable type (`int32`) allows larger values to be stored directly, beyond the 16-bit limit. This is especially useful for scales, accumulators, or data structures that exceed 32,767.

## **Extended Trace Support**

***

Three VM trace debug fields are now 32-bit capable (trace 1–3).\
This enables developers to observe and debug larger numeric values in real time via the Device Monitor.

## **Larger SPVAR Values**

***

32-bit SPVAR (script persistent variables) can hold much greater values, allowing:

* Better state tracking
* Complex accumulations without overflow
* More efficient bit packing
* Larger data storage inside variables

Compared to 16-bit SPVAR limits, this significantly expands what state can be tracked.


---

# 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:

```
GET https://guide.cronuszen.com/gpcscripting/gpc-script-guide/32-bit-support.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.