> 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-carcrafting/changelog.md). # Changelog ## 1.0.1 * Removed a leftover logo from the crafting screen header ## 1.0.0 First public release. * In-world workbench screen with categories, build plans, material check, level and blueprint locks * Part by part assembly with carried props, install markers, animations and skill checks * Live car body on a creeper and an assembly board with progress, quality and the next step * Helpers: the owner invites nearby players from the parts rack, helpers share the XP * Quality grades that set engine and body health of the delivered vehicle * Guaranteed and chance based recipes, crafting levels with XP * Builds survive restarts and reconnects, other players see builds in progress * Delivery to the first free parking spot, saved to the owner's garage with keys and fuel * Qbox, QBCore and ESX; ox, qb, ps, lj, qs and codem inventories; ox\_target and qb-target * 20 base game vehicles in 7 categories, item lists for ox\_inventory, qb-core and ESX, 13 item images * English and Turkish --- # 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-carcrafting/changelog.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.