> ## Documentation Index
> Fetch the complete documentation index at: https://bettertickets.gg/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How roleplay commands work in better tickets. Hugs, kisses and everything else, with reciprocation buttons, per-pair stats and opt-out/block controls.

Roleplay adds a set of anime-gif reaction commands (`/hug`, `/kiss`, `/slap` and more) that post a random image alongside a templated message and track how many times members have done each action to and with each other. It's entirely free and works both in servers and DMs.

## Enabling it

Configure it on the [dashboard](https://dashboard.bettertickets.gg/)'s Roleplay Config page. By default roleplay commands are enabled in a server until an admin turns them off. Running any roleplay command in a server where it's off replies telling the member it needs to be enabled first (or silently does nothing, if **Silent reply when disabled** is turned on).

## Running a command

Every roleplay command (`/hug`, `/kiss`, `/slap`, etc.) takes one option: the member to target. The bot picks a random image for that action, posts it with a message like "@**{target}**! **{author}** is hugging you." and updates stats for both members. You can't target yourself or a bot. As a text command, replying to someone and pinging them fills in the target automatically, without needing to type it.

Most actions require a target, but a set of solo commands (`/cry`, `/laugh`, `/dance` and more. See [Commands](/docs/roleplay/commands) for the full list) work standalone too: run one with no target for a plain reaction ("**{author}** is crying."), or with a target for a directed one ("@**{target}**! **{author}** is crying with you."). Solo commands don't track stats and never show reciprocation buttons.

## Reciprocation buttons

Most actions post two buttons under the message:

* **"{Action} back"**: Lets the target immediately do the same action back, posted as a fresh message. Only the target can click it.
* **Skip**: Lets the target decline. The bot posts a small "skipped it" reply with a sad gif and the buttons on the original message get disabled either way once one of them is used.

Some actions only get the back button (no skip) and a few low-stakes ones (like `/wave`) get neither.

## Stats

Two kinds of counters are tracked per member, shown automatically in the default message when they apply:

* **Mutual count**: For affectionate, reciprocal actions (kiss etc.), how many times a specific pair of members have done that action together, regardless of who started which one.
* **Received count**: For one-directional actions (slap, kick, bonk, etc.), how many times a member has had that action done to them by anyone.

## Opting out and blocking

Any member can run `/opt out` to stop being targetable by roleplay commands entirely (across every server) and `/opt in` to allow it again. `/roleplay block` lets a member block a specific person from targeting them (and from being targeted by them) without opting out of roleplay entirely. Up to 500 blocked users at a time. `/roleplay unblock` reverses it and `/roleplay blocklist` shows your current block list.

## Customizing the message

Premium servers (any tier) can override the default message and footer text from the dashboard's Roleplay Config page, using the same [templating syntax](/docs/variables) as tickets and applications, plus roleplay-specific variables like `{{verb}}` and `{{rp.animeName}}`. The same message template handles both cases for solo commands. Use `{% if target.id %}...{% else %}...{% endif %}` to control what's shown with versus without a target. See [Variables](/docs/variables#roleplay) for the full list. Free servers and any premium server that hasn't set a custom message, use the built-in default wording.

See [Commands](/docs/roleplay/commands) for the full command list and [Roleplay settings](/docs/roleplay/settings) for a field-by-field reference of what's configurable.


## Related topics

- [Overview](/docs/leveling/overview.md)