> For the complete documentation index, see [llms.txt](https://apex-studio.gitbook.io/dash-core-endless-runner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apex-studio.gitbook.io/dash-core-endless-runner/01_quickstart_guide/troubleshooting-common-onboarding-issues.md).

# Troubleshooting Common Onboarding Issues

#### Chapter 4: Troubleshooting Common Onboarding Issues

The automated architecture of Dash Core significantly reduces common Unity errors, but here are quick solutions to potential onboarding roadblocks:

* Issue: The Setup Hub refuses to build the Player Prefab.
* *Solution:* Check the Hub's Validation messages. Ensure your 3D model's Rig is set to Humanoid in the Import Settings, and that it has an Animator component attached.
* Issue: Missing References or "Null Reference Exception" on start.
* *Solution:* Because Dash Core uses EditorPrefs to cache GUIDs and dynamically loads assets, ensure you haven't moved the core ScriptableObjects out of their default Resources or Data folders. If you did, simply reopen the Command Center to force a re-scan of the Asset Database.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://apex-studio.gitbook.io/dash-core-endless-runner/01_quickstart_guide/troubleshooting-common-onboarding-issues.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.