> 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/data-and-persistence/strings-images-and-adt-records.md).

# Strings, images, and ADT records

### One string and a string array

```cpp
const string STATUS = "READY";
const string MODE_LABELS[] = { "OFF", "STANDARD", "ALTERNATE" };
```

***

### Image record

```cpp
const image ICON = {
    8, 8,
    0xFF, 0x81, 0x81, 0x81, 0x81, 0x81, 0x81, 0xFF
};
```

For width `w` and height `h`, supply exactly `ceil(w*h/8)` pixel bytes after the two dimensions.

***

### Adaptive-trigger record

The 11 positions are `MODE`, `START`, `FORCE1`, `FORCE2`, `STRENGTH_LOW`, `STRENGTH_MID`, `STRENGTH_HIGH`, `UNK1`, `UNK2`, `FREQ`, and `UNK3`, in that order.

{% code title="adt-record.gpc" %}

```cpp
const ps5adt ADT_PROFILE = {
    PS5_ADT_CR, // 0: mode
    0,          // 1: start
    128,        // 2: force 1
    128,        // 3: force 2
    64,         // 4: low strength
    128,        // 5: mid strength
    192,        // 6: high strength
    0,          // 7: unknown/reserved 1
    0,          // 8: unknown/reserved 2
    100,        // 9: frequency
    0           // 10: unknown/reserved 3
};

main {
    adt_setx(PS5_R2, addr(ADT_PROFILE));
}
```

{% endcode %}

A `ps5adt` record is exactly 11 bytes. Preserve the unknown/reserved fields from a known-good record. `addr` is a compiler address form, not a general pointer.


---

# 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/data-and-persistence/strings-images-and-adt-records.md?ask=<question>&goal=<user_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.
