> 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/support.md). # Support ## Support This page explains how support works for SL Scripts resources. Before contacting support, please read the product documentation and the Troubleshooting page. *** ### Official support channel Official support is provided through Discord: ```txt https://discord.gg/jCncSfFJHX ``` Use this Discord for: * Installation questions * Configuration help * Bug reports * Product questions * Update information * Basic troubleshooting *** ### Before asking for support Please check these pages first: 1. Getting Started 2. Installation 3. The product page for your resource 4. Troubleshooting Most common issues are related to: * Wrong folder name * Missing dependencies * Incorrect ensure order * SQL not imported * Inventory item not configured * Target system not started * Missing permissions * Server console errors * Client F8 errors *** ### What support includes Support includes help with: * Basic installation * Resource startup issues * Configuration guidance * Product-specific bugs * Reproducible errors * Missing dependency checks * Permission setup guidance * SQL setup guidance * General product usage questions *** ### What support does not include by default Support does not include: * Full server setup * Custom framework rewrites * Rewriting the resource for private systems * Installing unrelated third-party resources * Fixing errors caused by other scripts * Creating custom features on demand * Redesigning the full UI for one server * Editing protected escrow files * Setting up your entire database * Configuring every server resource manually Custom work may be discussed separately, but it is not part of standard product support. *** ### Information to include When asking for support, include as much information as possible. Recommended format: ```txt Product: Resource name: Version: Framework: Inventory: Target: Database: 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 Target: ox_target Database: Not required Issue: Item does not open the smartwatch Steps to reproduce: Use smartwatch item from inventory Server console error: none Client F8 error: none Screenshot/video: attached ``` *** ### Version number Always include the installed version when reporting an issue. The version may appear in: * Startup logs * NUI footer * Admin panel * About section * README.md * Product page Example: ```txt SL Smartwatch GPS ยท v1.8.14 ``` Reports without version information may take longer to review. *** ### Screenshots and videos Screenshots or short videos are very helpful. Try to show: * The issue happening * The server console * The client F8 console * The resource folder name * The config section related to the issue * The item/target/command being used Do not share private information such as: * Webhook URLs * Database passwords * Server license keys * Private tokens * IP addresses * Personal data *** ### Bug reports A good bug report should explain: ```txt 1. What you expected to happen 2. What actually happened 3. How to reproduce it 4. Which version you are using 5. Whether the issue happens after restart 6. Whether the issue happens on a clean test server ``` The easier it is to reproduce the issue, the faster it can be fixed. *** ### Updates Product updates may include: * Bug fixes * Compatibility improvements * UI improvements * Configuration improvements * Performance improvements * New features * Documentation updates Always read the product changelog or update notes before replacing files. *** ### Custom servers Some servers use heavily modified frameworks, inventories, banking systems, permissions or UI resources. SL Scripts resources are designed to be configurable, but custom servers may require additional bridge work in `custom.lua`. If your server uses custom systems, mention that clearly when asking for support. *** ### Refunds and purchases For purchase-related issues, check your Tebex / CFX account first. Common purchase issues: ```txt - Wrong CFX account - Asset not granted yet - Server license key does not match account - Downloaded from the wrong account - Asset Escrow entitlement error ``` Purchase and entitlement issues may require checking Tebex or CFX delivery status. *** ### Official links **Tebex Store** ```txt sl-scripts-webstore.tebex.io ``` **Discord Support** ```txt https://discord.gg/jCncSfFJHX ``` **YouTube** ```txt https://youtube.com/@sl_scripts ``` *** ### Final note SL Scripts resources are built for serious roleplay servers. Clear reports, correct version information and complete error details help keep support faster and more accurate. --- # 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/support.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.