> For the complete documentation index, see [llms.txt](https://wiki.redmodding.org/cyberpunk-2077-modding/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/effects-explained.md).

# Effects and particles

How do effects work? How do I mod them?

## Summary

**Published**: Feb 11 2024 by [mana vortex](mailto:undefined)\
**Last documented edit**: Feb 11 2024 by [mana vortex](mailto:undefined)

### Wait, this is not what I want!

* See [Effects modding](/cyberpunk-2077-modding/modding-guides/everything-else/effects-modding.md) for a hands-on list of changing effects in Cyberpunk
* See [Effect components](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/components/documented-components/effect-components.md) for effect explanations by component
* See [FX Material Properties](/cyberpunk-2077-modding/for-mod-creators-theory/materials/configuring-materials/fx-material-properties.md) for animated *materials*
* While explosions are definitely effects, lights are something else => [Lights explained](/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/lights-explained.md)
* To **position** effects, see [Broken mention](broken://pages/0fwS9Da6EqLbMl7czlNM) -> [Broken mention](broken://pages/0fwS9Da6EqLbMl7czlNM#placing-your-light-components)

{% hint style="info" %}
This page is a stub, but this wiki is a community project! Please [sign up](https://app.gitbook.com/invite/-MP5ijqI11FeeX7c8-N8/H70HZBOeUulIpkQnBLK7) and [start editing](#user-content-fn-1)[^1], we'd love to have you!
{% endhint %}

## Effect registry

All effect files are registered in `static_effects.csv`. Since that file can only be edited once, you have to merge your own .es files by script.

For instructions on how to do that, check [Scripting Cyberpunk](https://wiki.redmodding.org/scripting-cyberpunk/) -> [Effects](https://wiki.redmodding.org/scripting-cyberpunk/scripting-cyberpunk/using-scripts-for.../effects)

## Effect duration

An effect's **duration** is defined in the .effects file:

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-b9acfa6e39b3f272a2a1da45d225714a1e0a46f7%2Feffect_duration.png?alt=media" alt=""><figcaption></figcaption></figure>

## Particle lifetime

You can find a particle's lifetime for the individual entries in the `modules` array:

These are probably (?) overwritten by effect durations?

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-621cfbcda31f27cd5708bc805ff2747a868a638b%2Fparticle_durations.png?alt=media" alt=""><figcaption></figcaption></figure>

[^1]: Don't worry, you can't break anything. Each change has to be reviewed by an admin before it is merged back.


---

# 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://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/effects-explained.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.