> For the complete documentation index, see [llms.txt](https://guide.cronuszen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.cronuszen.com/gpcscripting/gpc-script-guide/start-here/the-smallest-useful-script.md).

# The smallest useful script

Every GPC script needs `main` logic. Zen runs it repeatedly from top to bottom, once per VM cycle.

{% code title="smallest-useful-script.gpc" lineNumbers="true" %}

```cpp
main {
    if(get_val(PS5_L2)) {
        set_val(PS5_R1, 100);
    }
}
```

{% endcode %}

***

### What each part does

| Function               | Purpose                                           |
| ---------------------- | ------------------------------------------------- |
| `get_val(PS5_L2)`      | Reads the current L2 value.                       |
| `set_val(PS5_R1, 100)` | Writes a fully pressed R1 to the outgoing report. |

***

### How it runs

{% stepper %}
{% step %}

#### Read

`get_val(PS5_L2)` reads the current L2 value.
{% endstep %}

{% step %}

#### Evaluate

Any nonzero value is true in an `if` condition.
{% endstep %}

{% step %}

#### Write

While L2 is active, `set_val(PS5_R1, 100)` makes the outgoing R1 value fully pressed.
{% endstep %}

{% step %}

#### Send

At the end of `main`, Zen finalizes and sends the output report.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
This does not create a permanent state. The condition is evaluated again on the next VM cycle.
{% endhint %}

<details>

<summary>Can I use more than one <code>main</code> section?</summary>

Zen Studio Live accepts more than one `main` section and merges them into one combined section. Use a single `main` section in new scripts unless splitting generated source is genuinely useful.

</details>


---

# 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://guide.cronuszen.com/gpcscripting/gpc-script-guide/start-here/the-smallest-useful-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.