> 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/vehicles/crash-spawn-impact.md).

# Crash when spawning or driving

A client or server crashes on spawn, entry, driving, or collision.

{% hint style="info" icon="bolt" %}
**Quick check:** Save the crash text and identify whether one client, all players, or the server process is affected.
{% endhint %}

## Fix it

1. Repeat the exact action with the untouched package on a test server.
2. Record extras, tuning state, speed and collision when relevant.
3. Test without competing vehicle packages and compare another client.

## Check the result

Repeat the original action under the same conditions. A crash that remains in an isolated test needs a support ticket.

## Still happening?

[More detailed checks](/studioworks-docs/troubleshooting/crashes-performance.md) · [Prepare a support ticket](/studioworks-docs/support/preparing-a-ticket.md)

Include the product version, first error, and the steps you tried. Keep secrets out of logs and screenshots.


---

# 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/vehicles/crash-spawn-impact.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.