> 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-gps/troubleshooting.md). # Troubleshooting ## The GPS does not open * Check that `ox_lib` is started **before** `daddy-gps`. * If `Config.RequireItem` is `true`, the player needs the item named in `Config.ItemName`. The `/gps` command does not work in that case, use the item or the keybind (`F9`). * If `Config.RequireRealJob` is `true`, the job of the player must be in `Config.AllowedJobs`. * Set `Config.Debug = true` and read the F8 console. The log shows why the GPS was refused. ## "You do not have permission to use this system." The job of the player is not in `Config.AllowedJobs`, or it points to a department key that does not exist in `Config.Departments`. ## Using the item does nothing Add the export to the item definition of your inventory, see the [Installation Guide](/daddy-studios-docs/scripts/daddy-gps/installation-guide.md). ## A department is missing in the list Check that the department has `enabled = true` and that a job is mapped to it in `Config.AllowedJobs`. ## The GPS shows `H2O_FATAL` The player went underwater with the GPS on. It reconnects after the repair sequence. Set `Config.WaterDamage.Enabled = false` if you do not want this system. ## Blips jump or lag Lower `Config.LerpTickMs` for smoother movement. Keep `Config.LerpAlpha` low for slow interpolation. ## Wrong language Set `Config.Locale` to one of `en`, `tr`, `de`, `fr`, `es`, `it`, `nl`, `pt`. Players can also change it in the settings tab of the app. ## Update messages in the console On start the script checks for a new version and prints a message to the server console. It never changes anything on its own. *** Still stuck? Join our [Discord](https://discord.gg/NFKjbN9s2q) and send your Tebex ID and the console log. --- # 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-gps/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.