> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/file-formats/.chromaset-razer-chroma-integration.md).

# Razer Chroma integration: .chromaset

How to edit .chromaset files

## Summary

Published: Nov 20 2024 by Seberoth\
Last documented edit: Nov 20 2024 by [mana vortex](mailto:undefined)

This page contains ínformation about `base\razer_chroma\animation_mappings.chromaset`

{% hint style="info" %}
Please note that as of now, this supported on the technical side, but has not yet been tested.
{% endhint %}

## Importing buffers

In theory, it should be possible to import regular `.chroma` files into a buffer:

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-33975a5b7b1cc2cc9dd5b65decdd3960d577c7bd%2Fchroma_load_item.png?alt=media" alt=""><figcaption></figcaption></figure>

## Editing buffers

When changing the Device type of an entry, these frames need to be adjusted:

<table><thead><tr><th width="230">Type of device</th><th>Value that needs to be used</th></tr></thead><tbody><tr><td>1D devices (1 Row)</td><td><code>FChromaSDKColorFrame1D</code></td></tr><tr><td>2D devices (> 1 Row)</td><td><code>FChromaSDKColorFrame2D</code></td></tr></tbody></table>

### Buffer values

| Device               | Rows | Colors |
| -------------------- | ---- | ------ |
| DE\_ChromaLink       | 1    | 5      |
| DE\_Headset          | 1    | 5      |
| DE\_Keyboard         | 6    | 22     |
| DE\_Keypad           | 4    | 5      |
| DE\_Mouse            | 9    | 7      |
| DE\_Mousepad         | 1    | 15     |
| DE\_KeyboardExtended | 8    | 24     |


---

# 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://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/file-formats/.chromaset-razer-chroma-integration.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.
