> For the complete documentation index, see [llms.txt](https://docs.jgscripts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jgscripts.com/pro-scoreboard/config-and-customisation.md).

# Config & Customisation

{% hint style="info" %}
You can configure the script inside `config.lua`. Most of the config options are self-explanatory, but this guide should explain most options anyway.
{% endhint %}

### Highlighted Jobs

* The color of each highlighted job must be a hex code
* `countOnDutyOnly` will display the total players in that whitelisted job that are currently set as on duty (:warning: QBCore only)
* Icons are from <https://icons.getbootstrap.com/> - paste the name of the icon (without the `bi-` prefix) to change it
* `ShowAdminBadges` will either hide or show orange stars next to players who have admin or god status
* `AdminBadgeIcon` uses the same bootstrap icons as above
* You can set multiple jobs in one highlighted job counter: for example, if you have multiple mechanic jobs you can do: `job = {"mechanic", "mechanic2"}`

### Name & Logo

* The name can be changed by customising `Config.ServerName`.
* You can change the icon displayed in the top left by replacing the png at `/html/my-logo.png`.

{% hint style="danger" %}
The image that you change to **MUST** be a `.png` and it must be a square aspect ratio.
{% endhint %}

### Key Bind

* `Config.KeyBind` is the default key bind for all players. Individual players can change it to their liking by going into `Settings > Key Bindings > FiveM > (jg-scoreboard) Open Scoreboard` in-game.


---

# 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.jgscripts.com/pro-scoreboard/config-and-customisation.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.