> For the complete documentation index, see [llms.txt](https://docs.gamesense.biz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gamesense.biz/pt-br/getting-started/first-script.md).

# Primeiro Script

Controles de menu e eventos de alteração.

O exemplo abaixo cria uma caixa de seleção que controla a visibilidade de uma configuração adicional.

```lua
local advanced = menu.checkbox("Advanced settings", false)
local amount = menu.slider_int("Amount", 0, 100, 50)

amount:set_visible(advanced:get())

advanced:on_change(function()
    amount:set_visible(advanced:get())
end)
```

## Funcionamento

| Expressão              | Descrição                                       |
| ---------------------- | ----------------------------------------------- |
| `menu.checkbox(...)`   | Cria uma caixa de seleção                       |
| `menu.slider_int(...)` | Cria um controle deslizante de números inteiros |
| `:get()`               | Retorna o valor atual do controle               |
| `:on_change(callback)` | Registra uma função para mudanças de valor      |
| `:set_visible(state)`  | Exibe ou oculta um controle                     |

Quando **Advanced settings** está ativado, o controle **Amount** aparece. Quando está desativado, ele fica oculto.

## Tratamento de eventos

A função `register_callback` executa código durante atualizações do jogo ou renderização de quadros. Consulte [Callbacks](/pt-br/api-reference/callbacks.md).


---

# 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.gamesense.biz/pt-br/getting-started/first-script.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.