> For the complete documentation index, see [llms.txt](https://docs.febucci.com/text-animator-unity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.febucci.com/text-animator-unity/2.x/effects/add-effects-to-your-texts/databases.md).

# Databases

Effects are stored into Databases (e.g. “Behaviors”, “Appearances”, “Disappearances”), which are a ScriptableObject on their own as well.

You can add and remove effects to any Database however you prefer, and you can have multiple TextAnimators share the same Databases too. By default, all TextAnimator’s will share the same “Default” Databases from the settings file.

You can create new effects by right-clicking in the Project View -> Create -> Text Animator, and then choose the category and effect you want to add.

<img src="/files/oZZDAaxjNy8WmDrpVNia" alt="textanimator unity create effects scriptable" width="600">

Since you can also edit effect tags in each ScriptableObject, you could create different ones for different purposes, like a specific “shake” effect that applies when a dialogue has to communicate “cold”, and another when it should communicate “fear”.


---

# 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://docs.febucci.com/text-animator-unity/2.x/effects/add-effects-to-your-texts/databases.md?ask=<question>&goal=<endgoal>
```

`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.
