> 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/common-issues/04-vehicle-not-spawn.md).

# Vehicle Does Not Spawn

If your vehicle does not spawn, work through these checks.

## 1. Confirm the resource is installed

Make sure the resource is inside your server's `resources` directory.

## 2. Confirm the resource is started

Check your `server.cfg`:

```
ensure resource_name
```

Make sure `resource_name` matches the resource folder.

## 3. Check the spawn name

Make sure you are using the correct vehicle spawn name.

Do not assume the resource folder name and spawn name are the same.

## 4. Check the server console

Look for errors when the resource starts.

Pay attention to:

* Missing files
* Invalid manifest
* Missing dependencies
* Resource startup errors

## 5. Restart the resource

```
restart resource_name
```

Then spawn a fresh vehicle.

## Still not working?

Send support:

* Vehicle name
* Spawn name
* Screenshot/video
* Server console error
* Framework
* Relevant vehicle scripts


---

# 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/common-issues/04-vehicle-not-spawn.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.