> For the complete documentation index, see [llms.txt](https://docs.invitelogger.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.invitelogger.me/advanced/messages/legacy-commands-deprecation.md).

# Legacy commands deprecation

As announced a few months ago, discord is will implement the [message ](https://support-dev.discord.com/hc/en-us/articles/4404772028055-Message-Content-Privileged-Intent-for-Verified-Bots)intent after April 30th 2022. It means that InviteLogger won't be able to receive messages from guild members after this date. \
This update will impact our services as well.\
\
**Legacy commands**, the ones with customizable prefix will be **shutted down** for the main InviteLogger. They will be **still available** on [**private bot instances**](/pbi/what-is-a-private-bot-instance.md). It means that the only way to use the bot past this date will be [slash commands](https://discord.com/blog/slash-commands-are-here).\
\
Also, some servers have refused the bot to create slash commands in their servers. They are now receiving a deprecation message requesting to re-invite the bot.![](https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2FbC5tT1Uy3HNPa1dtBHtD%2Fimage.png?alt=media\&token=7fd812b6-bbec-4167-b527-c5517ae3cf93)

And if you are still using legacy commands. you might see this message below regular command embeds\
![](https://1233429419-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MW_7KWGOtXaonSVC9Jd%2Fuploads%2F6eTifaPcHeQdWAnlahVE%2Fimage.png?alt=media\&token=7664caef-47e0-45cc-8fbd-dac3a2d13698)


---

# 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.invitelogger.me/advanced/messages/legacy-commands-deprecation.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.