> 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/game-maker/creative-guides/experience-design-techniques/art-design/detailing-dressing.md). # Detailing / Dressing ## Add Details Once Experience logic is mostly in place, level designers will begin placing assets that do not need logic applied and make the world come to life. These assets are considered the "dressing" of the Experience because they give it more flavor. Not enough flavor will make the Experience bland, but too much flavor may make it overwhelming or not worth playing.

This Experience was built in the **Oracles Faction** theme by The Sandbox

## Design Considerations * Ensure there are clear pathways for players wide enough to get through without running into the collision boxes of assets * Turn off collisions on short objects on the ground such as stones, carpets, etc. so players don't get caught on them unnaturally while walking * Turn off collisions on grasses, vines, and other non-interactive items that are small and add a lot aesthetically but may cause frustration when walking around - these can also cause players to get stuck! * Test frequently so you can see things from the player perspective, and move assets as needed so the player's line of sight is clear and views are maximised for visual impact * Check often to ensure your Experience dressing aligns with your planned [**visual hierarchy**](/en/creator/game-maker/creative-guides/experience-design-techniques/art-design/experience-art-concept.md#visual-hierarchy) --- # 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/game-maker/creative-guides/experience-design-techniques/art-design/detailing-dressing.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.