> For the complete documentation index, see [llms.txt](https://docs.perfectcs2.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perfectcs2.com/documentacao/api/icons.md).

# icons

Ícones do Font Awesome.

A tabela `icons` tem os **1.402 ícones do Font Awesome 6** (estilo *solid*), os mesmos do menu. Cada ícone é um texto: desenhe com [`render.text`](/documentacao/api/render.md) usando `font = "icons"`.

```lua
callbacks.add("draw", function()
    render.text(20, 20, icons.crosshairs, color(255, 140, 40), { font = "icons", size = 18 })
    render.text(46, 21, "Crosshair on", color(255, 255, 255), { size = 15 })
end)
```

## Nomes

O nome é o do site [fontawesome.com/icons](https://fontawesome.com/icons?o=r\&s=solid), com `_` no lugar de `-`:

| No site         | Em Lua                |
| --------------- | --------------------- |
| `crosshairs`    | `icons.crosshairs`    |
| `heart-pulse`   | `icons.heart_pulse`   |
| `bomb`          | `icons.bomb`          |
| `eye`           | `icons.eye`           |
| `skull`         | `icons.skull`         |
| `gun`           | `icons.gun`           |
| `shield-halved` | `icons.shield_halved` |
| `stopwatch`     | `icons.stopwatch`     |

Ícones com nome de número são acessados com colchetes: `icons["0"]`, `icons["1"]`. Um nome que não existe devolve `nil`.

{% hint style="info" %}
Ícones ocupam o espaço de um caractere. Para centralizar um ícone num ponto, use `align = "center"` e meça a altura com `render.measure_text(icons.eye, { font = "icons", size = 18 })`.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perfectcs2.com/documentacao/api/icons.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.