> 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/modding-guides/everything-else/lockeys-values-and-formatting.md). # LocKeys: Values and formatting ## Summary Created: May 24 2026 by [Leefekyn](mailto:undefined)\ Last documented edit: May 24 2026 by [Leefekyn](mailto:undefined) This page will show you how to use values (and colours) in translation entries ## LocKey interpolation at runtime LocKey files support the use of certain variables (i.e. {float\_#} and {stat\_#}), and this can be seen in many descriptions in the games files. The LocKey file also has the ability to set colors, text style, and text size using Rich Values. The Gorilla Arms Cyberware uses a couple of these to change text color and display stats: ```html Gorilla Arms are lightweight, efficient and hard-hitting arm replacement cyberware.\n\n+{stat_0} to Body ``` Defining Floats and Stats: 
UIData:
  localizedDescription: #YOUR LOCKEY FILE 
  floatValues: #these are defined values, usually used to show effects 
    - 1 
    - 2 
    - 3 
  stats: #these are the variables used by the game, usually to show the result of effects 
    - BaseStats.AttunementHelper #{stat_0} 
    - BaseStats.AttunementHelper2 #{stat_1} 
    - BaseStats.AttunementHelper3 #{stat_2}
You can also use hex format colors instead of the predefined table of colors in certain locations by using: {% code overflow="wrap" %} ```html YOUR TEXT HERE ``` {% endcode %} You can combine a couple of these effects, and in certain text locations, change the color of text dynamically based on a stat value. This is done by defining a stat variable (i.e, {stat\_0}), then using that stat variable in the hex code for the color. The end result should look something like this: {% code overflow="wrap" %} ```html YOUR TEXT HERE ``` {% endcode %} This allows a stat to replace the first few digits of the hex code, and display a different color than originally shown. From my testing these variables are a little more strict in how they are put in, and have only had success when defining any changes to the variable at the item level via stat modifiers (either constant or combined). There are also a few irregularities when defining and using this system. In this example the first 2 digits from the hex are absent and being replaced with the given stat: \#\_ \_9999 -2 Digit variables here work as expected here. -3 Digit variables here push out the final 9 from the hex code, and use the whole 3 digit variable at the start. -4 Digits and beyond only use the last 2 digits. -Decimals also work, and I believe they always use the last 2 digits in the variable but this needs more testing. Seems like they work up to 3 decimal places, and it selects the last 2 in this instance. --- # 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://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/everything-else/lockeys-values-and-formatting.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.