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

# Installation

## 1. The usual steps

{% stepper %}
{% step %}
Install the dependencies listed on the product's Requirements page (usually `oxmysql`and`oxlib` ).
{% endstep %}

{% step %}
Drop the resource folder into your `resources` directory.

{% endstep %}

{% step %}
Add it to `server.cfg` after you framework and its dependencies.
{% endstep %}

{% step %}
Import the SQL only if the product guide asks for it - most of our resources create their own tables on first start.
{% endstep %}

{% step %}
Register the items listed in the guide if the product uses inventory items.
{% endstep %}

{% step %}
Open config.lua set your framework - inventory if auto-detection is not enough, and restart the server.
{% endstep %}
{% endstepper %}

## 3. server.cfg

<pre class="language-yaml"><code class="lang-yaml"><strong># 1 database + libraries
</strong><strong>ensure oxmysql
</strong><strong>ensure ox_lib
</strong><strong># 2. your framework and its core resources
</strong><strong>ensure es_extended    # or qb-core \ qbx_core
</strong><strong>ensure ox_invetory    # or qb-inventory
</strong><strong>ensure ox_target      # optional, when the product uses a target
</strong><strong># 3. star resources - always after everything
</strong><strong>ensure star-script1
</strong><strong>ensure star-script2
</strong></code></pre>


---

# 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.starscripts.store/getting-started/installation.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.