> For the complete documentation index, see [llms.txt](https://scripter-sm.gitbook.io/elite-zone/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scripter-sm.gitbook.io/elite-zone/getting-started.md).

# Getting started

The basics every Lua needs, whether it's a ragebot planner or a misc Lua.

Ragebot planner Luas and misc Luas are built the same way. Every Lua talks to Elite Zone through one global, `api`. It registers itself with a **name** and a **type**, then takes over a **slot**.

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-bolt">:bolt:</i></h3></td><td><strong>Quickstart</strong></td><td>Your first Lua, loaded from the menu or your executor, in four steps.</td><td><a href="/elite-zone/getting-started/quickstart.md">Quickstart</a></td></tr><tr><td><h3><i class="fa-arrows-rotate">:arrows-rotate:</i></h3></td><td><strong>Lifecycle &#x26; slots</strong></td><td>How register, override and unload work, and what gets cleaned up.</td><td><a href="/elite-zone/getting-started/lifecycle-and-slots.md">Lifecycle &amp; slots</a></td></tr></tbody></table>

## Lua types at a glance

| Type                | Slot                 | Its hooks                                                                               |
| ------------------- | -------------------- | --------------------------------------------------------------------------------------- |
| `"ragebot planner"` | Ragebot              | ragebot hooks and custom methods ([guide](/elite-zone/ragebot-planner-luas.md))         |
| `"misc"`            | Misc                 | aimbot / flickbot / silent aim / triggerbot targets ([guide](/elite-zone/misc-luas.md)) |
| `"both"`            | Ragebot **and** Misc | all of them                                                                             |

{% hint style="info" %}
Every type can **read** the whole API and build UI. The type decides which slot you sit in and which **hooks** run.
{% 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://scripter-sm.gitbook.io/elite-zone/getting-started.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.