> For the complete documentation index, see [llms.txt](https://docs.ritabot.gg/ritabot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ritabot.gg/ritabot-docs/version-history/120/125.md).

# V1.2.5

Information about the 1.2.5 Update.

{% hint style="info" %}
If you need help at any point join our [**Discord Server**](https://discord.gg/mgNR64R) and someone will help you.
{% endhint %}

### Major Changes

* db.js has had a overhaul
* Database has been migrated to a larger DB, We wont be needing to do that again for a good 5 years.

### Bug Fixes

* Color now working in `Embed on` and takes user role color.
* Stop command for @user has now been fixed

### Command Changes

* Welcome message added for all new servers. System Channel is default, if not available it will pick first channel that has Write permissions.
* Announcement command added, This is Restreicted to DEV ONLY.
* Opt in and out commands added for announcements.
* `!tr settings persist [on/off]` command has been added, this will prevent bot responses from being deleted.

### Database Changes

* Validation Checks added at startup to avoid Blacklist and Stats SQL Errors

### Misc. Changes

* New Debug Settings for console.
* MESSAGE\_DEBUG

  > * 0 - Error's Only
  > * 1 - Console for all Messages
  > * 2 - Console for Translate Messages only
  > * 3 - Content of all Messages
  > * 4 - Content of Translate Messages only
  > * 5 - Commands Only


---

# 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://docs.ritabot.gg/ritabot-docs/version-history/120/125.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.