> 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/dash-tools/particletool.md). # Edit Particles ## Short Description Adjust particle settings and properties for enhanced effects. ## Description This tool allows users to adjust various settings related to particle effects, including physical properties and visual attributes. Users can control aspects such as density, speed, color, and more to refine the particle system in their application. ## Properties ### Base Properties * **Density**: Controls the density of the particles. * **Bounds**: Controls the bounds of the particles. * **Scale**: Controls the scale of the particles. * **Lifetime**: Controls the lifetime of the particles. * **Speed**: Controls the speed of the particles. * **Gravity**: Controls the gravity of the particles. * **X Stretch**: Controls the stretching of the particles in the X axis. * **Y Stretch**: Controls the stretching of the particles in the Y axis. * **Hue**: Adjusts the hue of the particles. * **Saturation**: Adjusts color saturation. * **Brightness**: Controls brightness levels. * **Opacity**: Controls the visibility of the particles. --- # 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/dash-tools/particletool.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.