# Generator

Generators define how the scene is built up, what objects are spawned and the the rules of placement of objects on the terrain. Every scene that you will build with Moonlander consists of several generators, each responsible for a different component in your scenes. All generators combined in your scene is called your Generator Stack.

There are two types of Generators: the [Global Generator](/v.1.0.0.alpha-4/explore-topics/generator/global-generator.md) and the [Bounds Generator](/v.1.0.0.alpha-4/explore-topics/generator/bounds-generator.md). You can define global settings through Global Generators and define the placing of objects and creation of Unity terrains through the Bounds Generator.

Each Generator consists of two tabs:

* Properties. The properties tab consists of all settings that make up this generator. Some Generators are very simple, while others can be very complex.
* Dependencies. In this tab, you can see the links between generators. The Input lists the Generators to which the current Generator listens, the Output lists the Generators that have the current Generator as Input. For more information see [DataRegistry](/v.1.0.0.alpha-4/explore-topics/dataregistry.md).

{% hint style="info" %}
Dependencies are key for building scenes that make sense. For example, you don't want to have your vegetation to grow on your roads! Linking your road generator with your foliage generator can quickly solve this issue.
{% endhint %}

####


---

# Agent Instructions: 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:

```
GET https://docs.moonlander.ai/v.1.0.0.alpha-4/explore-topics/generator.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.