> For the complete documentation index, see [llms.txt](https://mango-5m.gitbook.io/mango5m-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mango-5m.gitbook.io/mango5m-docs/resources/mango-admin/features/bans-and-kicks.md).

# Bans and Kicks

The record, offline bans, and what a removed player sees.

## The record

Every ban carries a short sequential number — **#0007** — that staff and players can quote at each other, with a copy button next to it. The list shows who, why, by whom, when, and when it expires.

Kicks are recorded too. The newest 500 are kept, which is what lets the panel tell somebody on their way back in that this is their third offence.

## Banning

From a profile, the roster, the mini menu, or by identifier alone for somebody who is not connected. A ban matches on **every identifier** the person held when it was issued, so coming back on a new licence with the same Discord is still caught.

How long a ban may be is capped by the role that issues it — `ban.maxDays`, most generous role wins, `-1` for unlimited.

## What they see

A disconnect screen with the reason, the expiry, who did it, the ban id and where to appeal — and the whole thing copied to their clipboard so they can paste it into a ticket instead of describing it.

## When they come back

The screen blurs and a card explains what happened, with **Continue** dead for five seconds so it cannot be clicked past. It says which offence this is, counting kicks and bans together across every identifier they hold.

{% hint style="info" %}
**Bans are enforced even while the panel is stopped.** The connection check lives in the panel, so stopping it would otherwise be the simplest way to walk a banned player back in. The watchdog holds the door instead, reading the panel's own ban file. See [While the Panel Is Down](/mango5m-docs/resources/mango-admin/resource-protection/while-the-panel-is-down.md).
{% endhint %}