> For the complete documentation index, see [llms.txt](https://docs.sandbox.game/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandbox.game/en/creator/voxedit/creative-guides/asset-guide/vehicles.md). # Vehicles ## Creating Vehicles Vehicles may require more nodes to create unusual shapes instead of using voxels to create curves. To create wheels for vehicles, use the [**Cross Technique**](/en/creator/voxedit/creative-guides/art-techniques/3d-design/circular-shapes-cross-technique.md), and [**combine models**](/en/creator/voxedit/docs/ve-guidelines/node-efficiency.md#better-group-items-in-a-model) for each axel to improve the performance of your asset in the Game Maker or Game Client software. {% hint style="info" %} It is currently not possible to get inside of a vehicle to drive in the game, but this feature is on our road map. For now, single player Experiences where the player is driving the whole time can be created by setting a vehicle asset as a custom avatar in [Spawn Point & Avatar's Feature](/en/creator/game-maker/docs/behaviours/basic-logic/spawn-point-and-avatars-feature.md). This means you can have multiple spawn points with different custom vehicles as avatars spawned. {% endhint %} --- # 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://docs.sandbox.game/en/creator/voxedit/creative-guides/asset-guide/vehicles.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.