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

# How to Install a Vehicle

## Step 1 — Download your purchase

Download the vehicle from the download location provided with your Modster Customs purchase.

## Step 2 — Extract the files

Extract the ZIP/RAR package on your computer.

Do not remove files from the package unless instructed.

## Step 3 — Upload the resource

Upload the vehicle resource to your FiveM server's `resources` folder.

Example:

```
resources/
└── [vehicles]/
    └── modster_vehicle/
```

## Step 4 — Start the resource

Add the resource to your `server.cfg`:

```
ensure modster_vehicle
```

Replace the example resource name with the actual folder name.

## Step 5 — Restart

Restart the resource or your server.

## Step 6 — Spawn the vehicle

Use the correct vehicle spawn name supplied with the product.

## Important

If the vehicle does not work after installation, **do not immediately modify the files**. Check the Common Issues section first.


---

# 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://modster-customs.gitbook.io/modster-customs-docs/getting-started/02-how-to-install.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.