Judgement before buttons

Your job is to stop harm, explain the boundary and help the conversation recover. Keep your tone calm, especially when the other person isn't calm.

Before taking action

1. Read the surrounding conversation. Check who said what, when it happened, and which server rule applies. A report is a starting point, not proof by itself.
2. Verify the person using their Discord user ID. Similar names and profile pictures can belong to different people. Turn on Developer Mode in Discord settings to access Copy User ID.
3. Preserve the minimum useful evidence: message links, channel, time and a short factual summary. If content must be removed immediately, contain the incident first and record what you safely can.
4. Check Warnings and Case history in Moderator Hall. A missing result does not prove there was never an incident: views are limited and older records may have expired under retention settings.
5. Coordinate with the moderator already handling it. Avoid two warnings or overlapping sanctions for the same conduct.
6. Choose a proportionate response. A quiet reminder may resolve an honest mistake; an ongoing attack may need immediate containment. You do not have to warn before every serious safety action.

While acting

Use an observable reason, verify the target and settings, then read Taffy's final receipt. Save the case number in the staff handover. A loading message is not a completed action.

After acting

Check that the harm stopped. Explain what needs to change without arguing in public. Offer a private route for questions and appeals. If you were personally involved, ask another moderator to review the decision.

Taffy does not automatically ban someone after a particular warning count. Do not invent a three-strikes rule. Apply the server's actual policy and consider severity, context and relevant history.