# leave/goodbye embed

### ✎ step one

* create the embed by using `/embed create name:leave_embed`
* you can name the embed anything you'd like, however we strongly recommend naming it something simple and easy to remember.

### ✎ step two

* now we can edit the details of our embed to our liking!
* remember : you can either outright use these edit commands, or use the buttons + modals from creating your embed to have an interactive text form.
* edit the author to the user's avatar and name/tag by using `/embed edit author embed:leave_embed text:{user_name} icon:{user_avatar}`
* edit the title by using `/embed edit title embed:leave_embed title:goodbye!`
* edit the thumbnail to the user's avatar by using `/embed edit thumbnail embed:leave_embed image:{user_avatar}`
* edit the description of the embed to `/embed edit description embed:leave_embed description:oh no!`

  `it looks like {user_name} has left us :c`

  `we now have {server_membercount} members`

{% hint style="warning" %}
Discord on PC/Desktop/select devices **do not** allow new lines in slash commands. If you're looking to have new lines/better spacing in your embed, we recommend either going through the text modal OR using the `{newline}` variable in place of where you want a new line to start.
{% endhint %}

* you can add a timestamp by using `/embed edit timestamp embed:leave_embed timestamp:True`
* edit the footer of the embed by using `/embed edit footer embed:leave_embed text:we now have {server_membercount} members. . .`
* edit the color of your embed by using `/embed edit color embed:leave_embed color:#feeee8`
* lastly, you can edit the image of the embed by using `/embed edit image embed:leave_embed image:`[`https://tenor.com/view/puffybear-puffy-face-cute-bye-gif-12628645`](https://tenor.com/view/puffybear-puffy-face-cute-bye-gif-12628645)
* if you followed this, you should get something like:

![a completed leave message embed](https://1355643618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjUSz3NQrpyR-tHhUV-%2Fuploads%2FDIkazxwkC7BFtZLGUxOt%2Fleavemsg.PNG?alt=media\&token=84903885-7506-4d2d-886a-ee40b639dcfb)

### ✎ step three

* now that you have a leave embed, we can set the leave message & channel!
* set your leave message by using `/set leave message message:oh no. . . bye, {user_tag} {embed:leave_embed}`
* make sure that mimu has full permissions to send the embed to the channel you want the message to be sent to, then run\
  `/set leave channel channel:#channel`

### ✎ step four

* we can test our leave using `/test leave`
* testing our leave should yield the results below ::

![our finished leave message!](https://1355643618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LjUSz3NQrpyR-tHhUV-%2Fuploads%2FdWCwIuQcsbqYKh3UQGMB%2FCapture.PNG?alt=media\&token=57f91b11-cf90-4210-bc37-01598ed56b03)

{% hint style="warning" %}
if mimu *doesn't* send the leave message to the channel, it means it has no permissions to do so. you can check by using `/ping` in the leave channel and seeing if it responds. no response = no permissions.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.mimu.bot/embeds/embed-guide/leave-goodbye-embed.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.