> For the complete documentation index, see [llms.txt](https://cgtoolbox.gitbook.io/cgtoolbox-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cgtoolbox.gitbook.io/cgtoolbox-docs/pcg-random-assemblies/random-assembly-definition.md).
# Random Assembly Definition
This is the main Data asset you will need, it's pretty simple as it has only three entries;
* The PCG Data asset entry
* The Dictionary of variants you want to apply on the PCG Data Asset, where the keys are the target tag(s).
* The static mesh spawner settings node (which can be overridden per variant).
Variants and their target tag(s).
***
You can create a new Random Assembly definition by using the "Create Assembly Definition":
{% tabs %}
{% tab title="BP Random Assembly actor" %}
From the button on the BP Random Assembly actor:
{% endtab %}
{% tab title="From Content Browser" %}
Alternatively you can create the data asset directly from the content browser by selecting Miscellaneous -> Data Asset
And pick the BPDA\_RandomAssemblyDefinition Class:
{% endtab %}
{% endtabs %}
***
---
# 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://cgtoolbox.gitbook.io/cgtoolbox-docs/pcg-random-assemblies/random-assembly-definition.md?ask=&goal=
```
`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.