> For the complete documentation index, see [llms.txt](https://sl-scritps.gitbook.io/sl-scripts-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-smartwatch-gps.md). # SL Smartwatch GPS ## SL Smartwatch GPS **Code:** GPS-08\ **Resource:** `sl_smartwatch`\ **Version:** v1.8.14\ **Category:** Utility / Wearable Device / GPS Tool\ **Status:** Stable **Structured tools for serious roleplay servers.** *** ### Overview SL Smartwatch GPS is a wearable smartwatch-style utility for FiveM roleplay servers. It provides a compact in-game HUD with GPS/minimap control, location information, signal behavior, stopwatch tools and a clean device-style interface. The resource is designed to work as an immersive IC device instead of only being a command-based utility. *** ### What is this script for? SL Smartwatch GPS gives players a simple wearable device that can be used for navigation, timing and lightweight roleplay utility. It is useful for: * Civilian roleplay * Exploration * Events * Racing support * Outdoor activities * Staff testing * Immersive GPS access * Servers that want GPS access to feel like an item/device *** ### Roleplay Experience SL Smartwatch GPS is designed to feel like an in-character wearable device, not just a technical HUD. The idea is simple: ```txt The player owns or receives a smartwatch item. The player uses it in game. The smartwatch becomes their navigation and timing device. ``` This makes GPS access feel more natural for roleplay servers, especially when the server wants navigation, location tools or event timing to come from an IC object instead of a permanent out-of-character HUD. The smartwatch can be used by civilians, racers, explorers, workers, staff characters, event participants or any player who needs a lightweight GPS-style device. *** ### Player / IC Flow #### 1. The player gets a smartwatch The player receives or buys the smartwatch item depending on the server setup. Example item: ```txt smartwatch ``` The server can decide how players obtain it: * Sold in a shop * Given by staff * Added to a job loadout * Used as a civilian utility item * Given during an event * Added as a starter item *** #### 2. The player uses the item The player opens their inventory and uses the smartwatch item. In roleplay terms, the character is putting on or activating the smartwatch. Expected result: ```txt The smartwatch HUD appears. The device is now active. ``` If the server requires the item, the player must keep the smartwatch in their inventory while using it. *** #### 3. The player uses GPS features Once active, the player can use the smartwatch to control GPS/minimap behavior. Common IC uses: * Checking navigation while driving * Finding the current area * Using GPS during travel * Supporting racing or delivery routes * Helping with exploration * Using the device during outdoor activities Example RP line: ```txt “My watch still has signal, I can check the route.” ``` *** #### 4. Signal can affect the experience If signal logic is enabled, the smartwatch may show no signal in certain places. Example: ```txt NO SIGNAL ``` This can happen in places such as tunnels, underground areas or configured no-signal zones. In RP, this creates a more immersive limitation: ```txt “We lost signal inside the tunnel.” “The GPS is not updating underground.” ``` *** #### 5. The player can use the stopwatch The stopwatch can be used for roleplay situations that need timing. Examples: * Races * Training * Events * Challenges * Delivery timing * Staff-organized activities * Fitness or endurance RP The stopwatch is a lightweight utility and does not require a complex admin setup. *** #### 6. The player can turn the device off When finished, the player can use the OFF button or configured control to turn off the smartwatch. Expected result: ```txt The smartwatch HUD closes. GPS/device behavior returns to inactive state. ``` This keeps the device feeling like something the character actively uses, instead of a permanent HUD. *** ### Example IC Scenarios #### Civilian use A civilian buys a smartwatch and uses it while driving around the city. ```txt “I’ll check my watch and follow the GPS.” ``` #### Racing event A player uses the stopwatch before a timed route or training run. ```txt “Start the timer when I pass the line.” ``` #### Exploration A player uses the smartwatch while moving through remote areas. ```txt “The signal is weak here. We may need to go back to the road.” ``` #### Staff or event use Admins or event organizers can use the smartwatch as a simple IC timing/navigation tool during organized activities. ```txt “Use your smartwatch timer for this round.” ``` *** ### What this resource is not SL Smartwatch GPS is not intended to be a full phone system, dispatch system or complex tracking platform. It is focused on: ```txt GPS utility small wearable HUD stopwatch signal behavior item-based device feeling ``` For best roleplay results, servers should treat it as a simple smartwatch device that supports navigation and timing. *** ### Main Features * Wearable smartwatch-style HUD * GPS / minimap toggle * Signal and no-signal behavior * Location display * Stopwatch * Heartbeat-style visual detail * Item-based usage when enabled * Server-side item validation when supported * Command fallback * Mouse/focus mode * Compact NUI interface * Clean visual design * Configurable framework, inventory and notify bridges * Standalone-friendly structure *** ### Dependencies #### Required ```txt FiveM server ``` #### Optional / Supported ```txt QBCore Qbox ESX ox_inventory qb-inventory qs-inventory ox_lib Custom notify systems ``` The resource can be configured depending on your server setup. If item usage is enabled, make sure your inventory system supports the configured item. *** ### Installation Notes 1. Place the resource folder inside your server resources folder. Example: ```txt resources/[sl_scripts]/sl_smartwatch ``` 2. Make sure the folder name is: ```txt sl_smartwatch ``` 3. Configure: ```txt config.lua custom.lua ``` 4. If using item mode, create or confirm the item in your inventory system. Default item: ```txt smartwatch ``` 5. Add the resource to your `server.cfg`. Example: ```cfg ensure sl_smartwatch ``` If using inventory or framework integrations, make sure they start before `sl_smartwatch`. Example: ```cfg ensure ox_lib ensure ox_inventory ensure sl_smartwatch ``` *** ### Item Setup Default item name: ```txt smartwatch ``` If `Config.RequireItem` is enabled, the player must have the smartwatch item to use the device. If active item validation is enabled, the resource may also check if the player still has the item while the device is active. This prevents players from activating the smartwatch, removing the item and still keeping the device enabled. *** ### How to Use #### Basic Player Flow 1. The player obtains the smartwatch item. 2. The player uses the item from inventory. 3. The smartwatch HUD appears. 4. The player uses GPS, signal or stopwatch tools depending on the situation. 5. The player can toggle mouse/focus mode if needed. 6. The player turns the device off when finished. #### IC Summary ```txt Get smartwatch → use item → device turns on → use GPS/stopwatch → turn off device ``` #### OOC / Technical Summary ```txt Have required item → activate resource → NUI opens → controls become available → device state is saved/updated while active ``` *** ### GPS Behavior The smartwatch can control GPS/minimap visibility depending on configuration. Common behavior: ```txt GPS ON = minimap / GPS visible GPS OFF = minimap / GPS hidden or disabled ``` The exact behavior may depend on your server configuration. *** ### Signal Behavior SL Smartwatch GPS can use signal logic to make the device feel more immersive. For example, some areas may show: ```txt NO SIGNAL ``` This is useful for tunnels, underground areas or zones where GPS access should feel limited. *** ### Stopwatch The smartwatch includes a stopwatch tool. In v1.8.14, the stopwatch was improved so the stop action updates visually immediately when pressed. This makes the stopwatch feel cleaner and more responsive. *** ### Commands Depending on configuration, the resource may include command fallback. Common command: ```txt /smartwatch ``` Possible mouse/focus command: ```txt /smartwatch_mouse ``` Legacy mouse/focus command if enabled: ```txt /smartwatch_cursor ``` Commands are useful for testing, fallback access or servers that do not want item-based usage. *** ### Keybinds If enabled, the resource may register a focus key for mouse interaction. Default focus key may be: ```txt F7 ``` Check `config.lua` for the exact keybind configuration. *** ### Admin / Owner Notes SL Smartwatch GPS is mainly a player utility, but owners and admins should check: * Item configuration * Inventory bridge * Framework detection * Notify bridge * Signal zones * GPS behavior * Command fallback * Debug mode * Startup logs There is no complex admin panel required for normal usage. *** ### Configuration Open: ```txt config.lua ``` Common settings may include: ```txt Product information Framework mode Inventory mode Notify mode Item name Require item true/false Register usable item true/false GPS behavior Signal zones Stopwatch settings Command settings Keybind settings NUI behavior Debug mode Startup logs ``` Recommended for production: ```lua Config.Debug = false ``` Use debug mode only for testing or troubleshooting. *** ### Custom Integrations Open: ```txt custom.lua ``` Use this file if your server has: * Custom inventory * Custom notifications * Modified framework functions * Custom item checks * Custom player identifiers * Custom server-side logic If your server uses a standard framework or inventory system, you may not need many changes here. *** ### Startup Logs When the resource starts correctly, you may see logs similar to: ```txt [sl_smartwatch][INFO] Server ready: SL Smartwatch GPS v1.8.14 [sl_smartwatch][INFO] Client ready: SL Smartwatch GPS v1.8.14 | Use /smartwatch ``` If startup logs are disabled, check `config.lua`. *** ### Troubleshooting #### The smartwatch item does not work Check: ```txt - The item exists in your inventory system. - The item name matches config.lua. - The inventory bridge is configured correctly. - The player actually has the item. - The resource started without server console errors. ``` Default item: ```txt smartwatch ``` *** #### The command does not work Check: ```txt - Commands are enabled in config.lua. - You are using the correct command. - The resource is started. - Client F8 console has no errors. - Server console has no errors. ``` Try: ```txt /smartwatch ``` *** #### GPS does not appear Check: ```txt - GPS is enabled in config.lua. - The device is turned on. - You are not inside a configured no-signal area. - Another resource is not forcing minimap visibility. - F8 console has no errors. ``` *** #### Device turns off by itself If item validation is enabled, the smartwatch may turn off when the player no longer has the required item. Check: ```txt - Player still has the smartwatch item. - Inventory bridge is working. - Active item validation is configured correctly. ``` *** #### NUI does not open Check: ```txt - web/ folder exists. - ui_page is correctly declared in fxmanifest.lua. - NUI files are listed correctly. - F8 console has no JavaScript errors. - Resource folder name is still sl_smartwatch. ``` *** #### Mouse does not interact with the HUD Check: ```txt - Focus key is configured. - Mouse/focus command is enabled. - Another NUI is not blocking focus. - F8 console has no errors. ``` Try the configured focus key or command. *** #### No signal appears everywhere Check: ```txt - Signal zones configuration. - Tunnel / underground detection settings. - GPS signal logic in config.lua. - Debug mode output if enabled. ``` *** ### Version Notes #### v1.8.14 * Stopwatch stop behavior improved. * Stopwatch now visually stops immediately when pressing stop. * GPS and signal behavior remain unchanged. * Focused on a cleaner user experience. #### v1.8.13 * Clean smartwatch UI improvements. * Location display simplified. * Stopwatch format refined. * Heartbeat visual detail improved. * Tunnel / no-signal behavior supported. * Item validation behavior supported. *** ### Support When asking for support, include: ```txt Product: SL Smartwatch GPS Resource name: sl_smartwatch Version: Framework: Inventory: Notify system: Issue: Steps to reproduce: Server console error: Client F8 error: Screenshot/video: ``` Example: ```txt Product: SL Smartwatch GPS Resource name: sl_smartwatch Version: v1.8.14 Framework: Qbox Inventory: ox_inventory Notify system: ox_lib Issue: Smartwatch item does not open the HUD Steps to reproduce: Use smartwatch item from inventory Server console error: none Client F8 error: attached Screenshot/video: attached ``` *** ### Final Notes SL Smartwatch GPS is intended to be a simple, clean and immersive wearable utility. For best results, configure the item, inventory bridge and GPS behavior according to your server style. --- # 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://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-smartwatch-gps.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.