> For the complete documentation index, see [llms.txt](https://theobsidianstudio-1.gitbook.io/theobsidianstudio-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://theobsidianstudio-1.gitbook.io/theobsidianstudio-docs/assets/obs_adminmenu/the-report-ecosystem.md). # THE REPORT ECOSYSTEM OBS Admin integrates a breathtaking, high-fidelity ticketing and report architecture natively into the dashboard environment. This eliminates the need for clunky third-party report menus. Players can seamlessly invoke the interface via `/report` or **F8**. *** ### 💾 Independent Data Architecture The report ecosystem operates entirely independent of external databases. It utilizes high-speed internal memory caching, meaning ticket data is retrieved instantly without causing database hitching during peak server hours. If your network operates across multiple servers and requires persistent SQL storage, you may invoke the database module by strictly setting `Config.Report.Database.Enabled = true`. *** ### 📡 Webhook Load Balancing & Routing Maintain absolute, god-tier oversight by routing categorical tickets directly to segmented Discord channels. This prevents channel clutter and allows specialized staff teams to monitor specific pipelines. Modify `Config.Report.Discord` to establish your pathways: * **Player Reports** -> Directs to Moderator channels. * **Bug Diagnostics** -> Directs to Developer channels. * **Staff Inquiries** -> Directs to Management channels. * **Chat Transcripts** -> Archival logging. {% hint style="warning" %} **High-Fidelity Spectate Screenshots** There is a separate `Config.ScreenshotWebhook` outside the report module strictly dedicated to capturing and transmitting uncompressed, high-definition screen captures taken during covert spectate operations. {% endhint %} *** ### 🤖 Psychological AI Responder Managing player expectations during high-stress reports is crucial. The ticketing system features an automated AI Responder layer (`Config.Report.AIEnabled = true`). Upon ticket submission, the "Official Assistant" will instantly generate a randomized, highly professional acknowledgment from the `Config.Report.AIReplies` array. This provides players with immediate psychological reassurance that their ticket has entered the queue, drastically reducing the likelihood of them spamming the chat or opening duplicate tickets while your staff is en route. --- # 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://theobsidianstudio-1.gitbook.io/theobsidianstudio-docs/assets/obs_adminmenu/the-report-ecosystem.md?ask=&goal= ``` `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.