> 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/changelogs.md). # Changelogs ## Changelogs This page contains public update notes for SL Scripts resources. Changelogs are used to explain important changes, fixes, improvements and version updates in a clear way. *** ### About changelogs Each SL Scripts resource may receive updates over time. Updates can include: * Bug fixes * UI improvements * Performance improvements * Compatibility improvements * Configuration changes * New features * Security improvements * Documentation updates *** ### Version format Most SL Scripts resources use version numbers like: ```txt v1.0.0 v1.0.1 v1.1.0 v0.1.14 ``` General meaning: ```txt v1.0.0 = stable release v1.0.1 = small fix / hotfix v1.1.0 = feature update v0.x.x = testing, alpha or pre-release stage ``` Some products may use alpha, beta or release candidate labels when they are still being tested. Example: ```txt v0.2.0-alpha v1.1.0-beta v1.0.0-rc1 ``` *** ### Public update format Public updates usually follow this format: ```txt Update CODE | Product Name — vX.X.X - Visible change or improvement. - Important fix explained clearly. - UI, configuration or compatibility improvement. - Notes about what remains unchanged if needed. ``` Example: ```txt Update GPS-08 | SL Smartwatch GPS — v1.8.14 - Improved stopwatch behavior. - The stopwatch now stops visually as soon as the stop button is pressed. - GPS and signal behavior remain unchanged. - This update focuses on a cleaner user experience. ``` *** ### Spanish / English updates Some update notes may be published in both Spanish and English. Recommended format: ```txt Update CODE | Nombre del Producto — vX.X.X - Cambio visible o mejora en español. - Corrección importante explicada de forma simple. - Mejora de UI, flujo o configuración. ------------------------------------------- Update CODE | Product Name — vX.X.X - Visible change or improvement in English. - Important fix explained clearly. - UI, flow or configuration improvement. ``` *** ### Current product changelogs Product-specific changelogs are listed inside each product page when available. Check the documentation page for the resource you installed: * SL Auto News Camera * SL Cart Ride * SL Civic Pulse * SL Coffee Stand * SL Dev Pose Lab * SL Fight Club * SL Perspective Camera * SL Photo Mode * SL Prank Props * SL Rolmaker Toolkit * SL Scene * SL Smartwatch GPS * SL Vintage Jukebox *** ### Before updating a resource Before updating any SL Scripts resource: ```txt 1. Backup your current resource folder. 2. Backup your database if the resource uses SQL. 3. Read the update notes. 4. Check if config.lua changed. 5. Check if custom.lua changed. 6. Check if SQL changes are required. 7. Replace only the required files if instructed. 8. Restart the resource. 9. Check server console and client F8 console. 10. Test the main flow in game. ``` *** ### Config updates When a new version includes new configuration options, compare your old `config.lua` with the new one. Do not blindly overwrite your custom configuration unless you have a backup. Recommended process: ```txt 1. Backup old config.lua. 2. Open the new config.lua. 3. Copy your custom values into the new config. 4. Check for new options. 5. Save and restart the resource. ``` *** ### SQL updates If an update includes SQL changes, read the product-specific instructions. Some resources may use automatic migrations. If manual SQL is required, import the provided SQL file carefully. Never run old SQL files without checking the update notes first. *** ### Reporting update issues If an issue appears after updating, include: ```txt Product: Resource name: Old version: New version: Framework: Inventory: Target: Database: What changed: Server console error: Client F8 error: Screenshot/video: ``` Example: ```txt Product: SL Vintage Jukebox Resource name: sl_vintage_jukebox Old version: v1.0.14 New version: v1.0.15 Framework: Qbox Inventory: ox_inventory Target: ox_target Database: oxmysql What changed: Updated resource files Server console error: none Client F8 error: attached Screenshot/video: attached ``` *** ### Stable releases A stable release means the resource is considered ready for normal use. Stable does not mean the resource will never receive updates. It means the main flow is expected to work correctly under the documented requirements. *** ### Hotfixes A hotfix is a small update focused on a specific issue. Hotfixes usually do not change the full product roadmap. Examples: ```txt - Fixing a button - Fixing a console warning - Fixing a UI behavior - Fixing a restart issue - Fixing a missing config value ``` *** ### Alpha / testing builds Some products may have alpha or testing builds. These versions are useful for testing new systems, but they may change more often. Use them carefully on production servers. Recommended: ```txt Test alpha builds on a test server before using them on a live server. ``` *** ### Final note Always keep track of the exact version installed on your server. Version information helps with support, bug reports, update checks and troubleshooting. --- # 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/changelogs.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.