> 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/obstacles.md).

# Obstacles

## How to Create Obstacles

<figure><img src="https://331512196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F83PS3g9zpWmq73xzlwFn%2Fuploads%2F7D945qwiMYsaHnAI2J8r%2FMusic%20Mayhem%20obstacle%20example.webp?alt=media&amp;token=723756da-f69a-47cb-97a9-bb2584dc9a3a" alt="" width="505"><figcaption><p><a href="https://youtu.be/tQoy0LTm6uM?t=11667">Wall obstacles created for Music Mayhem Experience <br>by Jacobg1998</a></p></figcaption></figure>

In this example, assets were created as obstacles for players to jump around and through to survive in a game jam entry that became a featured experience in Sandbox Alpha Seasons. These are compound assets created in the Animator with no motion keyframes added so players can jump through the empty spaces.

Obstacles should use Game Maker logic to be physically interactive, not animate the interactions, since animated assets have a single collision box and would have no affect on players regardless of how they appear.


---

# 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/obstacles.md?ask=<question>&goal=<user_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.
