# How to edit effects

You can edit any effect by clicking on its Scriptable Object in the project window. You will find a live preview in Edit mode (from Unity 6.3, other versions coming asap) that shows you how the effect is applied to different stages of a letter (appearing, disappearing and persistent).

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXuXUTa2X5PYuYL6yRvl1%2Fuploads%2FfTRHNzASaXwPAB8wzSE4%2FClipboard-20251116-161738-126.mp4?alt=media&token=8038e88b-b52f-4387-ae9e-2089b0c875d7>" %}

You can also modify an effect through Rich Text Tags, with [Modifiers](/text-animator-unity/effects/how-to-edit-effects/modifiers.md) (e.g. **\<wave s=2>** to make it twice as fast).

***

{% columns %}
{% column %}
It is important that you always set the **Tag ID**, otherwise the effect will not be recognized in the database!

In the inspector you will also find additional parameters, useful to modify effects even more, like:

* **Bake curves**: keep this to on! It optimizes your effects especially for critical contexts (if you have a lot of letters and a lot of effects on top of each other)
* **Override** [Global Settings](/text-animator-unity/customization/global-settings.md) with a custom [Curves](/text-animator-unity/effects/how-to-edit-effects/curves.md)  or  [Playbacks](/text-animator-unity/effects/how-to-edit-effects/playbacks.md) than default

{% hint style="info" %}
Time to Sync persistant is WIP! Let us know your feedback!
{% endhint %}
{% endcolumn %}

{% column %}

<figure><img src="/files/z27u2De0S4dkXHORzYeJ" alt="" width="375"><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}


---

# 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.febucci.com/text-animator-unity/effects/how-to-edit-effects.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.