Calm, consistent moderation.
Commands, automod, modlogs, notes, Sentinel, permissions and escalation for the Relics moderation team.
Vör Overview
The moderation bot, its command types and its dashboard.
Vör is the moderation bot (dashboard powered by PC Help Hub). It has three kinds of commands: /slash commands, right-click menu commands on a message or user, and !tags (text blocks).
Sentinel Moderation Message Logger Tickets (enabled, no panels yet) Verification off Reputation off
Support tickets run through Tickety. Vör's own ticket module is enabled but has no panels yet.
Dashboard tabs
Punishment Workflow
Check history, escalate step by step, and hand bans to leadership.
The ladder
- Check history.
/modlogs @userand/notes @user. - Warn for first or minor issues.
/warncreates a case and DMs the user. - Mute for repeat or disruptive behaviour, with a duration.
- Kick for serious issues where the user could still rejoin properly.
- Ban is leadership only. Send them the user ID, case numbers and screenshots.
Hacked account or scam
/comped is disabled. Mute right away, delete the messages with /purge, then tell leadership.
Ban appeals
Banned users get a DM with an appeal form. An appeal never guarantees an unban. Don't discuss appeals in DMs.
Action commands
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/warn | Warn a user. Creates a case and DMs them. | Moderator | First or minor rule break. | /warn @user spamming in #general |
/editwarn | Change a warning reason by case number. | Moderator | Typo or wrong reason. | /editwarn 12 new reason |
/mute | Timeout / mute for a set duration. | Moderator | Disruption, repeat offence, scam spam. | /mute @user 1h arguing after warning |
/unmute | Lift a mute early. | Moderator | Mistake or user calmed down. | /unmute @user |
/kick | Remove from the server (can rejoin). | Moderator | Serious issue, not ban-worthy. | /kick @user ignoring staff |
/ban, /unban | Permanent or timed ban, and unban. | Leadership / admin (Moderator has no Ban permission) | Hand over with evidence. | Ask leadership |
/comped | Softban + mute for hacked accounts. | Disabled | Not available. Mute and purge instead. | n/a |
/purge | Bulk delete messages. | Moderator | Scam waves, spam cleanup. | /purge 50 @user |
/slowmode | Set channel slowmode. | Moderator | Heated or flooded channel. | /slowmode 10s |
/lock, /unlock | Lock or unlock a channel. | Moderator | Raid or major incident. | /lock |
/setnick | Change a nickname. | Senior Specialist (has Manage Nicknames), not Moderator | Offensive or unpingable name. | /setnick @user New Name |
/dm | Message a user through the bot. | Admin / Leadership (no role set in Vör) | Official staff notice. | /dm @user text |
/rolepersist apply | remove | list | check | Keep a role on a user for a period. | Moderator | A role must stick. | /rolepersist apply @user Mute 7d |
/moderation preset add | delete | list | Reason templates. | Moderator | Same reasons used often. | /moderation preset list |
/moderation list_muted_users | check_muted_users | List or clean up mutes. | Moderator | Audit active mutes. | /moderation list_muted_users |
Modlogs, Notes and Alts
Look before you act, and leave a trail for the next moderator.
Cases and lookups
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/modlogs @user | All cases incl. Dyno and Circle history. | Moderator, Senior Specialist | Before any action. | /modlogs @user |
/mymodlogs | Your own cases. | Moderator | Review your actions. | /mymodlogs |
/case [number] | Details for one case. | Moderator | Check or quote a case. | /case 12 |
/reason, /duration | Change reason or duration afterwards. | Moderator | Fix a case. | /reason 12 new text |
/whois, /uinfo | User lookup. | Moderator, Tech Team, Junior, Specialist, Senior | Account age, roles, history. | /whois @user |
/modstats, /modactions | Statistics, and actions between two dates. | Moderator | Team reporting. | /modstats |
/moderation leaderboard | Ranking of mods by actions. | Moderator | Activity review. | /moderation leaderboard |
/moderation modlog_deduplicator | Find and delete duplicate cases. | Leadership / admin | After a data import. | Ask leadership |
/moderation share_modlogs_with | Share modlogs with another server. | Leadership / admin | Cross-server cooperation. | Ask leadership |
Notes
Notes work in the configured notes channel. Specialists can add notes but cannot see notes written by moderators. Notes carry a type, and come from Vör, Circle and Dyno.
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/note add @user text | Add a note. | Moderator and advisors | A pattern worth remembering. | /note add @user suspected alt |
/notes @user | List notes. | Moderator | Before acting. | /notes @user |
/note edit | delete | clear | transfer | Manage notes. | Moderator | Correct or move notes. | /note edit 3 text |
/note type | info | help | Note types and details. | Moderator | Categorise notes. | /note info 3 |
Right-click: Show user notes / author notes | Quick lookup. | Moderator | From a message or user. | Right-click a user |
Alt tracker
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/alt link @a @b | Link two accounts. | Moderator | Confirmed alt. | /alt link @main @alt |
/alt unlink | Remove a link. | Moderator | Linked by mistake. | /alt unlink @a @b |
/alt show @user | Show linked accounts. | Moderator, specialists | Ban evasion check. | /alt show @user |
/alt all | List all linked accounts. | Moderator | Overview. | /alt all |
Automod and Sentinel
What the bot catches on its own.
Automod rules
Category "Automod"
- 3 violations in 60 s triggers the punishment (delete only).
- @everyone / @here mentions.
- Message spam: 5 messages in 10 s.
- Crosspost spam: 3 channels in 5 s.
Category "Anti Role Ping Specialists"
- Applies to Junior Specialist, Specialist, Senior Specialist and Tech Team.
- Pinging a support role gives a 1-minute timeout and a note to use the support channels.
- Alerts go to
#message-logswith a Mute button.
Sentinel
Sentinel recognises known scam images by hash, perceptual hash and OCR. Currently 0 signatures are stored. With strict_ocr off, an OCR hit only posts an alert embed and does not time the user out.
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/sentinel add_image | Store a scam image (sha256 + pHash). | Moderator | A new scam image appears. | /sentinel add_image |
/sentinel list | remove | sync | View, remove, share across servers. | Moderator | Maintain the signature list. | /sentinel list |
/sentinel diagnose | Test OCR on an image. | Moderator | Why was an image missed? | /sentinel diagnose |
/sentinel automod channels | category | rule | Configure where and how automod runs. | Leadership / admin | Changing rules. | Ask leadership |
/sentinel selfalert add | remove | list | Personal keyword alerts by DM. | Moderator | Watch a scam phrase. | /sentinel selfalert add keyword |
/sentinel ocrgate | ocrkeywords | OCR sensitivity and keywords. | Leadership / admin | Tuning detection. | Ask leadership |
Other protection
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/honeypot deploy | stats | help | config | Trap channel: posting there triggers an action. | Moderator | Catch spam bots. | /honeypot stats |
/moderation honeypot_stats | Users removed by the honeypot. | Moderator | Review the trap. | /moderation honeypot_stats |
/name_enforcement view_config | scan | help | Enforces pingable nicknames. | Moderator | Unreadable names. | /name_enforcement scan |
Virus Total (automatic) | Scans attachments. | Automatic | Investigate alerts. | n/a |
Bot Case Listener (automatic) | Records cases from other bots. | Automatic | No action needed. | n/a |
Logs and Tools
Message and audit logs, giveaways, panels and role tools.
Logging
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/messagelog incidents | stored-message | info | help | Edit/delete logs and purge incidents. | Moderator | Someone deleted evidence. | /messagelog incidents |
/messagelog purge-messages | purge-events | purge-all | Permanently delete log data. | Manager only | Do not use. | n/a |
/audit vcactivity @user | Voice activity of a user. | Moderator | Voice harassment. | /audit vcactivity @user |
/audit config | help | Audit log settings. | Leadership / admin | Changing logging. | Ask leadership |
Events and panels
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/giveaway create | end | reroll | list | Run giveaways. | Events / Moderator | Community events. | /giveaway list |
/panel create | edit | list | delete | config | Button panels (e.g. role toggles). | Leadership / admin | Changing panels. | Ask leadership |
Users and roles
These can affect hundreds of members. Do not use mass-kick or kick-all.
| Command | Purpose | Who may use it | When to use | Example |
|---|---|---|---|---|
/user no-role count | list | Members without a role. | Moderator | Review new joins. | /user no-role count |
/user no-role kick-all | Kick all roleless members. | Leadership only | Never. | n/a |
/role add | remove | list | audit | Manage role membership. | Leadership / admin | Role changes. | Ask leadership |
/role mass-kick | Kick everyone with a role. | Leadership only | Never. | n/a |
/gate ... | Entry gate settings. | Leadership / admin | Raid protection setup. | Ask leadership |
/tenure, /tenure_reminder | Member tenure tracking. | Leadership / admin | Retention. | Ask leadership |
Permissions
What each role can do, in Discord and in Vör.
Discord role permissions
From the Discord role settings. Everything not shown is off. All members can send messages, react and attach files.
| Permission | Moderator |
|---|---|
| Kick members | Yes |
| Ban members | No |
| Timeout members | Yes |
| Manage messages | Yes |
| Manage nicknames | No |
| Pin messages | No |
| Manage threads and posts | No |
| Bypass slowmode | No |
| Mention @everyone / @here | No |
| Voice: mute | Yes |
| Voice: deafen, move | No |
Moderators can
Warn, mute, kick, delete messages and purge, look up users, use notes, modlogs and the alt tracker.
Moderators cannot
Ban, change other people's nicknames, pin messages, or ping @everyone. Escalate those to leadership.
Vör settings by role
| Setting | Allowed |
|---|---|
/warn, /mute, /kick, /rolepersist | Moderator |
/ban | No bot role configured. Needs the Discord Ban permission, which no role below leadership has. |
/comped | Disabled |
/whois, /uinfo | Moderator |
/modlogs (view) | Moderator |
Delete modlogs | Server admins only |
Notes (including mod notes) | Moderator |
Dashboard | Tier 1: Moderator. Tier 2: leadership roles. |
Vör stores roles as ID numbers only. The names above were matched by ID and should be re-checked if roles are rebuilt.
Cog Directory
Vör's modules. 26 are active and 11 are disabled.
The dashboard Overview page shows 31 of 42 because it also counts sub-features. Vör has 351 commands: 266 active and 85 disabled (as of 11 Nov 2026).
| Cog | Purpose | For |
|---|---|---|
| Moderation | Warn, mute, kick, ban, modlogs (40 commands). | Core |
| Notes / Alt Tracker | User notes and linked accounts. | Core |
| Vor Sentinel | Scam-image detection and automod. | Core |
| Message Logger / Audit Logger | Edit and delete logs, channels, roles, members, VC, timeouts. | Core |
| Honeypot / Name Enforcement | Spam trap, pingable nicknames. | Core |
| Autoresponder | Keyword auto-replies. | Info |
| Tags / Reminders / Misc Functions | Text blocks, reminders, /ping, /timestamp, /say, /close_thread, temp VC. | Everyday |
| Tickets | Vör tickets (enabled, no panels yet). | Info |
| PCPP / PSU Tier List / Drop Reference / FRST Utils | Build, price and log helpers. | Support |
| User Management | Roles, gate, tenure. | Leadership |
| Giveaways / Panel / Configuration / Bot Data Scraper | Events, panels, config, imports from Circle and Dyno. | Leadership / admin |
| Fun Economy / Currency Conversion | Coins, casino, /currency. | Fun |
| Bot Case Listener / Virus Total | Background scanners. | Automatic |
Disabled
Voting Starboard Tiers Verification RPGCog Minecraft Reputation Forms Reports RoleLink Suggestions
Disabled cogs do nothing. Don't promise them to users.
Escalation and Conduct
Who to tell, and how to behave while moderating.
Conduct
- Be consistent and fair. Check history first.
- Don't use moderator tools on yourself or friends. Hand it to another Moderator.
- Never share modlogs or notes outside staff.
- The strike system and activity rules apply to you too.
Staff Policies
The rules every staff member agrees to.
Use of AI
While AI tools can be valuable resources for assisting with technical support, they should be used responsibly and in moderation.
Guidelines
- AI may be used as a supplementary tool for research only.
- Direct copying of AI-generated responses is prohibited.
- Your own technical knowledge should always be the primary resource.
Remember that while AI can provide helpful suggestions, our goal is to offer human-to-human support with personal attention to each user's unique situation.
Payments and Tipping Policy
Payments are not permitted. No paid work, commissions, paid 1-on-1 services or price negotiations of any kind through this server.
We appreciate that users may wish to reward exceptional service. However, to maintain professionalism and fairness, strict guidelines apply to accepting gratuities.
Permitted
- Accepting a tip only if explicitly offered by the user first.
- Communication via the ticket channel.
- Communication via DMs only with prior permission from Senior Staff+ (SR+).
Prohibited
- Soliciting or asking for a tip.
- Setting a price for support services.
- Requesting a specific amount.
Any specialist found requesting tips, setting prices, or negotiating amounts will be issued TWO strikes on a first offense, which can lead to removal from the team. Our support services are free; tipping is entirely optional and user-initiated.
Personal Information Policy
Specialists must refrain from asking users for personal information including but not limited to:
In order to preserve the user's privacy and uphold strict ethical standards, specialists must avoid collecting any personally identifiable information unless absolutely necessary and explicitly consented to.
Prohibited information requests
- Full name or any identifying aliases
- Physical address or location details
- Phone numbers
- Email addresses
- Identification numbers (SSN, etc.)
- Financial information
Specialists must prioritize user privacy and only request information that is strictly necessary for the technical support task at hand. Any requests for personal information must be justified by absolute necessity and require explicit user consent.
Promotions
Our promotion system is designed to recognize and reward staff members who demonstrate consistent excellence in their roles.
Junior Specialist → Specialist
- After taking several tickets and remaining active, Senior Staff+ will schedule an "Observation".
- Senior Staff will complete an observation form evaluating your performance.
- Promotion decisions are based on this formal evaluation.
- Demonstrate consistent activity and quality responses.
- Complete an introduction in
#specialist-introsincluding: your name/nickname, where you're from, your areas of technical expertise, and why you joined the support team.
Specialist → Senior Specialist
- Consistently high user satisfaction ratings.
- Demonstrated leadership within the team.
- Active participation in community discussions.
- Willingness to mentor junior staff members.
- Consistent activity over an extended period.
Promotions beyond Specialist are evaluated based on overall contribution to the community, not just quantitative metrics. Leadership qualities, technical expertise, and dedication to helping others are all considered.
Inactivity Policy
To maintain an active and responsive support team, we require all staff members to remain engaged with our community.
Activity requirements
- If you do not participate in the server in a 14 day period without warning, you can be given a strike, demoted, or removed.
- Participation in community discussions is encouraged.
- Extended absences should be communicated to leadership.
A staff member hasn't responded to any tickets or participated in server discussions for 3 weeks without notice. After attempts to contact them go unanswered, they would be subject to removal from the staff team.
We understand that real life takes priority, so communication about availability is always appreciated and will be taken into consideration.
Three Strike System
To maintain high standards of professionalism and service quality, we employ a three-strike system for policy violations.
First strike
Cause: First-time violations (e.g., breaking rules, unprofessional behavior, misuse of AI, soliciting or requesting a tip)
Result: Formal warning.
Duration: 14 days.
Second strike
Cause: Repeating violations, soliciting or requesting a tip
Result: Temporary restrictions & leadership review.
Duration: 14 days.
Third strike
Cause: Continued violations.
Result: Removal from staff team.
Appeal: After 30 days.
Severe violations may skip the strike system entirely and result in immediate removal at the discretion of leadership. All strikes expire after 14 days if no further violations occur.