1
Use Commands Carefully
These commands affect users view of the server and moderation records. Always verify the target user and reason before executing any action.
Getting Started
Rebirth AI Staff Command Guide
Internal documentation for staff moderation and support commands used across the Rebirth AI ecosystem.
2
Prefer Clear Reasons
For moderation commands, include concise but specific reasoning so other staff can audit actions later. Good reason strings improve transparency and reduce appeal friction.
3
Follow Staff Procedure
Use lookup, warn, mute, kick, and ban commands in line with internal policy.
Staff Commands
⛔
/ban (user) (reason)
Permanently bans a user from the system or community context covered by the command.
/ban quick1ee Severe harassment in support tickets
↩
/kick (user) (reason)
Removes a user without applying a permanent ban. Best used for immediate removal where a full ban is not necessary.
/kick quick1ee Repeated disruption after warnings
🔇
/mute (user) (duration) (reason)
Temporarily mutes a user. Duration supports 1w / 1d / 1h / 1m / 1s style values, with a maximum mute length of 28 days.
/mute quick1ee 12h Spamming AI generation requests in public channels
⚠
/warn (user) (reason)
Issues a formal warning to a user. Use when behavior should be logged without immediate removal or mute escalation.
/warn quick1ee Inappropriate use of staff ping
🧹
/removewarn (user) (warn number)
Removes a specific warning from a user record.
/removewarn quick1ee 2
📋
/viewwarns (user)
Displays the warning history for a user so staff can review prior moderation actions.
/viewwarns quick1ee
🔍
/userlookup (discord_user) (hidden)
Looks up a user inside Rebirth’s database. If the command fails, instruct the user to run /link <roblox username> to properly link their account before retrying.
/userlookup @quick1ee true
🎫
/ticketautodelete (true/false)
Provides visual reassurance that staff will return to a ticket. This exists because a ticket was accidentally closed and blame got thrown at the bot, so this command helps avoid confusion.
/ticketautodelete true
✉
/message-send (channel) (content)
Sends a message to a specific channel. This has a narrow, deliberate use-case and should not be treated like a generic chat shortcut.
/message-send #announcements Scheduled maintenance begins in 10 minutes.
✨
/echo (content) (special effect list)
Booster-only command that staff can access. Sends custom content with a selectable special effect.
/echo Welcome to the update preview confetti
Staff Channels
Key Staff Channels
Primary staff-facing channels and their intended use. Use the correct channel to keep workflows predictable and auditable.
💬
#moderator-chat
The primary staff discussion channel for coordination, questions, and quick decisions. Keep broader context here and avoid posting sensitive logs.
🧠
#staff-ai (internal)
Private staff-only AI assistant that provides concise, context-aware help based on roughly the last hour of server activity.
🤖
#botstuff
Use this channel to run and test bot commands without cluttering moderator chat. Ideal for lookups, command testing, and ephemeral bot interactions.
🧠
#ai-mod
Logs and diagnostic output from the Rebirth AI moderation system. Use for reviewing automated moderation decisions and tuning models.
🔗
#invite-logs
Records invite creation and usage events. Useful for tracing invite abuse and tracking onboarding sources.
⚙️
#automod-logs
Captures Discord built-in automod actions and matches. Review here before taking moderator escalation actions.
📜
#rebirth-logs
Centralized log channel for moderation actions performed by staff and bots. Reference this for audit trails and appeals.
🧾
#ticket-transcripts
Stores full ticket transcripts (HTML) including timestamps, open duration, and resolution notes. Reference when reviewing past support cases.
Operational Notes
Important Internal Notes
These notes are intentionally surfaced in the same card-driven format so staff can scan them quickly.
!
Obsolete Backup Commands
/staff-tagcheck and /procheck are obsolete. They are only retained as backups and should not be used during normal operations.
i
Best Practice
Keep moderation reasons legible. Future staff reviewing the log should understand the action without needing to reconstruct context from chat history.