> 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/126.md).

# V1.2.6

Information about the 1.2.6 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

* Sharding is now automatic, this should auto scale to the needed amount.
* A Major memory leak causing rita to restart every few hours has now been fixed.

### Bug Fixes

* `!tr announce on/off` has been fixed.
* `!tr settings` has been unrestricted.
* `!tr blacklist {ServerID}` has been fixed.
* `!tr channel from {lang} to {lang}` no longer defaults to a DM task.

### Command Changes

* `!tr react on/off` now turns on and off flag reactions.

### Database Changes

* Added in 3 new columns ready for auto-warn and eject management

  > Servers will be allowed 10 Permission Errors Before a Warning

  > Server will be given a Maximum of 3 Warning before they are Ejected

  > If your server should be Ejected a second time it will be blacklisted

### Misc. Changes

* Sooooooo Many spelling mistakes corrected that it would be too many to list here.
* Help Menu updated with new commands.


---

# 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/126.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.