Corøna's Studios
  • 👑Corøna's Plugins Documentation
  • CrownPunishments
    • 🎯Overview
    • 👮Permissions
  • ⌨️Commands
  • 📍Placeholders
  • 🖼️Items and Menus
    • 🖱️ClickActions
    • ⚔️Item Syntaxis
    • 💬Messages and Formatting
  • 📖Punishment Types
    • ❌Ban
    • 💻SoftBan
    • 🔇Mute
    • ⚠️Warn
    • 🥾Kick
    • 🧊Freeze
Powered by GitBook
On this page
  1. Punishment Types

Warn

Functionality: Issues a warning to a player. Warnings are logged in the database and can be used to track player behavior. The plugin itself does not enforce any direct consequence from warnings beyond logging, but you can use the warning count placeholder for custom automations.

Usage:

  • Menu: Accessed through the main Punish Menu -> Warn option. Configure reason in the Warn Details Menu (time is not applicable).

  • Direct Command: /crown punish <player> warn [reason] or /punish <player> warn [reason]

Permissions:

  • crown.punish.warn: Permission to access and apply warnings.

  • crown.unpunish.warn: Permission to unwarn players.

  • crown.bypass.warn: Permission to bypass warnings.

Configuration:

  • Warn Command: Configured in config.yml under commands.warn_command. Defaults to warn {target} {reason}. If your server does not support this command, you can change or remove it by leaving this entry empty.

  • Unwarn Command: You can configure an unwarn command in config.yml under commands.unwarn_command. Defaults to unwarn {target}. If your server does not support this command, you can change or remove it by leaving this entry empty.

  • Menu Items: Configured in punish_menu.yml and punish_details_menu.yml under the menu.items and menu.punish_details.warn.items sections respectively.

  • Messages: Messages related to warns are in messages.yml.

PreviousMuteNextKick

Last updated 21 days ago

📖
⚠️
Page cover image