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

# License

License, refund and redistribution terms for Waro Studios scripts.

{% hint style="danger" %}
**Owner to fill in.** This page is a placeholder. The terms below have not been written yet and nothing on this page is a legal agreement. Do not publish this page until the owner has written and approved the text.
{% endhint %}

## License summary

{% hint style="warning" %}
Owner to fill in: what a purchase allows (for example how many servers, and whether the license is tied to the Cfx.re account).
{% endhint %}

## Refunds

{% hint style="warning" %}
Owner to fill in: the refund policy for digital goods bought on Tebex.
{% endhint %}

## Redistribution

{% hint style="warning" %}
Owner to fill in: what buyers may and may not share, resell or re-upload, including edited versions.
{% 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.warostudios.com/help/licence.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.