> For the complete documentation index, see [llms.txt](https://bnc-scripts.gitbook.io/bnc-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bnc-scripts.gitbook.io/bnc-scripts-docs/readme.md). # Welcome to BNC Scripts Welcome, and thank you for visiting **BNC Scripts** — a development studio focused on **high-quality, immersive FiveM scripts**. I’ve been involved in programming and FiveM development since 2019 — constantly learning, experimenting, and pushing the limits of what a truly dynamic RP experience can be. I don’t just write scripts — I **build systems that make your server feel alive**. Every release is crafted with **performance, realism, and community feedback** in mind. From immersive vehicle mechanics like **realistic tire wear and balancing**, to fully-featured job systems and optimized utility tools, everything is built to last — not just to sell. *** #### 🛠 What You Can Expect: * Focused development experience since 2019 * **Immersive mechanics** with real gameplay impact * Lightweight, configurable, **performance-optimized** code * Ongoing **updates, support, and roadmap-based growth** * Built by a player. Maintained by a perfectionist. Balanced for your server. *** This is not just about code — it’s about **creating tools for better stories, deeper roleplay, and stronger communities**. Thank you for being part of the journey.\ 🛞 **Let’s roll.** --- # 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://bnc-scripts.gitbook.io/bnc-scripts-docs/readme.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.