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

# Minecraft crashes when Cesium loads in

Most load crashes are a version mismatch or a conflict with something else in the game.

{% hint style="info" %}
Most load crashes are a version mismatch or a conflict with something else in the game.
{% endhint %}

## Check the version

Loading into any other version can crash the game. See [Supported Minecraft versions and launchers](/cesium-docs/support/supported-versions.md).

## Check for conflicts

* Other clients or injectors: only one client should be loaded into the game at a time.
* Overlays: close Discord overlay, GPU recording overlays, and similar, then try again.

## Update

Open the launcher. It fetches the current client before it starts. If you have been offline, let it update, then load again.

## Collect the crash report

Minecraft writes a crash report to the crash-reports folder inside your Minecraft directory. Take the newest file. Also note your client build and launcher version from the launcher's Session info panel.

## Report it

Post the crash report, your Minecraft version, the Minecraft launcher you used, and the Cesium build in [Discord](https://discord.gg/3QBFFwbbH).


---

# 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://cesium.gitbook.io/cesium-docs/support/crash-on-load.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.