> 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/changelog.md). # Changelog ## 1.0.0 First public release. * School tablet for staff: students, classes, clubs, lessons with live attendance, timetable, exams, discipline, announcements, Security Center and Director Panel * Lessons announced with notices and markers to the classroom and the teacher, an attendance book signed in the room, class points and leaderboards * Exams on printed booklets, grading in red pen, a report card * A notebook to write and draw in; pages can be torn out and left in the world * Detention with chores and fines; a teacher's sanction waits for the principal * Student Affairs desk: enrolment, ID card, hall pass requests, rankings, club management * Campus security: countdown and return for students outside without a pass, hall passes, alerts, CCTV, campus lock, gate guards * Student, teacher, principal and security ID cards * Scholarship press paying out to the school card; ATMs on the map * Everything placed in game from `/collegeadmin`, with history and undo * Qbox, QBCore and ESX through daddy\_lib; English and Turkish --- # 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/changelog.md?ask=&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.