> 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/reports.md).

# Reports

A real conversation with the player who asked for help.

A player types `/report <message>` and gets a window with a thread in it. Staff reply from the Reports page, and the conversation stays in one place until it is closed.

## The queue

Open, closed, and the ones nobody has looked at yet. A report shows who opened it, when, what it is about, and whether anyone has replied.

## Inside a report

|                      |                                                                               |
| -------------------- | ----------------------------------------------------------------------------- |
| **The conversation** | Everything said, by everybody, in order                                       |
| **Staff notes**      | Messages the player cannot see, for talking among yourselves                  |
| **Attachments**      | The players and vehicles this report is *about*, separate from who is talking |
| **Participants**     | Who is in the thread, and who added them                                      |
| **The clip**         | The seconds before they pressed report, if clips are on                       |

Naming somebody as **reported** is a moderation act and is kept separate from **attaching** them, which is just staff keeping notes.

## Mentions

Type `@` to offer the people on the server — by player name, character name or id, with fuzzy matching so a half-remembered name still finds them. Plates match fuzzily too, because a plate read off a screen is the most misremembered thing in any report.

## Clips

With clips enabled the player's client keeps a rolling buffer, so the video covers what happened **before** they pressed the button rather than the aftermath. It uploads in paced pieces so a long clip cannot saturate your event budget, and the thread shows it inline with a copy-link button.
