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

# Configuration

Every file in `config/` has a short note next to each setting.

| File               | What                                                                                         |
| ------------------ | -------------------------------------------------------------------------------------------- |
| `main.lua`         | Language, school clock, roles, money accounts, modules on or off, waypoint, interface, theme |
| `tablet.lua`       | Item, command, prop, apps and who sees them, CCTV                                            |
| `classpoints.lua`  | Lessons, attendance, points, leaderboards, the lesson bell and voices                        |
| `exam.lua`         | Durations, grading, points                                                                   |
| `notes.lua`        | Notebook limits, inks, pages in the world                                                    |
| `discipline.lua`   | Durations, fines, detention chores, restrictions                                             |
| `affairs.lua`      | The desk clerk, enrolment, clubs, the Student Tablet price, club doors                       |
| `security.lua`     | Lock schedule and doors, hall passes, out-of-campus countdown, guards, alerts                |
| `studentcard.lua`  | Card types, showing distance, photo                                                          |
| `scholarship.lua`  | How students spin, rates, payout, packages, press timings                                    |
| `cardpay.lua`      | ATM models, teacher salary                                                                   |
| `admin.lua`        | Setup panel limits, models and scenarios offered                                             |
| `integrations.lua` | Other Daddy Studio products                                                                  |

## Interface

```lua
Config.Ui = { Notifications = 'college', Progress = 'college' }
```

Notifications and progress bars are drawn in the school's style. Set either to `'ox'` to use ox\_lib's, so they match your other scripts.

## Modules

Every part can be turned off on its own in `Config.Modules` (`tablet`, `classpoints`, `exam`, `notes`, `discipline`, `affairs`, `security`, `studentcard`, `scholarship`, `cardpay`, `admin`).

## Lesson voices

The lesson bell can say the lesson's name. The recordings are in Turkish and play for Turkish lesson names (`Config.ClassPoints.Bell.Voices`); any other lesson gets the bell alone.

## Discord

Set in `server.cfg` with `set`, never `setr`:

```cfg
set daddy:discord_token "bot token"
set daddy:discord_guild "server id"
set daddy:webhook:college:<module> "https://discord.com/api/webhooks/..."
```

A webhook per module (`classpoints`, `exam`, `discipline`, `security`, `tablet`, `scholarship`...) posts that module's log. The bot is only needed for the Discord role options (self-enrolment, excused students, roles taken on expulsion).


---

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