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

# Starting resources

Set up the folder structure, resource name, and startup order.

## Find the actual resource folder

A streaming package might look like this:

```
resources/
└── [studioworks]/
    └── studioworks_example/
        ├── fxmanifest.lua
        ├── stream/
        └── other included files
```

`studioworks_example` is a placeholder. Use the real name from your package. Products can have different subfolders. Keep all included files and only rename the resource if its instructions allow it.

## Add it to the server configuration

```cfg
# Example: replace this with the actual resource folder name
ensure studioworks_example
```

Start required libraries, frameworks, and database adapters before the script that depends on them. Install only the dependencies named by your product. A model resource does not automatically require a framework.

If you start an entire category with `ensure [studioworks]`, use individual resource entries during troubleshooting on your test server. This helps identify which resource actually fails.

## Server console commands

| Command                 | Effect                                                    |
| ----------------------- | --------------------------------------------------------- |
| `refresh`               | Rescans resources and reads their manifests               |
| `ensure resource_name`  | Starts a stopped resource or restarts one that is running |
| `restart resource_name` | Restarts a running resource                               |
| `stop resource_name`    | Stops the named resource                                  |

{% hint style="warning" %}
Even `ensure` can restart a running resource. Plan tests around active players. Changes to streamed models or metadata may also require reconnecting the client or a planned full server restart.
{% endhint %}

## Common mistakes

* The ZIP was copied without being extracted.
* The manifest is one folder level too deep.
* The `ensure` entry does not match the folder name.
* Letter case differs on a Linux server.
* Duplicate copies of the resource exist in different folders.
* The server loads a different configuration file than expected.

Technical reference: [Cfx.re resource commands](https://docs.fivem.net/docs/server-manual/server-commands/#resource-commands).

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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://studioworks.gitbook.io/studioworks-docs/installation/starting-resources.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.