> For the complete documentation index, see [llms.txt](https://docs.polygonflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polygonflow.io/how-it-works.md).

# HOW IT WORKS

- [Procedural Scattering](https://docs.polygonflow.io/how-it-works/scatter-masking-features.md): Dash contains various scatter tools, each tailored towards specific purposes. And in this page we will explain why these scattering tools are the most used ones in Dash.
- [Centralized Asset Browser](https://docs.polygonflow.io/how-it-works/centralized-asset-browser.md): With Dash's Content Browser, you can tag all your assets, making them easy to find and also create a Centralized Asset Browser. Meaning that you can access all your UE5 assets from any Unreal project.
- [Material / Atmospheric Tools](https://docs.polygonflow.io/how-it-works/material-authoring.md)
- [Procedural Mesh Tools](https://docs.polygonflow.io/how-it-works/mesh-based-tools.md)
- [Physics Tools](https://docs.polygonflow.io/how-it-works/physics-tools.md): Dash features a set of physics tool that help you realistically place objects, from painting them with realtime collision to individually moving objects, and watching them push their way through.
- [Workflow Enhancements](https://docs.polygonflow.io/how-it-works/misc-tools.md)


---

# 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.polygonflow.io/how-it-works.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.