> For the complete documentation index, see [llms.txt](https://hellbot-docs.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hellbot-docs.gitbook.io/docs/changelogs/version-0.4.md).

# Version 0.4

Released: August 01, 2021

## :rocket: *<mark style="color:red;">**Hêllẞø† α - 0.4**</mark>*

* Fixed and Updated Gban & Gmute.
* Added GPromote & GDemote. Check out `.plinfo globals` .
* Updated `.promote`. Now users will get promoted with `Voice Chat Rights` too.
* Added new plugin `voice_chat`. You can `Turn On` & `End` & `Invite Users` by giving command to userbot. Do `.plinfo voice_chat` to know more.
* Fixed `.repo`.
* Updated and added new Spam Commands. Added new spam command `.uspam` and `.bspam`. Do `.plinfo spam` to know more.
* Bigspam now spams the replied message.
* Fixed `memify`.
* Added new plugin `protecc`. Do `.plinfo protecc` to know more.
* Added `Auto Waifu Catcher`. To activate this you need to set up a heroku var. Do `.set var WAIFU_CATCHER TRUE`.
* Updated and fixed `.ss`. Now you can quote a bot's message too.
* Updated `telegraph`. Some users were having trouble copying telegraph links as it was in hyperlink format. Now you can tap to copy the telegraph link.
* Did some improvements for future updates. ( Maybe Assistant )
* Bug fixes.


---

# 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://hellbot-docs.gitbook.io/docs/changelogs/version-0.4.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.