> For the complete documentation index, see [llms.txt](https://docs.sollumz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sollumz.org/documentation/maps/grass-batches.md). # Grass Batches Grass batches are represented as a mesh with only vertices, where each vertex represents a grass instance. Attributes are used to store per-grass instance settings. Geometry nodes are used to generate and preview grass batches. Each grass batch is configured through a list of "templates", which define the models that can appear and their per-model settings (e.g. scale, LOD distance). The geometry nodes modifier then uses these templates to scatter the grass instances over a base mesh. {% embed url="" %} The geometry nodes require Blender 5.0 or newer. Import/export still works on all supported versions, since the grass batch itself is just a regular mesh containing only vertices. This also means some manual editing is possible.

--- # 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.sollumz.org/documentation/maps/grass-batches.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.