Warn members and manage warnings

Use /admin to issue a warning, review a member's warning history, and safely remove an isolated warning.

Before you begin

• Complete CoreRP setup.
• Discord Manage Messages is the default permission for /admin. Without it, Discord may not make the command available to you.
• You also need the Moderator role configured in CoreRP. If this role is missing, CoreRP responds You do not have permission to use this command!
• Your server's /admin enabled, channel or role access, and cooldown rules must allow the command.
• If you use a Core log channel, CoreRP needs View Channel, Send Messages, and Embed Links there. Configure the role and channel in Update core channels and roles.

Warnings do not require a citizen ID. They belong to the Discord member across all characters, so deleting or restoring a character does not change them.

Command options

/admin warn user:<member> reason:<text>
/admin warnings user:<member>
/admin remove-warning user:<member> warn_id:<integer>

• user is required for all three commands and selects the Discord member.
• reason is required for warn. Keep it at 1024 characters or fewer so the public result can display it.
• warn_id is required for remove-warning, starts at 1, and comes from the latest warnings result.

Add and review a warning

1. Enter /admin warn, choose user, and enter reason.
2. Send the command. CoreRP posts a public result with the member, reason, and moderator. It also tries to direct-message the member and send a Core log entry.
3. Run /admin warnings user:<member>. CoreRP publicly lists each warning with a numbered ID, reason, moderator, and date.

The example uses Alex Morgan as user and Repeated fail-RP after staff instruction as reason.

Remove a warning safely

/admin remove-warning removes the selected warning immediately, with no confirmation and no member-facing undo. Confirm the current warning list and intended warning before sending the command.

1. Run /admin warnings user:<member> immediately before removal. Warning numbers shift after a warning is deleted.
2. Confirm that the warning is isolated and its reason matches the record you intend to remove.
3. Run /admin remove-warning user:<member> warn_id:<number>.
4. Confirm the public result. CoreRP shows the removed warning's reason and the administrator. It does not direct-message the member.
5. Run /admin warnings user:<member> again and confirm the intended warning is no longer listed.

Troubleshooting

• /admin is unavailable — confirm Discord Manage Messages and the server's Discord command permissions.
• You do not have permission to use this command! — assign the configured CoreRP Moderator role to the staff member.
• You do not have permission to use this here., This command is currently disabled., or a cooldown message — use an allowed channel or role, enable /admin, or wait for the displayed cooldown.
• @member has no warnings. — there is no warning available to remove.
• Warning with ID 1 does not exist. — run warnings again and use a current ID.

Next steps

Review the current availability of Mute members with /admin mute, or continue with Add and remove vehicles with administrator commands.