Giving a warning

A warning is a recorded explanation of a rule breach. It should tell the member what happened and what to change, without insults or speculation.

Recommended workflow

1. Verify the member, context, evidence and rule.
2. Check existing warnings and recent cases. Make sure another moderator hasn't already handled this incident.
3. In Hall, choose Warn, find the member and write the reason.
4. Review the user ID and reason, then confirm once.
5. Read the receipt and record the case number. Taffy tries to DM the member the warning and reason.

Slash alternative: /warn member:@Member reason:Repeated personal insults in general after a reminder to stop. Please address the discussion without attacking other members.

The member mention is a placeholder: select the real member in Discord. A slash warning runs when submitted; it does not open the Hall's final review screen.

Useful reasons

• "Repeated off-topic promotion after a moderator reminder. Keep advertising to the channels allowed by the rules."
• "Continued targeted insults after being asked to stop. Disagree without attacking another member."

Avoid "bad attitude", "because I said so", or a list of private allegations. State the conduct and expected change. Put sensitive evidence and internal discussion in a separate private staff note.

Reasons are optional in the form and command, up to 500 characters. Blank reasons become "No reason provided." For proper staff records, fill the reason in.

Checking the result

Use Hall → Warnings or /warnings member:@Member. The slash view shows up to 15 active warnings; it is not a complete lifetime record. Use /case number:42 for the full stored reason.

If the receipt says the DM was not delivered but the case was saved, the warning already exists. Do not warn again to retry the DM. If appropriate, communicate the boundary through an existing private staff conversation.

If Taffy says the warning was not saved and no DM was sent, ask the bot owner to investigate before deciding whether to try again.