> 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-deathscreen/troubleshooting.md). # Troubleshooting ## Two texts are on screen at the same time Your ambulance script still draws its own death text. Remove the lines that draw text, see [Framework Integration](/daddy-studios-docs/scripts/daddy-deathscreen/integration.md). ## The screen does not open * Start `daddy-deathscreen` after your framework and your ambulance script * Your server artifact must be 5104 or newer with OneSync enabled * Set `Config.Debug = true` and read the F8 console. Check that the detected framework is the one you use, or set `Config.Framework` by hand * Test it with `/deathscreentest 120 dead center`. If that works, the screen is fine and the death state is not reaching it ## `/deathscreentest` says nothing or is not allowed Your account is missing the permission. Add it in `server.cfg` and restart the server: ```cfg add_ace group.admin command.deathscreentest allow ``` ## The timer does not match my ambulance script (QBCore, ESX) These scripts do not expose their timers. Set `Config.Timers` to the values of your script, see [Effects & Timers](/daddy-studios-docs/scripts/daddy-deathscreen/configuration/effects-and-timers.md). ## The fee in the respawn text is wrong Set `Config.RespawnFee` to the fee of your ambulance script. `0` hides the fee. ## The screen stays grey after I am revived Another resource is using a game timecycle modifier at the same time. Set `desaturate = false` in `Config.Effects`. ## The cause of death is missing The framework reported no attacker and no weapon (for example a script kill). No cause is shown then. ## The fonts look different The bundled Sora font could not load. Check that the files in `html/assets` were not removed and that the resource was fully restarted. --- # 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-deathscreen/troubleshooting.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.