# Toxicity Reports

<mark style="color:$warning;">**Has the reported player broken any rules?**</mark>\
We will always encourage our players to make a report ticket, even if it turns out the reported player did NOT break a rule, when a ticket is made it is our duty to guide, explain, determine, and if needed, take action.\
The best way to check if a rulebreak happened, for example in chat, first of all, is to seek out proof, either from the reporting party, or if possible, check the discord logs if the reported player deleted their messages to avoid detection.\
When you have received proof, either from the reporting party or in logs, check the quicktables and/or the chat rules in the player guide, or ask a fellow member of staff if you are uncertain if a rule has been broken.\
Once you have determined if a rulebreak happened, there are 2 ways it can go.

<mark style="color:$warning;">**The player DID break a rule.**</mark>\
Based on this answer, the next step is to check if this player has previous punishment history within the server, see the guide under ‘’Timing Out’’.\
\
\- If the answer to this is **YES**, see the ban tables and ban stacks also found under ‘’Timing Out’’, go up a step on the ladder and perform correct proof and logging of the ban.\
\- If the player has **NO** previous history and this is a first offense, determine the severity of what was said, and follow the quicktable as advised, perform the correct proof and logging of the ban.\
\
After the incident has been controlled and logged, inform the reporting party the situation has been handled, you cannot tell the reporting party what action you took, due to our player privacy protection. (for example: how long you timed someone out.)\
Once complete, ensure the reporting party has nothing else they need assistance with, and close the ticket.

<mark style="color:$warning;">**The Player DID NOT break a rule.**</mark>\
After checking the community rules and the quicktables and perhaps fellow staff members, you may find that this player did not break any rules.\
From here, you would go ahead and tell the reporting party that while their report is appreciated, no rules were broken, and do elaborate why, so they are not left in confusion as to why something that seemed like a rulebreak, was not a rulebreak.\
Sometimes ‘’no rules were broken’’ is not what the reporting party wants to hear, and in this case, it is wise to advise the reporting party to **block** the person they reported.\
This way they can ensure they avoid future interaction and negative experiences.\
Once you have offered your explanation and ensured the reporting party feels heard and properly informed, you can go ahead and close the ticket.\
\ <br>


---

# Agent Instructions: 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:

```
GET https://staffdocs.zoomingislander.lol/timing-out/toxicity-reports.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.