> For the complete documentation index, see [llms.txt](https://prisma-logs.gitbook.io/prisma-logs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prisma-logs.gitbook.io/prisma-logs/docs/en/help/faq.md).
# FAQ
Do I have to change my scripts?
No. Prisma Logs only reads your scripts to find their events and listens along. Your files are never changed.
Does it slow down my server?
Logs are collected and sent in one batch every 3 seconds. Actions that fire too often are capped. The resource does nothing heavy while people play.
Does it work with ESX, QBCore and Qbox?
Yes. Your framework is detected automatically. Whatever isn't running is skipped.
Does it work with encrypted (Tebex) scripts?
Those can't be scanned. If you know their event names, log them with [your own events](/prisma-logs/docs/en/configuration/custom-events.md).
Can my staff see the logs?
Yes. Add them under **Staff**. They see all logs but can't change anything about your server.
Why don't I see commands from other scripts?
FiveM has no way to see all commands of other scripts. Log commands with the [export](/prisma-logs/docs/en/configuration/export.md).
How long are logs kept?
7, 30 or 90 days, depending on your [plan](/prisma-logs/docs/en/the-panel/plans.md).
I added a new script. Now what?
Press **Scan scripts** under **Categories** in the panel. The new actions show up within a minute.
---
# 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://prisma-logs.gitbook.io/prisma-logs/docs/en/help/faq.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.