> For the complete documentation index, see [llms.txt](https://alexs-organization-34.gitbook.io/scatter-graph/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alexs-organization-34.gitbook.io/scatter-graph/introduction.md).

# Introduction

**Scatter Graph** is a node based tool to procedurally scatter point instances on a Unity terrain based on user defined rules and filters. The points data is then exported and loaded at runtime to instantiate prefabs following distance based activation/pooling rules ([lazy initialization](https://en.wikipedia.org/wiki/Lazy_initialization)). This means prefabs are instantiated and enabled only when needed without polluting the scene with thousands of GameObjects from the start of the game.

### Why Scatter Graph

Creating large environments usually means dealing with thousands of GameObjects, heavy scenes and slow editor performances. **Scatter Graph** avoids this by generating and storing placement data ahead of time. This allows to populate terrains with complex placement rules while keeping both the editor and runtime performances fast and responsive.

The goal of **Scatter Graph** is not only to populate large terrains, but to make every spawned object part of the gameplay experience. Since runtime instances are regular GameObjects, they can fully interact with gameplay systems such as physics, destruction, harvesting, AI or player interactions, allowing to create dense and fully interactable environments without sacrificing performances.

{% embed url="<https://youtu.be/s2nTuTwG4Cc>" %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://alexs-organization-34.gitbook.io/scatter-graph/introduction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.