> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-college/troubleshooting.md).

# Troubleshooting

**Daddy College does not start**

Start `ox_lib`, `oxmysql` and `daddy_lib` before `daddy_college`, and keep the folder names as they came. `daddy status` in the server console shows each Daddy Studio resource and its state.

**Using an item does nothing**

Run `daddy check` in the server console: it shows the inventory it found and every item missing from it. Add the items from `install/generated/items/<language>/`.

**Attendance papers, exam papers, notebooks or hall passes do not work**

They carry data on the item, so they need an inventory with item metadata. ESX's own inventory has none; use ox\_inventory, or set `Config.ClassPoints.RedeemMode = 'direct'` for class points.

**A place does not show**

Check in `/collegeadmin` that it is active and that its module is on in `Config.Modules`.

**No school roles**

The jobs must exist in your framework with the names in `Config.Roles`. The Setup page of `/collegeadmin` shows which ones are missing.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-college/troubleshooting.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.