> 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/installation.md).

# Installation

1. Download **daddy\_lib** and **daddy\_college** from your [Keymaster](https://keymaster.fivem.net) and put both folders in your `resources` folder. Do not rename them.
2. Add the items: copy the file for your inventory from `daddy_college/install/generated/items/<language>/` (`ox.lua`, `qb.lua`, `qs.lua`, `codem.lua`, `core_inventory.lua`, `tgiann.lua`) into your inventory's item list, or run `esx.sql` on ESX.
3. Add the jobs from `daddy_college/install/generated/jobs/<language>/`: `qbx.lua` or `qb.lua` into your shared jobs, `esx.sql` on ESX. The jobs are `student`, `teacher`, `principal`, `school_security`, `canteen`, `school_driver` and `janitor`.
4. Start them after their dependencies in `server.cfg`:

```cfg
ensure ox_lib
ensure oxmysql
ensure qbx_core          # or qb-core / es_extended
ensure ox_inventory      # your inventory
ensure ox_target         # or qb-target
ensure daddy_lib
ensure daddy_college
add_ace group.admin daddy.admin.college allow
```

5. Restart the server. The tables (`daddycl_*`) are created on the first start.
6. Pick the language in `config/main.lua`: `Config.Locale = 'en'` or `'tr'`.

Continue with [First Setup](/daddy-studios-docs/scripts/daddy-college/first-setup.md).

{% hint style="info" %}
`daddy status` in the server console lists every Daddy Studio resource with its version and state; `daddy check` shows the framework and inventory it found and any item missing from your inventory.
{% endhint %}


---

# 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/installation.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.