> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-construction/firework/build-custom-effects/generic-firework-objects.md).

# Generic Firework Objects

To make the creation of firework effects easier, Depence comes with so-called "Generic" objects, which automatically create and set up the necessary particle emitters behind, based on simple and known properties.&#x20;

These Generic Objects represent basic firework bombs that are scaling in size defined by the caliber.&#x20;

Usually, all permutations of these Generic Effects are already existing in the factory library, but you can easily use this object to let Depence create some basic particle emitters and settings for you as a good starting point.&#x20;

<mark style="color:blue;">To break down a Generic object into the final objects, do a right-click in the 3D-Hierarchy and choose "Breakdown".</mark>&#x20;

{% hint style="info" %}
Most emitters have a "PressFire" option to test the effect from the Settings Window.
{% endhint %}


---

# 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://help.depence.com/depence-construction/firework/build-custom-effects/generic-firework-objects.md?ask=<question>&goal=<user_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.
