Evidence Bot Commands & Staff Workflows
Reference for Evidence Bot staff and member commands, access rules, case workflows, reminders and exports.
Evidence Bot Commands & Staff Workflows
Access overview
| Command | Access |
|---|---|
/evidence, /followup, /assigncase, /myqueue, /playerhistory, /linkappeal, /closecase, /reopencase, /casetimeline, /caseexport, /searchcases, /resolveappeal | Staff roles or Administrator. |
/casestats | Administrator by default in Discord; the runtime staff check also applies. |
/setpresence | Administrator only. |
/ping, /mycases, /checkappeal | Members. Results and output are limited to the caller. |
All responses are ephemeral. Autocomplete is restricted to staff, except /checkappeal, which suggests only the member's own tickets.
Staff commands
| Command | Options and behavior |
|---|---|
/evidence | Required: player_username, discord_username, reason, actions, status. Optional: evidence, attachment. Creates a report and stores its original details. |
/followup | Required: case_id. Supply at least one of note, new_evidence, update_status, or attachment. Stores notes, attachment metadata, and old/new statuses. Closed cases must be reopened first. |
/assigncase | case_id, reviewer. The reviewer must be a staff member. The assignment is recorded and the reviewer is mentioned in the thread. |
/myqueue | Downloads your outstanding assigned cases with forum links. |
/playerhistory | player: exact Minecraft name, UUID, or Discord user ID. Downloads all matching stored cases, including appeals and resolved cases. |
/linkappeal | case_id: the appeal. original_case: the original punishment or report case. Posts a link and records the relationship. |
/closecase | case_id, reason. Marks the case resolved, records the reason, and archives the thread. |
/reopencase | case_id, reason. Unarchives the thread, marks it pending review, and records the reason. |
/casetimeline | case_id. Downloads the recorded timeline as JSON. |
/caseexport | case_id. Downloads a text transcript of stored details, evidence references, follow-ups, links, assignments, and the timeline. |
/searchcases | query and/or status. Searches case IDs, names, UUIDs, Discord identities, ticket IDs, and filing staff. Up to 50 matches; the embed displays the first 10. |
/resolveappeal | case_id, decision (accepted, denied, pending), optional note. Records the decision. Pending appeals remain reviewable; accepted and denied appeals become resolved. |
/casestats | Status totals, recent months, and filing staff activity. |
/ping | Member command. Shows the Discord acknowledgement round trip, gateway heartbeat latency, and process uptime. |
/setpresence | Administrator only. status, optional activity_type, activity_name, activity_url. Changes the bot's presence for this process. |
/evidence player_username:ExamplePlayer discord_username:@ExampleUser reason:Repeated rule violations actions:Issued a seven-day ban status:Banned evidence:https://example.com/evidence
/followup case_id:ZC-MO44GYQC note:Reviewed the recording and confirmed the report.
/assigncase case_id:ZC-MO44GYQC reviewer:@ModeratorName
/resolveappeal case_id:ZC-MO44GYQC decision:accepted note:Appeal reviewed and accepted.
Prefer a Discord user ID or mention when recording identities. Legacy names are matched exactly, not by substring.
Member commands
/pingshows the caller the Discord acknowledgement time, gateway heartbeat latency, and process uptime — useful as a quick "is the bot alive and responsive" check for anyone, not just staff./mycasesshows up to ten cases associated with the member's Discord identity, including resolved records./checkappeal ticket_id:...checks the member's own appeal. Autocomplete suggests only their own tickets.
Follow-up notes may be visible to the matching appellant when they check an appeal. Write notes with that in mind.
Related guides
- Evidence Bot installation and setup
- Punishment imports and appeals
- Website addons
- Maintenance and backups
Command latency and responsiveness
/ping measures a single lightweight reply, not the duration of every case operation — a fast /ping doesn't guarantee every command is equally fast, just that the bot's connection to Discord is healthy. Commands that take at least five seconds are logged in the terminal for diagnosis, so a slow /caseexport or /searchcases on a large case store is something you can actually see and investigate.
A few things keep normal commands responsive: optional activity-log posts never delay the /evidence or /followup confirmation itself; a thread status change combines any changed tags and the thread name into one edit instead of several; and autocomplete reads lightweight case summaries rather than pulling full evidence, follow-ups, and timelines for every suggestion.
Review reminders
Once per minute, the bot checks assigned cases with statuses Pending, Appeal, or Suspicious. After the configured inactivity interval (REVIEW_REMINDER_HOURS), it mentions the reviewer in REVIEW_REMINDER_CHANNEL_ID or in the case thread.
- Successful reminders are saved and do not reset the case's last activity.
- Repeated reminders wait another full interval.
- Closed and resolved cases are excluded.
- Failed notifications are retried on the next check.
Evidence files and exports
Use the attachment option on /evidence or /followup to attach a screenshot or other file. The bot posts its Discord URL and stores its name, URL, size, and content type. Exports contain file references, not downloaded file contents.
Discord attachment URLs may expire. Keep original evidence in persistent storage when permanent retention is required.