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

# V1.2.4

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

Dev only Command handler has been added in to enable fast changes to command restrictions.

### Bug Fixes

* Lots of little things, nothing of consequence.

### Command Changes

* `!tr history` shows Development History of the bot.
* `!tr stats server [ServerID]` shows stats for the targets server.
* `!tr blacklist [ServerID]` Blacklists a server (Developers Only).
* `!tr unblacklist [ServerID]` un-Blacklists a server (Developers Only).
* `!tr warn [ServerID]` Warns a server (Developers Only).
* `!tr unwarn [ServerID]` un-Warns a server (Developers Only).
* `!tr eject [ServerID]` Removes RITA from the target server (Developers Only).
* `!tr check [ServerID]` Checks Warn & Blacklist status of the given server.
* `!tr checkperms [bot/user]` checks permissions of the bot and the user for RITA compatibility.

### Database Changes

* A new column has been added to manage blacklisting and Warning, backwards compatible to all previous versions.

### Misc. Changes

* Once again Zycore broke something (a lot of times) Zycore fixed it again.
* Help muenus update with new commands.
* Help menus has been reworked, Still a work in progress but they look much better now.


---

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