Skip to main content

Leave Messages

Leave messages use the same configurable-message pattern as welcome messages: choose a destination channel, edit the content/embed, test the result and remove the configuration when you no longer need it.

  1. Set the destination with /config leave channel.
  2. Open/view the leave message editor.
  3. Configure message content and optional embed fields.
  4. Insert supported member/server variables.
  5. Run /config leave test.
  6. Use the remove action when you want to disable leave messages.

Variables​

Leave messages use the member/server placeholders documented in Message Variables, including values such as the member tag/avatar and server name/icon/member count.

A user who has already left cannot be interacted with in the same way as an active member, so build the message around readable identity/context rather than depending on an actionable mention.

Design tips​

A useful leave message is normally shorter than a welcome flow. Common uses are:

  • a simple departure notice;
  • current member count;
  • a branded embed/avatar;
  • a staff-visible record in a dedicated join/leave channel.
tip

Use /config leave test after changing the destination channel or embed URLs. It verifies presentation and Discord permissions without waiting for an actual member departure.

Troubleshooting​

Nothing is sent​

Confirm the saved channel still exists and Kakashi can view/send there. If an embed is configured, check Embed Links as well.

A variable is printed literally​

Use only variables supported by the welcome/leave renderer. Ban-message variables such as {reason} are not automatically valid here.