> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/other-integrations/discord/create-a-discord-bot.md).
# 创建 Discord Bot
创建你自己的 Discord Bot，与不同服务器中的人分享。
按照以下步骤创建你自己的 Discord 机器人：
1. 导航到 [Discord 开发者门户](https://discord.com/developers/applications)
2. 点击 **新建应用**
3. 输入你想要创建的机器人名称。我们就用 **ConvaiTracy**
4. 接受开发者服务条款和开发者政策，然后点击 **创建**.
5. 现在，你会进入应用详情页面。上传应用图标，并按需提供描述。然后点击保存更改。
6. 然后点击 **OAuth2** --> **URL 生成**器
7. 点击 **bot** 复选框，位于 **Scopes** 部分下方
8. 在各项权限下方勾选以下复选框
1. 常规权限：
1. 管理 Webhooks
2. 文本权限：
1. 所有复选框
3. 语音权限：
1. 连接
2. 使用
3. 使用语音活动
4. 优先发言者
5. 请求发言
9. 复制下面生成的 URL。这将是该机器人在所有服务器上的可分享邀请链接。
10. 接下来点击 **机器人**
11. 点击 **添加机器人** --> **是的，就这么做！**
12. 在 **特权意图** 部分下允许以下意图，然后点击 **保存更改。**
13. 点击 **重置令牌** 以为机器人生成新的令牌。然后点击 **是的，就这么做**
14. **复制** 生成的令牌，稍后用于托管机器人服务器。
现在我们继续将 Discord 机器人与 Convai 角色连接，并托管服务器。
{% content-ref url="/pages/164c6c4f8dd87bc05eb88c0cc49438037a5c17d0" %}
[从个人服务器托管 Discord Bot](/api-docs/zh/cha-jian-yu-ji-cheng/other-integrations/discord/hosting-discord-bot-from-personal-server.md)
{% endcontent-ref %}
---
# 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.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/other-integrations/discord/create-a-discord-bot.md?ask=&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.
