Skip to content

Review player records

Read sanctions, reports and internal notes together without losing their context.

Records combines known information about a person in the selected server. A record does not mean that person has been sanctioned. Access requires sanction management.

Search by nickname or preferably Discord ID, use the relevant filters, and check the identity before opening or adding information. Synchronized Discord members may have records without sanctions; people who left can remain searchable.

The new-members filter concerns Discord arrivals during the past seven days, when their join date is known. It does not mean new staff members. Name-only records stay separate from Discord-ID records. Matching nicknames never merge people automatically.

  • A sanction is a recorded decision; it does not prove a Discord action ran.
  • A report is a situation to review, with its own resolution status.
  • An internal note provides context; it is not a sanction or staff warning.
  • Leaving Discord is distinct from leaving staff.
  • The repeat-offence indicator starts at two sanctions within thirty days. It invites review, not an automatic decision.
  • Account age alone is not evidence of misconduct.

If a module is unavailable, its corresponding data can be hidden with an explanation. Do not interpret that as a clean record. Use the previous and next page controls to browse the entire accessible timeline, including older events. Counts and the thirty-day indicator use the full record rather than just the current page.

Open the correct record, write the relevant context, dates, checks and evidence links, then add the note and verify it appears. Use factual wording rather than vague judgments. Deleting an incorrect note removes only that note, not its sanctions or reports.

Warning and sanction actions can prefill the target identity. Check the type, reason and duration. These use the panel’s recording flow; open the saved sanction and confirm Apply on Discord, or use the corresponding Discord command, then check the application result separately.

The /record command also presents accessible information in a personal Discord response. See commands and sanctions and reports.