> For the complete documentation index, see [llms.txt](https://csrpmoddocs.officialcaliforniastateroleplay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://csrpmoddocs.officialcaliforniastateroleplay.com/bot-commands/punishments.md).

# Punishments

Punishments are moderation records against **Roblox players**, not against your staff. Logging one stores it against the player's Roblox account, so their history follows them regardless of which Discord account they use.

`>punish` is the main entry point. `>search` (or `>s`) pulls up everything known about a player: their Roblox account, any warnings on file, and alerts such as a young account, few friends, an active BOLO or a Roblox ban.

A **BOLO** is a standing "be on the lookout" flag. Once one is active, it surfaces on every search of that player until it is removed.

Punishment types, logging channels and presets are configured on the [Punishments](/dashboard/moderation.md) dashboard page.

## Commands

| Command                   | Aliases                                         | Who can use it | What it does                                                |
| ------------------------- | ----------------------------------------------- | -------------- | ----------------------------------------------------------- |
| `>punish`                 | `p`                                             | Staff          | Punish a user                                               |
| `>punishment manage`      | —                                               | Staff          | Manage punishments                                          |
| `>bolo active`            | `search`, `lookup`                              | Staff          | View the server's active BOLOs.                             |
| `>punishment leaderboard` | —                                               | Staff          | View the server's punishment leaderboard.                   |
| `>tempban`                | `tb`, `tba`                                     | Staff          | Tempbans a user.                                            |
| `>punishment analytics`   | —                                               | Staff          | View punishment analytics overview for the server.          |
| `>punishment staff`       | —                                               | Staff          | View detailed punishment stats for a specific staff member. |
| `>punishment player`      | —                                               | Staff          | View punishment history and trends for a specific player.   |
| `>punishment top`         | —                                               | Staff          | View the top repeat offenders in the server.                |
| `>mywarnings`             | `mymoderations`, `mypunishments`, `moderations` | Everyone       | Lookup your punishments with CSRP Moderation.               |
| `>search`                 | `s`                                             | Staff          | Searches for a user in the warning database.                |
| `>userid`                 | `u`                                             | Everyone       | Returns the User Id of a searched user.                     |


---

# 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://csrpmoddocs.officialcaliforniastateroleplay.com/bot-commands/punishments.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.