# 18/05/2026 {% hint style="warning" %} **PLEASE NOTE:** This Update was accurate at the time of sharing. Please refer to our Support documentation to ensure accurate and up-to-date information is known, If you have any questions or concerns please join our [**Discord Server**](https://discord.gg/ritabot) and someone will assist. {% endhint %} {% code overflow="wrap" %} ```typescript It has been a little while since the last update, and we have been working on a range of backend improvements, diagnostics, reporting changes, and support for a new translation provider. So here are some updates for you. * DeepL integration * Message counter support added back in, your stats will now show a full message counter * DeepL added to dashboard for users to select from * A new `!tr diag` diagnostic command * Stats updates for DeepL * Locale updates for new stats output * DeepL support in the slash command * Early work on a new Balance command (More info to come soon) ``` {% endcode %} ## DeepL Integration 
Yes, Yes, thats correct. 

We have now added support for DeepL as a translation engine within RITA.

This allows DeepL to be used alongside our existing supported translation systems and gives us more flexibility in how translations are handled across the platform.

This also lays the groundwork for future improvements in engine handling, reporting, and usage balancing.
{% code title="PLEASE NOTE:" overflow="wrap" %} ```typescript DeepL characters cost more per million than Google characters, so this multiplier allows usage to be balanced more fairly when DeepL is being used. The Multiplier is set at 1.0432, so for every 100 characters used normally, it would use 104 with DeepL, Full information can be found in out S.A.L.T.S policy. https://docs.ritabot.gg/ritabot-docs/policys/s.a.l.t.s-policy#deepl-api-usage-updated-limits ``` {% endcode %} ## Message Counter Added Back In 
A few years ago we remove the total message count from our stats, this was for a few reason but maininly to reduce the calls on our Database and improve stability, RITA will once again track message count data as part of her normal stats tracking.

For now on you will see total message count in your stats - check `!tr stats` or `/stats`
## /diag - A new diagnostic command to fix your issues 
We understand that not everyone wants to reach out to support. As such, we have created a new diagnostic command for you to use. !tr diag and /diag will run a diagnostic check of RITA on your server.

At present, it can:
* fix object issues where the object and database do not match
* fix Server table issues where OwnerID, Owner, or ServerName are incorrect in the database
* fix task count values in the database where they are incorrect
* revalidate after a fix has been performed

This will be expanded upon to create more ways for us to automate and resolve any issues you may have.
## /reactionroles - Reaction Role support built in 
Setting up language roles just got a whole lot easier. The new /reactionroles command lets you create and manage reaction role messages directly from Discord.

At present, it can:
* `add` emoji/role pairs to any existing message — users react to get the role
* `remove` a single reaction role from a message
* `edit` which role is assigned to an emoji
* `delete` all reaction roles from a message in one go
* `list` all active reaction role messages on your server with status indicators
* `toggle` individual or all reaction roles on a message (enable/disable)
* `build` a brand new reaction role message with up to 11 emoji/role pairs and optional styling
* `group` automatically build a reaction role message from an existing translation group — RITA detects your language channels and matches roles for you

Reactions are automatically cleaned up after a user selects a role, keeping the message tidy.
## /quicksetup - An all-in-one Set-up wizard 
We know that setting up RITA for the first time can involve a lot of steps. /quicksetup is a guided wizard that walks you through the entire process in one go.

It will:
* Create or select a category for your translation channels
* Create up to 20 language channels with a naming prefix of your choice
* Create matching roles for each language — or reuse roles from an existing translation group
* Set channel permissions so only users with the right role can see each channel
* Post a reaction role message so users can self-assign their language

If you cancel at any point or the wizard times out, RITA will automatically clean up anything it created. You can skip permissions and the reaction message if you'd prefer to configure those yourself.
{% code title="Disclaimer:" overflow="wrap" %} ``` RITA is not responsible for any errors in permission levels or incompatible permission structures. This tool is designed to assist with quick setup — please review all permissions and channel settings to ensure they are configured to your requirements. ``` {% endcode %} ## /feedback - Feedback command, Tell us more! 
We want to hear from you — whether it is a bug, a suggestion, or just general feedback. The new /feedback command opens a form right inside Discord where you can:

Select a feedback type (Bug, Issue, Suggestion, General Feedback, or Other)
Describe the issue or idea in detail
Optionally attach a screenshot or file

Your submission is sent directly to the RITA team along with your server context so we can follow up quickly. No need to join a support server — just type /feedback and let us know.
## /help & !tr help have been reworked, Check it out! 
We've completely rebuilt the /help command from the ground up using Discord's latest Components V2 system — no more static embeds or dropdowns.

It will:

* Show a clean home screen with every command category and a live count of available commands
* Filter categories based on your permissions — you'll only see what you can actually use
* Let you browse commands page by page within each category, with Previous/Next navigation
* Show a detailed view for any command including its type, required permissions, usage examples, parameters, and subcommands
* Let you jump directly to a category with the topic option — no need to click through
* Every screen is fully interactive with buttons, and the menu automatically cleans up after 5 minutes of inactivity. 

All text is localised, so it appears in your server's configured language.
## Balance Command & More {% code overflow="wrap" %} ```javascript One of the promises we made when RITA was first created was that we would always do what we could for our users. That meant not raising costs unless absolutely necessary, always providing the best support we can, and never hiding functions or commands behind a paywall. As part of that commitment, we are working on a rewards programme for our users. This may change over time, but for now the details we can share are limited: * For each month you are a member of RITA and hold an active subscription, you will accumulate points * These points can be used to redeem free months of RITA usage * You can gift a one-month subscription to someone else or use it yourself ``` {% endcode %} ## Still to Come {% code overflow="wrap" %} ```javascript There are still a few more bits we want to do, for now here are a few of them DeepL support in all Object and Context commands Stripe integration work for the balance command User ability to decide if they want Deepl or Google to be used by default ``` {% endcode %} ## **Final Note** {% code overflow="wrap" %} ```javascript This update brings a mix of user-facing improvements, backend clean-up, database additions, and some early groundwork for future billing and engine support. while DeepL support is the biggest change you will notice, a lot of the work here has also been focused on making RITA easier to debug, easier to support, and easier for us to keep improving over time. that is all for now, but more is on the way, and we will share further updates as the remaining work is completed. ``` {% endcode %} {% hint style="success" %} That's it for now, but we will have some more info for you when we can. and if you want to check out all the changes made, dive into our change logs over in Version History From all the Development Team at RITA, See you soon. {% endhint %} --- # 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.ritabot.gg/ritabot-docs/updates/18-05-2026.md?ask= ``` 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.