> 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/01-getting-started.md).

# Getting Started

## What is included with my Modster Customs purchase?

The exact contents depend on the product you purchased. Check the product description and download package for the included files and installation instructions.

## What do I need before installing a vehicle?

You should have:

* A working FiveM server
* Access to your server's resources directory
* Permission to edit your `server.cfg`
* The vehicle files from your purchase
* Any dependencies specifically listed by the product

## Should I edit the vehicle files?

Normally, no. Install the resource as provided unless the product instructions tell you to make a specific change.

## Where should I install the resource?

Place the vehicle resource inside your server's `resources` directory.

Example:

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

The actual resource name will depend on the product.

## Do I need to restart my whole server?

Usually you can restart the individual resource after making a change:

```
restart resource_name
```

Replace `resource_name` with the actual resource name.


---

# 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/01-getting-started.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.