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

# Installing Your Script

Getting your loader and running it in-game.

There is nothing to install in the traditional sense. Your script is delivered as a **loader** — a small file you run inside the game with your executor. The loader handles updates automatically, so you never re-download after a script update.

## Getting your loader

You get the loader from the place you bought:

* **Dashboard** — your download link lives on your account after purchase.
* **Discord buyer panel** — click **Get Script** in the panel to receive the loader file.

The loader is a `.lua` file named after your script.

## Running it

1. Launch Roblox and join the game.
2. Open your executor and attach to the game.
3. Run the loader file (or paste its contents into the executor and execute).
4. The script loads and its menu appears.

## After a game update

Do nothing. Updates ship through the loader. If a script stops working after a game update, re-run the loader to pull the latest build.


---

# 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.getcelsius.net/getting-started/installing-your-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.