ArchivePunishments

ArchivePunishments 1.2.0

Added

• /suspend <player> and /unsuspend <player>: put an account on hold. The player is kicked and sees "We'd like to talk with you about something, open a ticket in …" until unsuspended.
• 72 punishment categories (39 ban, 33 mute), all in English, with longer and gentler escalation ladders.
• /archivepunishments (alias /apunish) with reload, info <player> and reset <player> [category].
• Muted players can no longer use private-message commands (/msg, /tell, /w, /r, /me, /say, ...). The list is configurable in mute.blocked-commands.
• Muted players now see the reason and the time left when they talk or join.
• Punishing offline players by name (they must have joined at least once).
• New archivepunishments.exempt permission to make staff immune to punishments. Nobody has it by default.
• Automatic config update: an outdated config.yml is backed up as config-old-vN.yml, the new one is installed and your discord-link is kept.

Fixed

• Muted OPs could still chat. Mute enforcement no longer checks any bypass permission. The old archivepunishments.bypass node has been removed.
• Voice chat mute expired immediately: the LuckPerms expiry was passed as a relative value instead of an absolute timestamp.
• Plugin errors when LuckPerms is not installed. The chat mute now works without it and the voice mute is skipped.
• Thread-safety issues: chat and login checks run asynchronously and used to modify shared data and write to disk.
• Punishing a player who is already muted or banned pushed them up the ladder. It is now refused.
• /punishcategories showed 0h for minute-based tiers.
• A duration like 0m silently became a permanent punishment. It is now rejected.
• The login ban screen only showed the time left. It now shows the reason, the staff member and the time left.

Changed

• Bans are stored only in the plugin's punishments.yml and no longer in the vanilla ban list. /unpunish still pardons old vanilla bans.
• /mute and /offend print the offense number to the staff member.

Upgrading

Old punishments.yml data is read as-is (older entries show the reason "Unknown"). Your old config is kept as config-old-v1.yml. If you customized categories, copy them over to the new config.yml.