> For the complete documentation index, see [llms.txt](https://docs.markhorscripts.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.markhorscripts.com/home/scripts/markhor-vehicleparts.md). # Markhor Vehicleparts {% embed url="" %} {% embed url="" %} Buy now at the Tebex store {% endembed %} ## Dependencies * [markhor\_bridge](/home/scripts/markhor-bridge.md) ## Features **Physical Parts**\ The resource comes with 12 different vehicle parts. This varies from a brake light to a complete front bumper. These parts are placed in the hand of the mechanic after which they can be mounted on the car.\ \ **Own trigger method**\ In the config a client sided event name is described which can be used to open the menu. This event checks the player for the correct job and whether the player is outside a vehicle. In this way, the menu can be integrated in, for example, the mechanic job.\ You can also, for example, link ox\_target or qb\_target using this event.\ \ **Extras**\ \- All the [Markhor Bridge resources](https://app.gitbook.com/o/F9nrzQ2nRVJMcScc4k56/s/jerXUlZqUhXaenH4pxnn/scripts/markhor-bridge) are supported\ \- Logging is possible through the bridge\ \- Current available language settings:\ \- EN | English\ \- NL | Dutch --- # 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://docs.markhorscripts.com/home/scripts/markhor-vehicleparts.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.