> For the complete documentation index, see [llms.txt](https://docs.devhub.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devhub.gg/id-card-and-license/configuration/sh.lang.lua.md).

# sh.lang.lua

All player-facing text lives in `Config.Lang` as key → value pairs. Translate the system by editing only the **values** (right side).

## <mark style="color:yellow;">**Lang**</mark>

```lua
Config.Lang = {
    ['active'] = "Active",
    ['expired'] = "Expired",
    ["license_issued"] = "License Issued",
    ["show_license_cooldown"] = "Please wait %{seconds}s before showing another license.",
    ["player_has_no_licenses"] = "%{player} has no licenses",
    -- ... hundreds more keys (NPC dialog, notifications, and Vue UI labels)
}
```

* **Description**: A single table holding every string the system displays — license statuses, notifications, NPC dialog, fake ID mission text, crafting station prompts, server messages, and all Vue/NUI labels (keys prefixed with `vue_`).

### Rules

* **Do not change the keys** (left side) — they are referenced from code.
* **Only change the values** (right side) to translate or reword text.
* **Keep the `%{value}` placeholders** intact. They are replaced at runtime with dynamic data.
  * **Example**: In `["player_has_no_licenses"] = "%{player} has no licenses"`, `%{player}` is replaced with the target player's name.
  * **Example**: In `["show_license_cooldown"] = "Please wait %{seconds}s before showing another license."`, `%{seconds}` is replaced with the remaining cooldown.

{% hint style="info" %}
Keys prefixed with `vue_` are consumed by the NUI (Vue) interface — the MDT, card holder, license creator, fake ID screen, and scan terminal. Translate them the same way as the in-game strings.
{% endhint %}


---

# 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://docs.devhub.gg/id-card-and-license/configuration/sh.lang.lua.md?ask=<question>&goal=<endgoal>
```

`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.