> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_stats/configs/config.md).

# Main config

There are multiple config files that you can adjust to your liking.

You will probably only need to adjust `config.lua` in the root folder.

There are also these, but don't change them unless you know what you are doing:

* `configs/config_performance.lua` - performance settings
* `configs/config_units.lua` - units settings (km/h, mph, etc.)
* `configs/config_other.lua`

### Debug

If you see anything wrong and you would like to know more, for example to show in support ticket, you can set `Config.Debug = true` to see more debug info in client (F8) console ingame, or server console.

### Language

To change the language, go to config.lua and change value `Locale` to any of the available languages listed on the same row.

To add your own language, go to `rcore_stats\locales`, copy `en.lua` and translate the values inside.\
Name the new file to your country code (e.g. `fr.lua` for French), save it and change it in config.\
Don't forget to change the `Locale['en']` to your country code in the new file. (e.g. `Locale['fr']` for French)

### Commands

There is only one command in the script:

* `/stats` - Open stats panel

You can change this command as `Config.Commands.OPEN_UI` in `config.lua`

## ❗ DANGER ZONE

Do not change anything in the danger zone unless you know what you are doing.

In here you will be able to force set framework and database stuff. This is automatically done for you if you do not touch this part.


---

# 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://documentation.rcore.cz/paid-resources/rcore_stats/configs/config.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.