> 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/pbi/get-pbi/setup-your-private-bot-instance.md).

# Setup your private bot instance

You've bought your private bot instance on our [store](https://invitelogger.tebex.io/) ?\
It's time to setup your order.

### 1 - Create your discord bot

{% hint style="warning" %}
Before creating your own bot instance, make sure the bot will be created on a "safe" account. \
If your discord account is deleted, the bot will be deleted too.
{% endhint %}

To create a discord bot you need to login on the discord dev portal: <https://discord.com/developers/applications/>

And click on the create application button

![](/files/-MdgnTZ_q3qgCA4L_3X1)

Put your bot name **(Please don't use a public invite bot name / profile pic)** and click on the create button.

![](/files/-Mdgo2BUiQ0FNyfNgO2v)

Once created you will see something like this:\
Copy the Application id and send it to chaun14.&#x20;

![](/files/-MdgpCa0FU0JovNq0AA4)

Once the application created, you need to create a bot inside your application.

![](/files/-MdgwlnJqoPqBhb-yyvE)

![](/files/-MdgwqJzz7tROfrM65yd)

Put your bot name and eventually a profile pic

![](/files/-MdgxZ9MZZFopWSBmnfe)

And tick the three intents at the bottom of the page to make sure the bot works.\
✅ Presence intent\
✅ Server members\
✅ Message

<div align="right"><img src="/files/-Mdgzh1_uB0ahJERMEXb" alt=""></div>

Once everything is done, scroll up and copy the token, then send it to chaun14.

![](/files/-Mdh0QNd5Nid2mFN5ncT)

### 2 - Customize your bot instance.

The bot itself is now ready to be started, we just need more informations about customization.<br>

#### A - Embed color

Go to this page: <https://www.google.com/search?q=color+picker> and choose an embed color (should be related to your server brandings)

![This color will be on the left bar of embeds](/files/-MeLylg_e_nlIGNHKRzs)

Once the color is selected, copy the HEX code. (i.e **#4287f5**) then send it to chaun14.

#### **B** - Bot activity / status message

Each bot has a status / activity. It represent your bot identity and is a great advantage for your server.

![Example of activity](/files/-MeM-Py-MgcwXvdYzPiG)

You need to provide a status message for your bot, it could be your server name, a domain name, a private joke...

The bot is in a streaming state by default, it's possible to request [something else](https://abal.moe/Eris/docs/Client#method-editStatus).\
\
Once choose, send it to chaun14.

{% hint style="warning" %}
Please note the `| tag for help | s0` at the end of the status message can't be edited
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.invitelogger.me/pbi/get-pbi/setup-your-private-bot-instance.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.